ottopaulsen / node-red-contrib-power-saver

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

Issue with the fix for "Configured values for output are sent, not only true/false" #130

Open eirektg opened 1 year ago

eirektg commented 1 year ago

In the change log for 4.1.2 is says: "Fix so configured values for output are sent, not only true/false"

Was this actually fixed?

I can send you the full output from node 3 if you want, but here are the important parts.

Config: {"fromTime":"00","toTime":"00","hoursOn":3,"maxPrice":null,"doNotSplit":true,"sendCurrentValueWhenRescheduling":true,"outputIfNoSchedule":true,"outputOutsidePeriod":false,"outputValueForOn":1,"outputValueForOff":0.6,"outputValueForOntype":"num","outputValueForOfftype":"num","override":"auto","contextStorage":"memory","hasChanged":false}

Hours: [{"start":"2022-12-01T00:00:00+01:00","price":3.49,"onOff":false,"saving":null},{"start":"2022-12-01T01:00:00+01:00","price":3.45,"onOff":false,"saving":null},{"start":"2022-12-01T02:00:00+01:00","price":3.48,"onOff":true,"saving":null},{"start":"2022-12-01T03:00:00+01:00","price":3.43,"onOff":true,"saving":null},{"start":"2022-12-01T04:00:00+01:00","price":3.39,"onOff":true,"saving":null},{"start":"2022-12-01T05:00:00+01:00","price":3.52,"onOff":false,"saving":null},{"start":"2022-12-01T06:00:00+01:00","price":3.63,"onOff":false,"saving":null},{"start":"2022-12-01T07:00:00+01:00","price":4.68,"onOff":false,"saving":null},{"start":"2022-12-01T08:00:00+01:00","price":5.17,"onOff":false,"saving":null},{"start":"2022-12-01T09:00:00+01:00","price":5.38,"onOff":false,"saving":null},{"start":"2022-12-01T10:00:00+01:00","price":4.75,"onOff":false,"saving":null},{"start":"2022-12-01T11:00:00+01:00","price":4.53,"onOff":false,"saving":null},{"start":"2022-12-01T12:00:00+01:00","price":4.53,"onOff":false,"saving":null},{"start":"2022-12-01T13:00:00+01:00","price":4.61,"onOff":false,"saving":null},{"start":"2022-12-01T14:00:00+01:00","price":4.75,"onOff":false,"saving":null},{"start":"2022-12-01T15:00:00+01:00","price":5.13,"onOff":false,"saving":null},{"start":"2022-12-01T16:00:00+01:00","price":5.15,"onOff":false,"saving":null},{"start":"2022-12-01T17:00:00+01:00","price":6.03,"onOff":false,"saving":null},{"start":"2022-12-01T18:00:00+01:00","price":4.79,"onOff":false,"saving":null},{"start":"2022-12-01T19:00:00+01:00","price":4.68,"onOff":false,"saving":null},{"start":"2022-12-01T20:00:00+01:00","price":4.72,"onOff":false,"saving":null},{"start":"2022-12-01T21:00:00+01:00","price":4.27,"onOff":false,"saving":null},{"start":"2022-12-01T22:00:00+01:00","price":3.8,"onOff":false,"saving":null},{"start":"2022-12-01T23:00:00+01:00","price":3.8,"onOff":false,"saving":null}]

Version: version: "4.1.2"

eirektg commented 1 year ago

The logic related to this issue seems to be like this: When I do the '"sendSchedule": true' command, it is working like its supposed to. But when the node itself generates this output (after a typical price input etc.) it only outputs true/false and not the configured values