Sorry, i just don't understand attitude like that.... good luck with your NR endeavors or whatever you want, I can assure you that neither I or others were after pissing you off for whatever reason you felt slighted
I cannot say enough how much i appreciate some of your contributions (example: IKEA blinds) but a majority of your really apparently-at-worst-angry and at-best-passive-aggressive posts are really perplexing... this whole Hubitat thing doesn't appear very fun for you, i wish it was, it would be so much better for everyone because you do have programming talent.
I guess the last thing I would say on this, is that if anything isn't obvious and clear, there are many users in here that try to answer questions - whether they are Hubitat node specific or not.
So, for anyone - if there is ever a question that you can't figure out, just ask for help. Hopefully someone else on here will know the answer and be able to help.
I'm getting some odd behavior when I change from RGB to CT - the first time it does not take but the second time it does.. everything else seems to work well. This may be an Amazon Echo thing but wanted to give you a heads up.
Now who is trying to get this thread off the rails???? I am embarrassed to admit that I know who you are talking about. I made it thru episode 1 and about 10 minutes into episode 2 before I had to stop.
I get notifications just fine on my phone when the contact sensor is open, but i also get them when the mode changes, regardless of contact sensor state.
Should the open/closed switch be after the mode switch?
And to cancel the timer, when switch is closed, is the change node in the correct spot, with set msg.payload to stop?
EDIT: Stop timer definitely wrong! Ignore!
Beforehand, note the shape of the blue box at the bottom of the Mode Node, it means sending events when the mode changes (like a HE trigger). The blue box will become hollow when it doesnt "send events"
Thanks @mike
Knew it would be simple....i actually thought of that, but was looking at the switch nodes. Didnt think to look at mode node......Thanks
Btw, the status blue box remained solid!
Thanks @JasonJoel. I just had the problem again. That's 4 days in a row. It seems to change to evening and night mode. But won't change to day until I reboot node red.
That is bizarre. Are you sure the logic that is triggering day mode is triggering when you expect? Does that same set mode work if you trigger it manually with an inject node?
I'm trying to understand if it is really s hubitat node issue, or some other quirk in the flow.
My modes are all changing, so I don't know of an issue with hubitat set mode node, but that doesn't mean there isn't... No one else has reported set mode not working for them, though.
Yes, but does the logic try to execute at the expected time? You know it executes at reboot.
But does it try to run when you expect it to, and fails? Or is there something wrong with the flow and it never triggers/runs at all at the expected time? Two possibly different issues.
And if you add an inject trigger, does it work/run without a reboot?
Could post the flow if you want, and one of us can look and see if we see something wrong.
Not sure if anyone is using telegram, but i thought i would mentioned it incase.
Im using telegram for other groups, so gave it ago for my hubitat/nodered notifications too. I Must i'm quite impressed.
I've been using that Harmony node for a while and it is great - BUT ..... I've found that it never picks up my Harmony Hub again whenever I have to restart Node Red. Even when I go into the Harmony Node and re-connect it, it takes many attempts before it will actually connect again. Don't know if it's something in my system but at the moment I've reverted to the Hubitat community driver for Harmony. I'd be interested to hear other's experience with it.
