Closed avvalex closed 3 years ago
All 500 and higher errors are reported when issues is identified as fault on server side. Sometimes it is due to connection errors between boiler and Ariston server (usually https://www.ariston-net.remotethermo.com is affected as well) and sometimes the issue is with specific requests that some data is incompatible with specific model. If Ariston server is affected then nothing can be expected from the integration. Unfortunately I have no data to go with as I have not updated integration to store html replies for faulty cases (usually some hints can be there) and it is hard to get someone to provide me with required data without describing steps to get the data or requesting login and password to do it myself or creating prototypes which gather more data in specific cases.
Do you get those fault for different types of requests (there is often "_get_xxxxxx" included in the log) or a specific request?
You may try uploading ariston.txt (rename to ariston.py), which should store additional files when setting store_config_files
to true
in configuration.yaml.
The result should be files ending with _[reply code]_error.txt among many other. If to open then as html files a fault description might be present.
You may also try to set polling
to 1.2 in configuration.yaml.
Usually i had no problems with connection but recently i got more errors with code 500 and many timeouts and by setting that value higher than 1 makes integration slower but generates less errors (gives more time for the server to process and thus less "overload" and timeouts).
Issue closed due to no activity and no data to work with.
In case of faults set store_config_files
to true
in configuration.yaml
to gather more data so that details could be analyzed.
Issue can be reopened if more data is provided.
You may also try to set
polling
to 1.2 in configuration.yaml. Usually i had no problems with connection but recently i got more errors with code 500 and many timeouts and by setting that value higher than 1 makes integration slower but generates less errors (gives more time for the server to process and thus less "overload" and timeouts).
polling it refers to period_set e period_get?
Hi, great work, but in HA logs i had tons of 500 and 590 (or 599, i don't remember) errors (warnings). Is there a way to fix the problem? It's not related with sensors, since i've tried with only one sensor in config.yaml and errors start appearing the same... For the rest the integration seems to work well... Thanks