I have Homebridge running on an rpi and Node-red on the same rpi, using Maker API on HE to send info to Node-red. I am trying to get a u by Moen to talk to Node-red. It seems like a path to this might be if I can get Home Kit to send alerts/ifo to homebridge.
Is this possible or does anyone know of a way to connect a u by Moen with Node-red?
Thanks
Unfortunately HomeKit doesn’t send to homebridge (except by being able to trigger devices homebridge exposes to HomeKit).
Thus the best way I have found to send if from kit to bridge and then on is create a virtual switch in bridge, then build a home kit automation that turns on the virtual switch when the event you are monitoring occurs and off when it stops. The problem is that it requires basically 1 automation per bit of information you are sending. It works fine for me for a motion sensor, but for anything more complex like a temp sensor it is effectively useless. So that is probably not worth it for the moment device
That would work for me as well I think, I just want to have automations that let the lights stay on while we are in the shower. I have a motion sensor there but it seems to get a little unreliable when the humidity is high.
Try a Hue motion sensor. I’ve had one in my bathroom for years, almost directly over the shower and it’s never been a problem.
Ugh, I'm trying to get away from Hue...
Joins directly to HE if you want. It’s not the snappiest sensor I own, but it sure is reliable.
Not after snappy with the shower, just an acknowledgment that it exists. 
Of course I might do something around lowering the temp over time if someone is in there to long...
Would you mind providing more detail around how you created the virtual switch in home bridge and then how you discovered it in home kit. I have Homekit up and running with the shower but am missing how to get the virtual switch in Homebridge...
First I use the homebridge-dummy to create the device:
Then I make sure it is visible as an item in the Homekit Home app.
Then I build 2 automations, one to turn it on and 1 to turn it off:
The other automation is the mirror image of this one.
Basically, it translates to when an event (motion protected true/false), either turn on or turn off the switch that is name Eve Motion Passthrough.
@tmichael I know you aren't the Homekit/Moen Helpdesk but... I have everything looking like I believe it should. But, when I go to create an automatic with the Moen it doesn't show up as an option to use in an automation and when I look at yours it looks like you have it set up as some type of motion automation. Thoughts? And thank you for taking the time.
So when creating an automation, you first pick the trigger. As you said, in my original example I was basing in on the motion sensor detecting motion (the last of the options shown in the first image)
Alternatively you can trigger when an accessory is controlled. Thus my thinking is that if you chose that option, then the Moen would be on the screen you see. Since I don't have that you can see what I have. I chose the fan to get the 3rd image which let me chose to do something when the fan (or probably Moen turns on). It of course also gives options like only at a specific timeframe or when people are present or absent (per Homekit).
Then the action (not shown in an image) is to trigger the virtual switch that Hombridge exposed.
Thank you. The U by Moen doesn't seem to be recognized as something that can trigger an event in Homekit. It can be controlled (turned off, on, temp set) but can't trigger an action.
That’s unfortunate. I would have thought that it would have been visible like the fan as having been turned on or off.
Download the Hubitat app
