Max! eq-3 integration broken in current builds?

Hi,
i am wondering if the component (using hass.io) is currently broken or if its just me.
A few weeks back i added the config element for the gateway, the heaters showed up as entitys and i was able to control them. Then i had to use the LAN cable otherwise, removed it, and config showed the expected error that the cube is not available. A few weeks forward, cable goes back to the cube, config stops giving that error, also no error in logs (in dev console). But the heaters won’t show up again. discovery: is still in the config file. since then i installed a few updates on hass.io. Reset of cube did not solve the problem, can still use it with the eq-3 app, though. Is it me or is the component broken?

Hey,

i have the same issue here :frowning:

There is one solution to this behaviour, at least for me it worked: Don’t keep the eq-3 software (system tray) open on any machine. There seems to be some kind of lock, where only our eq-3 PC software can access the cube OR hass.io can. Might help.

Thanks for the answer… I don’t have the software on any device running :frowning:

Try to reset, then remove power, then add your controls again. For me it works locally without internet connection, hass.io can get the heating systems even tho the “internet” LED is blinking. But honestly i have no clear plan to reproduce that it works. Just praying that both components, MAX! and hass.io won’t stop working, or at least start to give proper error messages.