The appliance is offline - But it is not about homebridge-homeconnect HOT 5 CLOSED

Yes, the API is quite unreliable. I have suggested to the Home Connect team that there should be an official status page but haven’t received a response yet... which is why I created my own unofficial version.

from homebridge-homeconnect.

Those are all errors with the Home Connect API. They are not caused by this plugin, and there is nothing that I can do about them.

I have knocked together a quick Home Connect API status monitor which you can find at:
https://www.thouky.co.uk/homeconnect.html

Obviously this is running via my own internet connection and monitoring my own appliances so it won't show problems that only affect some users, and will have some false alarms if there are problems with my network connection. However, in this case you will see that I experienced similar error messages around the same time that you did.

from homebridge-homeconnect.

Oh man.. sorry to bother you. To me it seems that the Home Connect API is very unreliable.

My log is flooded now with the error every 10 sec.

Starting events stream for all appliances
Terminated events stream for all appliances: Home Connect API error: Gateway Timeout

But you Home Connect API status monitor will help to see, that the problem is "global" and not due to anything local or with the plugin.

Again, sorry to bother.

from homebridge-homeconnect.

@thoukydides Out of context.. but I noticed when I restart homebridge and the coffee maker is off, because of the restart the coffee maker is turning on every time. Is this meant to be?

from homebridge-homeconnect.

I noticed when I restart homebridge and the coffee maker is off, because of the restart the coffee maker is turning on every time. Is this meant to be?

This is the fix for issue #17. Due to poor design/implementation of the Home Connect API some appliances do not return the correct options for programs unless they are currently selected. Hence, to construct the configuration schema it is necessary to turn on the appliance, select each program in turn, and read their options.

The results should be cached, so this should only happen the first time that the plugin is started after upgrading to v0.17.0, when the Identify routine is invoked, or when the cache is invalidated (e.g. by changing the API language). This is how it behaves with my physical appliances and with the appliance simulators.

If you are seeing this behaviour every time that you restart the plugin then please raise a new issue for it and provide a full debug log.

from homebridge-homeconnect.