Great video! You can get around the merge by setting using the change node to set alternative msg values (msg.heatsched) to be used later in the flow. BTW, I finally got my version up and working based off our previous discussions and your earlier examples you shared. The US version of the climate/honewell API left lots of challenges and ended up creating custom schedules (heating and cooling) with specific temperature so I now control everything from HA including guests/vacation/etc and I override any schedules in the thermostats. Still have some clean up but is working.
Glad it's working, yeh i think it's probably easier to control it all from inside HA! I'm pretty sure I had tried that and for some reason it couldn't make it through the switch, maybe I was doing it wrong - it was a little while ago now!
Sounds like a great idea for boosting heating in individual rooms, hopefully it’ll work with Hive... but more interesting is the explanation of the merge function and how to extract the elements from the payload, as I’ve been trying to suss that out for a while. I’ve been using AppDaemon as a light controller for my Hue and Tradfri remotes, but it eats CPU cycles. I’ve looked at NodeRED to do this instead, but making many flows for each remote is just too fussy. Merge should help me make a single flow for each remote type, now I understand how it works.
Hi Will, another great video, i see that you have hard code the boost temperature to 21 , how would you configure it to say get an input from say a text box, i am struggling to find an answer , thanks
The end time in lovelace will change, but the time which went into node-red will stay constant as it actually uses the delay instead of time - the end time is purely so you have an easy way of knowing that a 2hr30min delay will mean it finishes at 12:30 for example
Nicht das ich wüsste. Versuch doch mal die Untertitel zu aktivieren und von RUclips auf deutsch übersetzen zu lassen. und dann halt öfter auf Pause klicken. Bei mir hat die Anleitung jedenfalls funktioniert....aus die end_time...die ist bei mir 2 Stunden in der Zukunft auch wenn ich nur einen Boost von einer viertel Stunde auswähle.
Great video! You can get around the merge by setting using the change node to set alternative msg values (msg.heatsched) to be used later in the flow. BTW, I finally got my version up and working based off our previous discussions and your earlier examples you shared. The US version of the climate/honewell API left lots of challenges and ended up creating custom schedules (heating and cooling) with specific temperature so I now control everything from HA including guests/vacation/etc and I override any schedules in the thermostats. Still have some clean up but is working.
Glad it's working, yeh i think it's probably easier to control it all from inside HA! I'm pretty sure I had tried that and for some reason it couldn't make it through the switch, maybe I was doing it wrong - it was a little while ago now!
Like the video Will, keep up the good work, I like you enthusiastic approach!!
Thank David!
Sounds like a great idea for boosting heating in individual rooms, hopefully it’ll work with Hive... but more interesting is the explanation of the merge function and how to extract the elements from the payload, as I’ve been trying to suss that out for a while. I’ve been using AppDaemon as a light controller for my Hue and Tradfri remotes, but it eats CPU cycles. I’ve looked at NodeRED to do this instead, but making many flows for each remote is just too fussy. Merge should help me make a single flow for each remote type, now I understand how it works.
Yeh it took me a while to figure out merge! Glad you can use it for something else!
Hi Will, another great video, i see that you have hard code the boost temperature to 21 , how would you configure it to say get an input from say a text box, i am struggling to find an answer , thanks
Great Video as always. Everything works for me except the end time. It's 2 hours ahead of my actual time. Any idea what I can do to change that?
Great video. But when I start heating boost, end time keps changing time. First says 18:25 and time, and after 10 min. says 18:35.
The end time in lovelace will change, but the time which went into node-red will stay constant as it actually uses the delay instead of time - the end time is purely so you have an easy way of knowing that a 2hr30min delay will mean it finishes at 12:30 for example
{{ as_timestamp(states.sensor.date_time_iso.state) }} should give you local time as timestamp, just as now does but in UTC.
Amazing! Thank you! I'll have to give it a go!
can you show the whole value_template: ? If that is where this would go :)))
@@Golla63 {{ (as_timestamp(states.sensor.date_time_iso.state) | int + (float(states('input_number.boost_hour_select'))*60*60)) | timestamp_custom('%H:%M') }}
für mich ist es zu schnell. Gibt es eine Beschreibung zum lesen?
Nicht das ich wüsste. Versuch doch mal die Untertitel zu aktivieren und von RUclips auf deutsch übersetzen zu lassen. und dann halt öfter auf Pause klicken.
Bei mir hat die Anleitung jedenfalls funktioniert....aus die end_time...die ist bei mir 2 Stunden in der Zukunft auch wenn ich nur einen Boost von einer viertel Stunde auswähle.