Monitoring missing

[c0fec0de]

• I have a setup with one VR630, VR60 and 4 VR90.
• For various reasons i just want to monitor
• This implies Implementation which doesn't open/close the connection each time #3
• I will fix this and also provide an updated home-assistant integration

[c0fec0de]

Hi,

thanks a lot for ebusd integration into home assistant. As i said, I need to monitor a complex setup with 4 mixers, a warm water circuit and one heater.
The initial bring up was quite fast, but i stumbled over a set of issues:

• the ebusd integration just allows to monitor one device, but i have 6 and do not want to generate multiple instances
• the current implementation issues read operations, this somehow overloaded my ebus and caused error messages in the UI.
  I think it is better to just monitor the values and ask for the values which do not occur on the bus regularly.
• the telnet connection is opened and closed every time
• the mixers (mc) have a suffix .N in case of multiple instances and i do not want to duplicate the definitions in const.py

As these are a lot of conceptual changes, so i tried on my own.
At the end I had to completely rewrite ebusd. I just created a new project called 'ebus'.
https://github.com/c0fec0de/ebus
The documentation is located at https://ebus.readthedocs.io/en/latest/
We can completely convert to ebus or I merge the 'ebus' to 'ebusd'. What do you think?

There is now a Connection object to handle a persistent connection.
A CircuitMap handles multiple instances of the same unit (i.e. mc vs mc.3)
A Units object holds all possible formats (temp, tempok, pressure), their conversion and the corresponding home-assistant attributes.
A Fields object holds the informations from your const.py with the devices, their messages and fields.
I add also some tests, to ensure function and quality. Target is to have 100% coverage. I am not done yet.

I also adapted the home assistant integration accordingly.
https://github.com/c0fec0de/home-assistant/tree/ebus/homeassistant/components/ebusd
It makes use of the new 'ebus' implementation.
The configuration options on the configuration.yaml changed.
I kept legacy. The existing options should work as know.
Additional there is a circuitmap option, which feeds the CircuitMap object.
By default all known attributes of all known devices are listed,
if the monitored_conditions option is not specified.

I am gonna extend the code also to handle the sensor states: No value yet, Value does not exist in system and value available.

Overall i am nearly done with fixing the issues above. I would try to get the home-assistant integration merged as soon as possible,
but i need to extend documentation and testing first.

After that, there is the other idea, to load all field defintions from the ebusd-configuration repo/URL