Tobias Wasner
Tobias Wasner
Further information: This is most likely a timezone related issue. Only when scheduling the "day_rollover" task to run at "01:00" it is not running on startup, when e.g. trying "00:05"...
It is even worse: When I use `schedule.every().days.at("00:00", timezone_string).do(day_rollover)` It get's actually called every time `schedule.run_pending()` is called between 00:00 and 01:00, which is every second for me. So in...
> Having same issue when running inside a container under AWS ECS. Anything on a fixed schedule is not launched > > > > schedule.every().day.at("16:50:00").do(my_task) > > > > I...
#609 Sorry I did create a duplicate, did not find this issue before as I thought it was Docker related. The issue is still persisting for me.
@thomasnordquist Could you please release, so this annoying bug is finally fixed? :)
@thomasnordquist Could you please release, so this annoying bug is finally fixed? :)
URL for EM3 PRO: http://IP/rpc/EM.GetStatus?id=0 Example response: `{"id":0,"a_current":2.167,"a_voltage":229.0,"a_act_power":144.9,"a_aprt_power":495.7,"a_pf":0.29,"a_freq":50.0,"b_current":0.500,"b_voltage":229.7,"b_act_power":64.9,"b_aprt_power":114.7,"b_pf":0.55,"b_freq":50.0,"c_current":0.366,"c_voltage":231.6,"c_act_power":21.8,"c_aprt_power":84.6,"c_pf":0.26,"c_freq":50.0,"n_current":null,"total_current":3.033,"total_act_power":231.546,"total_aprt_power":695.043, "user_calibrated_phase":[]}`
``` 30 vulnerabilities (14 moderate, 16 high) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit...
Same problem here. On startup of this plugin my wifi network is not yet up. Therefor it only tries to connect to the device once, throws this error and never...
mDNS does not fix this. It just fails on startup with the mentioned error message and never re-tries! I will look into switching to HomeAssistant I guess.