search

cyr-ius / hass-heatzy

Climate Home Assistant component for Heatzy Pilot
MIT License
33 stars 13 forks source link

API with error code 500 - 502 (Unavailable device) #41

Closed JGitHubB closed 2 months ago

JGitHubB commented 8 months ago

Integration works great. But as you can on these logs, around every hour Heatzy becomes unavailable, which messes up the timeline.. Seems like something drops regularly. image

hombre-13hb commented 8 months ago

Hi, I've got roughly the same issue. Anything I can do to fix it ? Thanks

cyr-ius commented 8 months ago

I'm doing an API pool every 60 seconds since the plugin was created. But I have the impression that the web server opposite is no longer holding the load

cyr-ius commented 8 months ago

Please , test with 5.9.0

JGitHubB commented 8 months ago

Enabled debug mode + updating to 5.9. Will let you know.

hombre-13hb commented 8 months ago

Hi, installed 5.9 but entities keep being unavailable regularly making automation impossible to use. What can I provide to help ?

JGitHubB commented 8 months ago

Same there with 5.9.7

cyr-ius commented 7 months ago

As I stated above, unfortunately the 500 errors are not my fault. It's the constructor's API that returns this event to me. At first I thought it was a problem with the extraction frequency being too high, but by increasing the interval between scans it didn't change anything. I also tried switching the orders to digital instead of chain since both are possible. But that doesn't change anything.

I believe both machines hosted by Amazon do not hold the load.

Jeedom users encounter the same issue https://community.jeedom.com/t/message-de-probleme-de-connexion/112823/8

cyr-ius commented 6 months ago

Un mode Websocket extrêment performant , à tester en sélectionnant les versions commençant par : ws- En activant le mode Beta dans HACS Première sortie : ws-6.1.0 Résoud les problèmes d'erreur : 500 , 502

cyr-ius commented 5 months ago

Fiw with beta version, please test