I use the Maker API from a completely separate application that is much richer than Hubitat can provide. Introducing RoboDomo
I was polling getAllDevices() once per second and rebooting the hub every few days when it crawled or stopped altogether. I went to every 2 seconds, but that barely helped.
Why poll so fast? If you turn off a switch manually, you want to see the tile in the UI change state quickly or the whole thing feels sluggish from the lag.
Bugs/suggestions:
The post endpoint solves the need to poll. But some z wave devices do not report state change on manual change, so the need the z wave poller, which adds some lag but beats having invalid state.
I can’t use poller for fans, only switches and dimmers. This seems like an oversight.
I don’t think you can set up the post API to work with multiple endpoints. A better WebSocket API would be ideal.
I don’t think there’s a way to unset the post API endpoint.
Maker API should let me post an array (JSON) of devices and states so I can send such an array to turn off 35 of my 50 things with one http request.
I want an arrival or geofence for each person and each vehicle. Any hubitat solution would be ideal, but I am looking at putting a Bluetooth device in each vehicle and polling for Bluetooth devices from a Linux system to determine if the device (vehicle) is in range. Not sure if hubitat has BT hardware, it would be the win.
