Closed jontofront closed 1 year ago
EcoNet version has been already added on dev branch, so it will be available once the dev is merged. As for the rest versions I'm not sure how they should be integrated into HA, perhaps as attributes? I am not sure, but I will think about it.
I try to fnt in google documentation about econet keys, check what I found: https://github.com/denpamusic/PyPlumIO/blob/main/pyplumio/const.py
I try to fnt in google documentation about econet keys, check what I found: https://github.com/denpamusic/PyPlumIO/blob/main/pyplumio/const.py
This is from the library where you originally created a request for ecoNET300 support, but that library provides support for devices that communicate via RS485 where the communication layer is designed to use binary data rather than the text data like it is in the case of ecoNET300 where we have just a rest API exposing some data in textual (json) form.
It can be add in there
I will probably add it, actually I have already done it, it's on the dev branch together with other changes but I will probably create a separate PR for this purpose. However, I think that I will limit it only to ecoNet fw version, otherwise it would result in multiple devices being registered in device registry in Home Assistant and we don't want it.
http://x.x.x.x/econet/sysParams
Controller
controllerID: "ecoMAX810P-L TOUCH"
Controller software versions Module ecoNET version:
softVer: "3.2.3819"
Module A version:moduleASoftVer: "8.30.176.R1"
Module Panel version:modulePanelSoftVer: "8.11.42"
Module B version:moduleBSoftVer: "1.30.7"
Module Lambda version:moduleLambdaSoftVer: "3.2.7"