I ran into this problem today as well. I’m just starting out on my home automation journey and have written a small python hack that is running on a raspberry pi. This hack does two things by listening to the events sent by the heart through the websocket connnection:
- Acts as a relay to control my Rusta/Sartano/Kangtai 433Mhz sockets that are not (yet?) supported natively by the heart.
- Stores all measurements to an influxdb database so that I can visualize measurements over time using chronograf and Grafana
Before today, I didn’t have that many devices generating that many messages, so I managed to stay under the 7000 messages per 24 hour limit. But today, I received my espresso machine with a PID controlled boiler. The PID control ensures a stable temperature in the boiler with short bursts of electricity to the heater element. This generates a lot of messages from the smart socket and after a couple of hours, I had hit the message limit .
I completely agree with Jon that this limit makes the websocket API pretty much useless. I understand the need for a request limit for cloud messages to reduce the risk of overloading the cloud service, but for messages within my local network, this limit makes no sense at all to me. Especially considering that these are messages sent by FROM the heart. Also, ping messages shouldn’t be counted since they are required to keep the connection open. (actually, the ping messages are completely unnecessary since there is support for ping messages in the websockets protocol that the heart does respond to, but seems to ignore since it closes the connection anyway, but I wrote about this in a separate thread)
The API request limit for requests within my own network, at least as it is right now, feels in my opinion completely arbitrary, artificial, useless and quite frankly super frustrating…