Hi all - I'm struggling with what should be simple, time-based lighting automation. Hoping there's a simple, elegant solution out there that I'm just not grasping yet... The automation involves a motion sensor. When it's on, it checks the time. If the time is between 08:00 and 21:00, it sets the br…

Not really an answer but if something is injecting the wrong timezone, you could use node-red-contrib-moment to translate to the correct timezone. Also, did you make sure to set the correct timezone on your server?

I'm using Node-RED in a Docker container as a service and verified the container has the correct time zone. I'm not sure anything is injecting the wrong time per session, I just can't seem to figure out how to work with it for this specific automation, which relies on the UTC -5 times for it to make…

[image] subjectbit: How would I use node-red-contrib-moment to do what you're describing? contrib-moment allows you, amongst other things, to convert between timezones. So if a node is only processing utc but your input is local (or visa-versa), it will automatically convert it for you. Just …

Hmmm, thanks for the response but I'm still not sure how to use the contrib-moment to achieve what you're talking about. I read the documentation here , but it's just not clicking. I added node to the lighting flow in question and set the input/output TZ to "America/New_York" and then deployed the f…

[image] subjectbit: Is there an example you can share or any other suggestions? Can you give me a simplified example of your flow without specialist nodes? So that I can make sure I'm understanding the need. Then I will see what I can do for you.

Sure and thank you for your continued support! A "state change" node checks a motion sensor in an office A switch evaluates the state change, if yes, it's passed to the already-on node, which checks to see if the office lighting is already on, if it is, the flow halts. If not, it's passed to a tim…

[ { "id": "74bde181.c781", "type": "tab", "label": "Lighting", "disabled": false, "info": "" }, { "id": "ba7fdad2.1f14b8", "type": "server-state-changed", "z": "74bde181.c781", "name": "Motion in Office", "se…

Which node is it that is not behaving as you expect with the time. Is it node-red-contrib-time-range-switch or something else? [Edit] Also, in the debug window the debug messages are shown with a timestamp at the top of each message. Are they correct?

[image] subjectbit: a197150.b9ea2e8 Yes, time-range-switch shows UTC timestamps. This impacts how I want lights to behave because it's 5 hours ahead of my actual time zone. The debug output is in local time (UTC -5). The problem with this is if I want the brightness of lights to vary based …

Node-RED

Node-RED Forum

Trouble with UTC and lighting automation

General

Colin 17 January 2019 13:50 9

Could you export your flow (just enough to show the problem) and post it here so we can see exactly what you have? Then we can run it and see what is going on. See this for how to post a flow if you don't know

Topic		Replies	Views
Time function as trigger in a flow General home-assistant	22	912	15 December 2023
[SOLVED] Issue : display AM/PM time instead of 24hours Dashboard	34	4603	21 December 2023
[ANNOUNCE] node-red-contrib-chronos Share Your Nodes	31	1824	24 November 2020
Motion, timers and lights / getting started General home-assistant	10	3808	13 February 2022
Using the time in node red General	21	12257	7 April 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Trouble with UTC and lighting automation

Related topics