Just pay attention to the differences between the two...
websocket
- gives you events for all devices, not just the ones selected in Maker API.
- ws does NO deduplication of events (aka you could get multiple present/on/etc events in a row when using the ws connector). So you could get things triggering that wouldn't if you use webhook. Whether this is important or not depends on your logic and devices.
- ws is unsupported by hubitat and could go away at any time (although it hasn't in > a year it has been in there).
- ws events have slightly different data than webhook (no type - 'physical'/'digital' for one).
- ws is a little faster than webhook.
- ws requires less configuration - just the IP of the hub
Webhook
- officially supported by Hubitat
- events have more details in some cases (type, and a few other items)
- only sends events for devices specified in maker api
- sends events post-internal deduplication, so events sent should match the events in a device history log
- requires a little more config (have to configure the POST url in maker api)
