-
Notifications
You must be signed in to change notification settings - Fork 110
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
Sensor doesn't update on new day #429
Comments
looking at my on log I see that something is seriously wrong with the addons when you have tried to add sensors, which you can't if you add additional sensor for same setup with different additional cost, since they will get the same name as the other. Then there will be a mental heywire of stuff running that are not present. Then when removing the, not much is done (if I look in the code). Maybe an idea to merge the unique entity_id patch soon. |
Not really. This is already been documented and asked multiple times. The ability to set your own unique id is most likely never going to get merged. |
I reread your issue. Thanks for the report. What ha version are you using? |
The entire log is super weird at it does not make sense at all. Seems like there are some additional sensors that messes things up. Please remove them all sensors and the entire nordpool.. Restart ha and add them back again. If the issue persist post the new log |
2024.10.3? As stated in the issue. |
It makes sense, since I added a couple of sensors (was trying to change the additional cost for both in and out price), it failed cause of the sensor got the same name as the old one and the failed halfway, creating a Integration entries without device and entity, but obviously adding some other stuff to HA. Reloading the integration in that state does not help. Removing Integration entries doesn't. Restarting HA (after tomorrow's price has arrived) looks to be the only solution to get out of it. |
Would be nice if the integration didn't create the same id, for the same setup for a sensor where only the additional cost is different, and the fail. |
Version of the custom_component
0.0.15
Homeassistant version
2024.10.3
Configuration
Configured through UI
Describe the bug
I have to sensors for the same region with different additional_costs_current_hour (one for selling and one for buying), one of them stop updating after midnight, even though both where working fine before midnight and both had tomorrow_valid: true before midnight
Looking though the log it's strange that then sensors have names like: nordpool_kwh_se4_sek_3_10_0, nordpool_kwh_se4_sek_4_10_0 even if they are named correctly in the UI. Also strange are the are both updating twice every hour (with a little different price also, super weird), it's like there are some artefact stuff left somewhere that are messing with me. This started after updating to 0.0.15.
Debug log
The text was updated successfully, but these errors were encountered: