I would have thought that maker api change was much older than 2.2.3, but I guess not (?). I have no way of checking/testing at this point, though.
1 Like
Yeah I think it was 2.2.0 so you should be good.
1 Like
Hmm, well it's not showing in NR but it does show up in the HE device log. The device is an Aeotec Nano Dimmer.
Are you using the websocket connection in node-red? It might not show up on that... Can't remember.
This:
1 Like
No, webhook
You should receive event on reboot too. Which connection did you use? (webhook or websocket)
Did you receive it with the fake systemStart event?
If you still have issue, then activate debug log and send me the log after a reboot test. We should see exactly what is done
1 Like
Weird, the only reason I can see, is that driver doesn't send this information
You can activate debug log in NR, and see exactly the event received by the webhook
But the device node doesn't make much processing on the event received ... so it should be not different
Maybe you have another device to test it?
1 Like
@erktrek is right. Was added in 2.2.0, so if you don't see it, you have another/different problem.
Definitely working for me on the current hubitat firmware and current node-red nodes on a DEVICE node. I did not try it on an EVENT node (EDIT: I did not, and type is on there too):
4 Likes
Now I'm really confused because it shows as expected now.
Yesterday I selected the "switch" attribute and the property was not coming through. Just now I tried the "all" attribute and it showed up as expected so I then selected the "switch" attribute and it shows up there as well. I must have done something different than I'm remembering.
My apologies to all for wasting bandwidth, time, and effort. I'll show myself out.
EDIT: I just tried websocket and got the results like yesterday so I probably had selected that by mistake. Senior moment. 
3 Likes
No worries! Glad it is working!
2 Likes
I just tested in my live and test node-red instances and the systemStart event is being published by the Event node and the Location node, so now I'm really confused as to why I wasn't seeing this before. I put logging at "debug" level in my test instance and saw that it was published. I then turned the logging level back to "info" and it was still published. Then I tested the event node and location node in my live node-red instance (without turning on debug) and confirmed that both nodes again published the events.
I now have to figure out why my logging database is not seeing the event. Sorry about the confusion.
UPDATE: Figured it out - in my logging flow, I am filtering and suppressing a "null" displayName. All the other events have a displayName attribute but the systemStart event does not.
@fblackburn - Is there any value to adding something in the displayName attribute? Currently, the location event "sunrise" or "sunset" have "sunrise" or "sunset" in the displayName attribute and hence were being logged. If it doesn't make sense, I will modify the flow to account for this event.
1 Like
Aah it's nice you figure it out 
Well displayName is not populated from NR, but come from HE directly. If you want to have a value in this field, you should make a request to Hubitat's team. But it's easier to update your flow, I guess 
3 Likes
Yep 
- thanks for the quick response.
UPDATE: Thanks to @thebearmay for the hub details driver, I fixed the flow to populate the Hub Name (location.hub.name) in the payload.displayName. It's the driver that keeps on giving:-)
2 Likes
I have a weird situation I’m struggling to diagnose. I have an event node which isn’t receiving events from one device.
Here’s what I’ve tried:
- make sure it’s enabled for the node-red maker api
- check that it’s available from the device drop down in a device node
- add a debug and trigger a device event (turn on/off/whatever)
I’m not sure why the one device isn’t appearing to transmit events. Any suggestions from the crowd?
Have you tried turning on Maker API debug and see if it shows as sending events for that device?
Have you tried restarting the Hubitat in question and NodeRED?
Try a device node for that device and check the "send event" property in that node. Also, what @aaiyar said - restarting node-red may fix it.
After some tinkering, what I can see is that the device (a bulb) isn’t sending events of a certain type. It’s sending color messages, but not switch messages. I believe this has to be a habitat issue..I think I’m going to have to delete and re add the bulb.
Restarting the habitat and the node-red servers didn’t change anything, but it was a good reminder!
2 Likes
Maybe try a different driver? I am not sure if device drivers are responsible for events but worth a shot.
2 Likes
I’m sure that they are. In this case I’m using the same driver and settings across several devices, and only one of them is broken.
2 Likes
