Thank you for a very good and educational review. You have a very nice appearance which makes it a pleasure to learn from you. Looking forward to more from you!
A while back, I tried to set up Light Scheduler. But the UI didn't make sense to me and I could not get it to work based on sun angle. I didn't realize that BOTH the schedule, and light angle combined like you showed. It's a really strange way to do it in my opinion. I opted for simple, time-based scheduled lights. I might give Light Scheduler another go after seeing this video. Thanks for making the comparison video, and going into depth on how light scheduler works!
To be fair, I went back into Node-RED and created an inject node with the string "light-only" and sent that to the input of the light scheduler node. The light scheduler node now shows the override in the status. I tried it overnight and so far it seems to be working on sun angle regardless of the schedule. Need a couple more days testing to make sure that works but I think that was the key.
Thanks for the note. Light scheduler is having issues with the "light-only" override not sticking. I've opened an issue on GitHub for that. I have a workaround with the inject node to set the override at startup and then every 30 min.
I tried both big timer and light scheduler and ended up using cron plus. It has many of your solar events plus cron scheduling. One of the features I like is that you can add, change and remove schedules dynamically. I found it more useful for my needs.
Hello thanks for your great videos i love them . In one off your videos you mention that you both https and http to your setup ( home assistent ) after i have duckdns and nabu casa i can`t get any local conection to my home assistent can you tell how you do ? i only have my duckdns conection working and nabu casa and i will say it`s slow , very slow then before i was local user only .
The way I do this is to use AdGuard for my local DNS and I add a DNS rewrite that points my duckdns domain to my internal IP when on the local LAN and public DNS resolves it back to my instance when I'm outside my LAN. But...I can still access it directly via the local IP address. I just have to accept that the SSL cert is not correct for the IP.
@@mostlychris Think they're referring to node-red-contrib-moment. (Node-Red Node that produces formatted Date/Time output using the Moment.JS library. Timezone, dst and locale aware.) Was already installed for me as Date/Time Formatter. Doesn't look like it has scheduling unless you run it through a switch maybe? But then again, the switch node can already handle time conditions so I'm not sure the context of the OP.
light scheduler is dumb, if the common use case is to fill up the schedule to make it work that's a design flaw, for example I ony care about sunlight, I dont want to fill the schedule, and I dont want to set an overrride since I also want to run the override 'trigger' but if I sent trigger it does not ignore the schedule, super dumb
Really helpful for a Node-red newbie. I got my porch lights set up very easily based on your explanations and example. (Used Bigtimer).
Thank you for a very good and educational review.
You have a very nice appearance which makes it a pleasure to learn from you.
Looking forward to more from you!
Thank you! Cheers!
A while back, I tried to set up Light Scheduler. But the UI didn't make sense to me and I could not get it to work based on sun angle. I didn't realize that BOTH the schedule, and light angle combined like you showed. It's a really strange way to do it in my opinion. I opted for simple, time-based scheduled lights. I might give Light Scheduler another go after seeing this video. Thanks for making the comparison video, and going into depth on how light scheduler works!
To be fair, I went back into Node-RED and created an inject node with the string "light-only" and sent that to the input of the light scheduler node. The light scheduler node now shows the override in the status. I tried it overnight and so far it seems to be working on sun angle regardless of the schedule. Need a couple more days testing to make sure that works but I think that was the key.
I prefer to work with the light sensor and motion detector. So the control becomes much finer depending on good or bad weather.
Thanks for the note. Light scheduler is having issues with the "light-only" override not sticking. I've opened an issue on GitHub for that. I have a workaround with the inject node to set the override at startup and then every 30 min.
3 years later, what do you use?
6:38 "I can tell by the position of the sun in the sky, that is time for us to go. Until next time, I am Lothar of the Hill People!"
Nice SNL reference.
I tried both big timer and light scheduler and ended up using cron plus. It has many of your solar events plus cron scheduling. One of the features I like is that you can add, change and remove schedules dynamically. I found it more useful for my needs.
Thanks for the info! I haven't heard of cron plus. Now I need to go find it and play.
Cant wait to get myself a pi. Unfortunately they are all out of stock due to the shortage of chips
Supply chain issues suck. I didn't realize that those were also affected.
What are the two grey nodes before the timer or scheduler node?
Not sure where in the video you are talking about. If it's what I think, they are inject nodes.
Hello thanks for your great videos i love them .
In one off your videos you mention that you both https and http to your setup ( home assistent ) after i have duckdns and nabu casa i can`t get any local conection to my home assistent can you tell how you do ? i only have my duckdns conection working and nabu casa and i will say it`s slow , very slow then before i was local user only .
The way I do this is to use AdGuard for my local DNS and I add a DNS rewrite that points my duckdns domain to my internal IP when on the local LAN and public DNS resolves it back to my instance when I'm outside my LAN. But...I can still access it directly via the local IP address. I just have to accept that the SSL cert is not correct for the IP.
Check the moment library from javascript
Not sure what that means. Might need more coffee but can you explain?
@@mostlychris Think they're referring to node-red-contrib-moment. (Node-Red Node that produces formatted Date/Time output using the Moment.JS library. Timezone, dst and locale aware.) Was already installed for me as Date/Time Formatter. Doesn't look like it has scheduling unless you run it through a switch maybe? But then again, the switch node can already handle time conditions so I'm not sure the context of the OP.
@@d_sellers1 Oh ok. Thanks for the clarification. I'm also not sure of the context. Maybe they'll chime in.
@@mostlychris: 😁😁😁🤑🤑🤑 why count the no. of mangoes?
Still test it your self.
light scheduler is dumb, if the common use case is to fill up the schedule to make it work that's a design flaw, for example I ony care about sunlight, I dont want to fill the schedule, and I dont want to set an overrride since I also want to run the override 'trigger' but if I sent trigger it does not ignore the schedule, super dumb
Sounds like you are on the BigTimer side.
@@mostlychris ended up just using the sun entity from home assistant in nodered, waaaay better than anything