UPDATE:
I apologize for not providing any updates on the WebSocket issues. I started working on changes over a month ago when Amazon killed the web-based WebSocket. I've found someone who has decoded the WebSocket that the amazon devices use. The issue is that in order for this to work I would have to port it over from Javascript to Java which in most cases is simple :|. But it's not simple when working with crypto and binary functions. The other issue is the libraries that are allowed on Hubitat. I was going to port over the code to the echo speaks server but that would cause Heroku over usage so I'm trying to find an alternate option.I've been entertaining creating a docker image that users can run on a home system that basically combines the current server and uses the javascript WebSocket library and just sends messages to the ES app when there are device changes thus eliminating the WebSocket device completely.
The problem is that many of you don't have servers and systems sitting around running 24 hours a day.
This was the sole reason I created the Heroku version of the server.
I realize some of you will be all-in on a new all-local version, but I need to take into consideration the time it takes to develop (I don't have as much free time any more so it's hard to work on these projects)
I would love to hear your thoughts on how important real-time volume and device status updates are to you!!!
