You can use 2 device nodes (on the same device ID) linked to a debug node and use each kind of configuration (webhook and websocket) for each device node. Then look the difference between timestamp when you receive an event. I think the debug node doesn't print seconds in the timestamp, but you can add an extra node between device-debug to add seconds
FYI that on v1.4.0 initialization works differently. I notice that after a node-red reboot my device nodes don't show current value until after they update one more time.
e.g. - notice the device nodes show no status underneath. This is a few minutes after a node-red reboot:
After the device updates, things look normal again (1 device updated):
You might need to explain further on what your issue is though. Saying you are getting "unexpected results" probably doesn't help francois understand what is broken.
The only thing I see is purely cosmetic - the status text on device nodes. Everything else seems to be working as expected for me (a couple things I thought were broken was something else I messed up that didn't relate to the 1.4.0 update).
As you can see, the value is not showing under my Life360 device after NR restart. This inject node runs .1 seconds after reboot, yet it fails on the James path, literally the msg stops after going through the device node. My wife's showing because she was actually driving/ changing the value.
.1s after reboot? I'm surprised they don't all fail.
I wait typically no less than 10s reboot before triggering flow updates. It takes a bit of time for the Hubitat nodes to initialize after a node-red (or Hubitat) restart.
Just want to call out that this was working before the NR HE release. Also, if I'm simply querying for status shouldn't it pull from the NR HE device cache? I guess the cache is building at startup, maybe that is the problem...
UPDATE: changed inject node to run after 60 seconds, it now works. I think HE NR node was building the cache as I was querying and it was failing.
According your setup/configuration/devices/hub/etc... the cache can be longer to build than before. You can look at the NR log to see the time needed for initialization and set your init offset according the result.
But it should not take more than a few seconds
I'm not sure I understand what you're looking for. You can build the equivalent of the Hubitat thermostat scheduler app, or even the new thermostat controller app, using the built-in nodes in conjunction with the hubitat nodes.
Is there a way to catch the event of opening a smart lock using a pin? What I would like to do is set HSM to intrusion disarm from alarmed away when a smart lock is opened pin.