Agreed, presumably web sockets has a much lower overhead (since it's already doing it anyway and an extra client is just a subscription on the socket) compared to having to do a HTTP POST for every event.
I actually just moved my own integration from the old ported ST MQTT/REST plugin (Hubitat MQTT Integration) to a web sockets and maker api equivalent for this reason. It would seem a step back to revert to a http post version .....
