search

ottopaulsen / node-red-contrib-power-saver

A Node-RED node to saver money by turning off when the power is most expensive
Other
71 stars 17 forks source link

Possible bug in 3.0.0 - When tomorrows price is not ready node gives error messages #9

Closed Swoop86 closed 2 years ago

Swoop86 commented 2 years ago

See attached image, have not seen it to affect the schedule it creates, but could potentially create issues? I am assuming this to be because of tomorrows price not being available, will check again after 13:00.

image

Swoop86 commented 2 years ago

Errors are gone after 13:00.

ottopaulsen commented 2 years ago

Thanks for reporting this.

Could you try again tomorrow before 13.00, and send me the input to the Best Save node? Just put a debug node alongside it and send it the same data. Also, I would like to see the total output from output 3 on the Best Save node. A copy of your flow would also be helpful.

Otto

Swoop86 commented 2 years ago

Skjermbilde 2021-12-14 kl 12 33 57 nordpool_powersaver_issue_9.txt

Gybrsh commented 2 years ago

Same here. To me, it may seem as if this now only happens at the first execution of the flow (version 3.0.3).

Subsequent runs of the flow do not produce the same messages. Restart nodered and it reappears.

Whether the cause lies with node-red-contrib-power-saver or it is the source of ps-receive-price (Nordpool integration in HA) that creates trouble is unknown to me.

ottopaulsen commented 2 years ago

Please try the fix in version 3.0.4. I can see what is going wrong, but I am not 100% sure it is fixed. If it still isn't working, please send me the input to the Receive Price node, that is the output from the Nordpool sensor.

Swoop86 commented 2 years ago

Will let you know tomorrow.

Swoop86 commented 2 years ago

Error messages are now gone here.

ottopaulsen commented 2 years ago

Great. Closing this, then.