You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
first of all: thank you very much for you important work to emancipate from the cloud and the closed source software.
After a little struggle with the setup, i am able to control the main features of my ETBX12EF9W.
Now i would like to monitor the behavior of the heatpump and the bridge. Therefore i try to find the mqtt topics as described in your manual. But in my mqtt explorer i can only see the topics as you see in my attached screenshot
I would like to the these informations because if i try to change the silent mode or the user mode by using the entitys in homeassistant , it does'nt have any impact. Also if use the L92 commant via telnet.
thanks in advance for any hints.
Philip
PS: if this post is more a kind of a discussion than an issue, fell free to move.
The text was updated successfully, but these errors were encountered:
This is likely the same issue as issue #98 - it seems that the bridge attempting to change quiet mode or trying to claim installer mode does not work on all systems - not sure why yet. Perhaps it is not possible, perhaps the mechanism is different.
Hello,
first of all: thank you very much for you important work to emancipate from the cloud and the closed source software.
After a little struggle with the setup, i am able to control the main features of my ETBX12EF9W.
Now i would like to monitor the behavior of the heatpump and the bridge. Therefore i try to find the mqtt topics as described in your manual. But in my mqtt explorer i can only see the topics as you see in my attached screenshot
I would like to the these informations because if i try to change the silent mode or the user mode by using the entitys in homeassistant , it does'nt have any impact. Also if use the L92 commant via telnet.
thanks in advance for any hints.
Philip
PS: if this post is more a kind of a discussion than an issue, fell free to move.
The text was updated successfully, but these errors were encountered: