g1za
g1za
Try to have a look here #164 It worked for me.
I moved to yi-hack-5 from 4. 142% wifi strength, Yi dome. Let me know if there is any command I can run on my camera (and how) to debug this.
I had the same issue with my Yi Dome 720p camera Firmware Version | 0.3.2 Base Version | 1.9.1.0J_201809191135 Model Suffix | yi_dome Hardware ID | 63US This change in...
Just for the records, I never enabled that option and the code fix was enough for me.
Another solution/implementation, like the one initially suggested by @Petro31, is proposed here: https://github.com/home-assistant/core/pull/88655
If useful I see some indices change over time ``` `2024-03-30 10:30:00,856 - web_server - INFO - Passed runtime parameters: {'prediction_horizon': 48, 'pv_power_forecast': [1478, 1584, 1631, 1678, 1661, 1644, 1602,...
``` `2024-03-30 13:30:00,857 - web_server - INFO - Passed runtime parameters: {'prediction_horizon': 48, 'pv_power_forecast': [1602, 1551, 1445, 1339, 1190, 1042, 843, 644, 470, 297, 148, 0, 0, 0, 0, 0,...
``` `2024-03-30 14:00:02,529 - web_server - INFO - Passed runtime parameters: {'prediction_horizon': 48, 'pv_power_forecast': [1551, 1445, 1339, 1190, 1042, 843, 644, 470, 297, 148, 0, 0, 0, 0, 0, 0,...
I thought that could be a reason (maybe my source data had changes due to the time change), so I checked but according to the command I'm expected to pass...
I definitely believe it is still a bug related to DST, @davidusb-geek At the switch to the new time the log didn't show any error anymore and the optimization was...