-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sensors stop updating #52
Comments
Can you try updating file to this PR?? Please post results |
Ok, i need you to show logs here. i need you review ERROR and WARNINGS (and DEBUG if you can) it is posible something goes wrong here , i have not this model uponor and i can not test it in my home Por cierto, es agradable encontrar españoles por aqui, saludos. |
please edit file manifest.json and add one line : "iot_class": "local_polling", |
I have added the above line to manifest.json and will reload. Is this the way to add debug in config.yalm: I will monitor it, but maybe I will need help how to extract warnings, errors and log data. I will ask if needed. Saludos!! |
Not updating sensor for around 1 hour. Updating uponor climate took longer than the scheduled update interval 0:01:00 This error originated from a custom integration. Logger: custom_components.uponor.climate Uponor thermostat was unable to update: ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')) Logger: homeassistant.helpers.entity Update of switch.uponor_cooling_mode is taking over 10 seconds Logger: homeassistant.helpers.entity Logger: homeassistant.components.switch Updating uponor switch took longer than the scheduled update interval 0:00:30 Update for switch.uponor_away fails During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Same problem overhere sinds a couple of days. |
Try to solves asev#52
Try to solves asev#52
Can you try updating file to this PR?? Please post results, i create warning messages if create a lot of api calls and i create new attribute last_update , i try to change update calls doing only one in same time |
Once updated, it kept updating a couple of sensors temperature changes, but nothing again for a hour (I even put some heat of a sensor to force it but it was not updated). all warnings with las PR below (3rd one is a error I am highlighting). I have to mention version 0.8.3 works in my case although this version just gives some message when I change thermostats but working well:
Log with last PR, following your intructions:
|
Try to solves asev#52
Ok, You put me behind the clue, thanks (i use your chatGPT solution, hehe) I create mix version between 0.8.3 and my PR, i update my PR with new commit changes. Please try my PR version and post results |
Already running new mix PR (3fdc4bb). First impressions (15min): sensors look to get updated, thermostast work and no log yet (even no warnings). I will follow-up it along the day. I only have this general warning, realted to all future deprecations, most in 2025, to be considered in the future: Logger: homeassistant.helpers.frame |
2 hours later, it is working Ok and there are not new logs. |
Ok, this week i will see it |
Hi @dacorde , can you try new PR file to solves deprecated call async_add_job ? |
I have overwritten "init.py" with your PR.
|
Hi @dacorde , please, try new PR file to solves deprecated call async_add_job |
From last 2 days I have realized temperature sensors get frozen with not data updated during hours. I looks to happen like twice per day. I have manually downgraded to 0.8.3 and it looks to work now.
Changes could be related, apart from 0.9.1., with HA 2024.6.4
Hardware: X245 - T-148
Anyone more with this issue?
The text was updated successfully, but these errors were encountered: