Just wanted to share - I have Helios device with the EasyControl 3.0 controller.
The controller does not provide ModBus data over TCP as the older versions did, only through WebSocket.
I reverse-engineered the protocol from the javascript sources and created small utility in nodeJS that creates unique HomeAssistant MQTT device for the Helios (based on its serial number) and supplies it with key parameters every 60 seconds.
At the moment I am running the code on another machine in my network that is permanently on, using GNU screen to keep it in the background with auto-start using cron. However, for future, I’ll look into how to write own integration (possibly using HACS) and I might transform it.
Should anyone be willing to help with the effort or just to provide general suggestions, I am more than happy to receive inputs!
@sanchosk : Thank you for your effort! Very cool! What a weird protocol…
Based on your work I am planning on creating a homebridge/homekit integration. Have you figured out how to change the device state? I am guessing that we have to set VlxDevConstants.EXT_CYC_ACTIVE_PROFILE?
To be honest, I did not even try, I was aiming at read-only thing, but I can take a look, should not be that difficult to reverse-engineer that part of code
As I don’t know how to integrate, my dev roadmap is more or less at the end for now. The git repo is linked in the first post - feel free to provide some PR, I’ll be happy to test and help as much as I can…