Hi Julien,
after upgrade that you released, I started to have some problems with auxiliary sensors from the alarm system. The following message appears: entity not available.
What could be the reason?
Good catch! The issue is fixed in this commit.
You can either try to run the current “master” version from HACS, or wait a few days for an actual release that will contain the fix.
Hi Julien,
I’m setting Up mi HA installation and I have home control with MyHomeServer1 and I’m tuning a little bit my climate control. I’ve setted up my KM4691 with heating/cooling and everything else. Then I find that with sizing 60 I can get also humidity but I don’t know how to set it in configuration.yaml.
Thanks in advance for help and for your integration.
Hi Julien,
no problem, let’s wait … just one thing I also encountered problems with the 4 zone control unit (thermoregulation) the set-point temperature and the current temperature are not displayed and then at each HA restart the energy_today and energy_current_month sensors are disabled.
The messages you can see, here I’m not sure what the compatibility matrix is, I suppose some old gateways don’t know about newer messages
The messages you can send, and here is where the problem becomes more complex.
In your case, with your F454 you can see WHO 6 and WHO 8, but you can only send WHO 8 commands; and F453AV can only send WHO 6 commands.
So, given the very restrictive circumstances, I will not build these commands into the integration at this point.
Your best bet is to do what @Costa was trying to do: use the send_message service to send the message you want. If your gateway understands it, it will send it.
@Murazor, as far as I know, you have nothing more to configure. If your device sends DIMENSION 60 humidity values, they will be added to the climate entity. But to be honest, since I don’t have the heating system, I cannot tell you what it looks like in Home Assistant; it’s possible that the humidity value appears as an attribute.
@vix0971, I’ll have a look at the energy entities. For the 4 zones heating, do all zones have the same problem? (Even the “central unit” zone?)
Do you have some logs that could help me find what’s wrong?
I’ve experimented with the script examples/command_session.py from my github repo (https://github.com/karel1980/reopenwebnet) and these are the results I’m getting:
My setup is as follows:
A router with a wired connection to an F545 and a Deco X60 mesh network
macbook connected to the Deco X60 network.
When the Deco network is in router mode (basically the macbook and the F545 are on a different network):
The connection is always lost after 30 seconds.
When the Deco network is in AP mode (i.e. macbook and F545 are on the same network):
The command_session.py script keeps working - as long as I keep MESSAGE_INTERVAL < 30.
Oh, and event sessions keep working, even when the client and the F545 GW are on different networks. That’s why my current implementation of the reopenwebnet mqtt bridge uses a long living event session for the mqtt state topic, and opens a new command session for every message received on the mqtt command topic
Hi,
I have a old Bitcino system, still using telephone landline.
I believe the gateway is the F422. I don’t see any ethernet port on the equipment and the system in not connected to my LAN …
Some images: