Martin Høy

@mvjt Your problem is that you have two schedulers running in parallel, writing their output to the same switch. But the two schedulers might (almost always) disagree on whether the...

@mvjt It sounds like you misunderstand how this works: It doesn't matter whether the two schedulers overlap wrt. the time-periods they consider. The scheduler is always running and will _always_...

@mvjt The lowest-price nodes sends output whenever: 1. It receives (valid) input 2. The schedule changes (going from on->off or opposite) If you think you're get too frequent outputs, you...

@stenkarlsen: It's included in the standard HA package, and allows you to create entities in HA from Node-RED. https://github.com/zachowj/node-red-contrib-home-assistant-websocket You also need this HA-integration, in order for the ha-sensor node...

@stenkarlsen: Maybe you have an old version? The latest version of node-red-contrib-home-assistant-websocket is 0.45.9: https://github.com/zachowj/node-red-contrib-home-assistant-websocket/tags

This looks like a timing issue: The ON/OFF commands might not arrive in the correct order. Example: What if the OFF-command from the 00-06 node arrives after the potential ON-command...

@ozziemannen See also my response [here](https://github.com/ottopaulsen/node-red-contrib-power-saver/issues/92#issuecomment-1266940527) on how I handle output from multiple schedulers running in parallel.

@lillson I also thought there was something wrong with "Best Save", but this is the way it's supposed to work. You might want to select the n number of hours...

@krnvar You can combine multiple "best price" nodes in parallel. I'm using two that each considers a 12-hour interval. Thus, I know that the water boiler will be on at...

@Swoop86 I believe the node sends one output upon initialization, and another one when it receives the dynamic config. You can confirm this by e.g. setting a different setpoint on...