I have been maintaining support for a custom component I wrote about a year ago to control my Mitsubishi AU/NZ HVAC via the built in ECHONETLite protocol. This consists of the custom component and the underpinning Python library.
Now in theory this custom component in its present state should work for any HVAC device that has support for the ECHONETLite protocol and I believe quite a few Japanese branded HVAC systems such as Panasonic or Daikin may support this protocol too.
Also, the ECHONETLite protocol itself has support for a myriad of device categories, all kinds of crazy sensors, water heaters, washers, dryers etc etc⊠I would be interested to know if anyone has ECHONET enabled devices.
I would like to see if anyone using non-Mitsubishi ECHONETLite enabled HVAC systems, or any other devices out there, are able to use the library. The idea is that I might continue to work on this project until support for the ECHONETLite protocol becomes a core component of Home Assistant.
Bit of a resurrection here, but Iâm currently building a house in Japan that will be using panasonic aiseg2 for things like solar production, energy usage and also my air conditioner. As far as I can tell aiseg2 is compatible with ECHONETLite and I would love to be able to get read outs on energy consumption and such into home assistant, so if youâre still working on this and need help testing, let me know (still a few months off the house being completed though)!
I havenât played around with it for a few months. My recommendation would be to set up a python CLI environment and then run the âmitsubishi_echonetâ discovery function. The example script has a few ideas.
Basically every ECHONET class in theory could be supported but none of the classes outside of HomeAirConditioner are coded. You would have to work out which classes your devices belong to and then use the specification document to fill in the gaps. You might even need to create new classes inside the library.
I would suggest that forking the library and messing about with it would be the way to start. the âdev-2â branch was an attempt to rework the original code into something that was a bit more extensible and generic but i lost interestâŠ
I have some Panasonic AiSeg stuff and finally had some time to hack on Scottâs library, I can read out solar and battery metrics from my PowerStation S+:
Discovering Anything..
Supported instance discovered at 10.0.0.1 - Home solar power generation class
Supported instance discovered at 10.0.0.1 - Storage battery class
{'status': 'On'}
{'cumul_power': 1632084}
{'instantaneous_power': 461}
{'status': 'On'}
{'remaining_electricity_3': 22}
{'working_operation_status': 'Standby'}
Some notes:
My PowerStation is connected via ethernet to local network
It does not seem to reply to multicasts, so I overrode ENL_MULTICAST_ADDRESS with the IP address of the PS
I did the absolute bare minimum to get this to work, code is by no means maintainable or reliable (no error checking, crappy naming, whitespace errors, etc.)
I plan on integrating with HA eventually, but I think some work is required to refactor the existing library (in fact, I just now saw that Scott started this in a new branch) to make it easier to add to and maintain. I donât have much free time so I hope this PoC is enough to get you or others going.
I have just started looking into what I can grab from my housemaker (äžæĄć·„ććș)'s HEMS.
They have this æ ć ±ćéăŠăăă(Info gathering unit, which I guess just means HEMS unit) which is made by Mitsubishi: https://echonet.jp/introduce/gz-000156/. It has itâs own Wi-Fi AP that other devices connect to, and is connected to the internet via my home network (hard wired). Using the housemakerâs android app you can control your aircon, see your power usage and/or solar power situation.
My Mitsubishi aircon was connected to that unitâs WiFi AP via the HM-W002-AC adapter. I paired the aircon with my home network instead and was able to grab info from it using Scottâs repo, so cheers for that @scotty !
Next I tried querying the HEMS unit but got this response which seems like it isnât going to be useful:
eojgc: Echonet group code = 5
eojcc: Echonet class code = 255
eojci: Echonet instance code = 1
0x05 corresponds to âcontroller classâ according to the ECHONET docs (link to the PDF posted by Scott previously), but canât spot anything interesting there.
Controller class looks like a manager of other ECHONETlite devices. Looks like you can query a whole bunch of stuff based upon index value (set EPC 0xC2)
If you are interested, we can look at integrating this controller class into the âpychonetâ library. the library has had a major update and use asyncio now.
Hmm, those commands donât show up in the property map. To be honest I hardly understand the ECHONET spec at the moment but I believe it should be listed if it was callable? The âmandatoryâ column is blank in the spec so I guess they didnât bother implementing it?
After sniffing the packets to/from the controller, it looks like the only echonet device I can access over the home network is my aircon. The smart meter/solar stuff is using Wi-SUN (920MHz) and the dongle are plugged into the controller which doesnât expose anything on its echonet interface. I guess I could try taking the dongle and using it on my PC.
