Thanks. I found some articles about centring the group name, but it's rather beyond me 
No worries. All in due time. Rome wasn't built in a day... Etc etc.
I am mostly stuck with the next few things I want to get done, hoping for Bruce to add event type to the Maker API response. I have a few automations in RM that do different things based on physical on/off vs digital. Can't do that today w/Maker API.
1 Like
Could you post a picture of how you do that in RM? I have never seen an option to choose whether a device is physically turned on vs digital but have seen people mention it a bunch.
Yeah, I know about them since I was the one asking Hubitat to implement them.....
You have now 4 PRs from me with all the different additions, including the shape change
1 Like
Choose "Physical Switch" or "Physical Dimmer" as the trigger.
Pretty simple. Just select "physical switch" or "physical dimmer" as the trigger type in an RM rule, instead of "switch" or "dimmer".
All that really does is look at switch/dimmer events that have type=physical in the event.
Duh, never even thought to look in the list. I always assumed it was somewhere after selecting "switch".
Well, that is how it should be (in my opinion). I think there should be one more attribute type on all event triggers to filter based on a criteria (like type=digital or physical). But Bruce has his reasons for doing things the way he does it. 
And after Bruce adds type to the Maker API return message, that's exactly how I'll do it in node-red.
Yup. And it could be implemented for locks as well .....
Yup! Would be a very flexible capability... Might be a nightmare to add behind the scenes though. Only Bruce knows that for sure, though.
No locks here yet. I have read so many posts here about people having trouble with them, it makes me nervous. I am intrigued by the Wyze lock even though it doesn't have HE integration.
The problems (for those that have them) seem to be with Schlage z-wave locks. I have Yale zigbee locks. I know of others with Kwikset zigbee locks and Schlage zigbee locks without issues.
Just catching up on this thread after it's gone crazy over the last few days. I've been snowed under by prep for Covid19. Our regional hospital is working 24/7 to triple the number of ICU beds, shutting down elective surgery, and spent $3 million in one day purchasing extra ICU equipment. Crazy stuff.
If I have multiple device nodes of the same HE device on different flows, it only polls HE once. There is no benefit to setting a flow.variable or a global.variable ? Is my understanding correct?
1 Like
Since the topic du jour is smart locks, is there anything i can do to get my Schlage HomeKit-only door lock to somehow talk with HE and/or Node-Red?
I'm sure it would involve some super hackey Alexa or HA jazz
As I understand it, there is no polling. Rather HE sends events, which NR stores. So there is no reason to put the values in a variable.
I don't know if any of you read this thread but I thought it was a BRILLIANT idea to be able to control the temperature of a CT bulb with a virtual dimmer.
So, I figured it wouldn't take much to re-create using Node Red when I discovered the Range Node. I know this isn't monumental but thought it might be helpful and not something others might have even thought of doing
BFAST NOOK is a Device Node for the virtual dimmer and BREAKFAST NOOK is Command Node for a group of CT Bulbs.
2 Likes
Indeed it is.
1 Like
You can watch the output of dd just by using status=progress after the of. It's not "real-time" but it updates every few seconds. It also only shows you the elapsed time and the size that has been copied, so you have to do a little math to figure out how much is left.
Excuse the pun, but there's progress for you. That must be a recent addition to dd.
In the old days, the only way to monitor dd progress was using pv as suggested by @JasonJoel.
I like pv. Lots of data, fast updates. 
I've had mixed results with status=updates. Sometimes I get no updates at all. Guess I should read up on why. I'm sure there is a reason for it that I just don't understand.
