However , got a few questions!
I am having a problem with updates to device status on flows. Say, I start a sonos player, it correctly shows the status from "stopped" to playing, but all downstream nodes connected to the sonos player assume its off. I have to mostly restart the flow to get the correct status propagated. What could be causing this? My node-red is hosted on an ubuntu vm with 4 gb ram. I have tried refreshing the webhook connection in the config - seems to work for a while and the problem comes back.
Is there a way to process commands sent back to hubitat devices in a batch and sequentially ? Something along the lines of first do this, and then that etc ... I have seen others use the delay button and chain nodes together. Is that the de facto way of doing this or is there a better way ? Just to reduce the visual clutter. I saw this (do-red (node) - Node-RED) and was wondering if that's the way to go ?
For non-zwave devices without dnla support to help with status updates, is constant polling of the device the only way to get its status ? ( related to #1 above ). Is constant polling good or bad?