That sounds exactly like what I would want to do albeit on single phase only.
I’ve read (limited research so far) that only some inverters support local API, is this the same thing you have enabled or something else?
I believe the modbus interface is separate to the local API. The modbus seems to be primarily intended for linking multiple inverters.
See my answer to “dazza25” for more details.
The document in which I found details of how to enable the TCP Modbus interface is called:
“sunspec-implementation-technical-note.pdf”
It should be easy to find.
That doc explained how to access the setup menu used to enable TCP Modbus. Please note, accessing that menu required using buttons inside the inverter, with the cover off and power on. Danger!
The HA side is a python script and support files that is loaded into a “custom_components” dir.
See here:
This is the script I am using. There are other versions or derivatives that may be better.
One issue I have found is that the python script does inverter and power monitor reads sequentially from the inverter. This can lead to problems, say in calculating current power consumption from the inverter power generation value and the power meter export value, as those 2 values don’t update at the same time. I can write python so will update my copy of the script soon to avoid this issue.
1 Like
Thanks very much.
I’m assuming you have a genesis inverter?
I’m being quoted for both genesis and energy hub with less than $500 difference however I doubt the genesis quote includes the extras I’d need like consumption monitoring and enhancement package. I think that comes standard on the energy hub.
I’m not sure it is necessary to access the buttons inside, I was able to enable MODBUS using the external ‘P’ switch position following the instructions here:
I note this is a different Home Assistant integration, so there are multiple ways get compile the data, I have also used the generic SunSpec MODBUS integration to access the data.
I have mine running on a 5 second update so get very fine resolution graphics.
THESE ARE NOT CERTIFIED
I was looking for plugs and came across these AU Plugs pre-flashed with esphome and priced reasonably. I ordered 6x and it came about $20 AUD a pop including shipping. There is a 15% black Friday discount going on right now.
1 Like
yes, that is a nice price. Do these plugs support energy monitoring?
Do you prefer the tasmota version or the esphome version? Which is easier ?
Please read the topic title. This product is clearly not certified for use in Australia.
@tom_l sorry, you are right. still someone else may find them useful since there are not many choices these days. Even certified plugs wont be certified anymore once we put a custom firmware on them anyway.
There are no certification tests related to firmware. It is all about physical and electrical tests that prevent electric shocks - creepage distances, case strength, finger probe tests, etc…).
3 Likes
@Chase07450 I bought the esphome version. tasmota version probably need MQTT. I dont think there is energy monitoring in them.
quite obviously there is. Look at the esphome yaml file.
1 Like
I have a Solaredge inverter without a display, and also got Modbus TCP enabled using the instructions in that link, just using the P switch, and can access the data via Python. Home Assistant is next once I get it on a new enough version.
Looking to add smarts to our Daikin ducted and two split system units. Keen to hear experience from those who have used the Airtouch 4 or Daikin’s Airbase - pros, cons, home assistant integration, etc.
I have the Daikin BRP15B61 Airbase. For the most part it works very well.
There are two minor issues I have open for this:
Neither of these issues have prevented me using this for automation (or control via the Lovelace thermostat card). The indoor temperature I take from another sensor and I don’t use the auto fan modes. I leave it on low most of the time with an automation that sets it to mid if the temperature needs a boost (essentially I made my own ‘auto’ fan mode).
1 Like
I have 3 of the Airbase adapters for my multi-head/VRF system. The main annoyance is that due to how multi-head system works, the entire system can only be in either cooling or heating modes, controlled by the primary controller.
This means when I try to change the mode, Home Assistant shows it to be ‘cooling’ but it will be set to whatever mode the primary controller is in. This means if the primary controller is set to ‘heat’ but off, the other room will actually be set to heat rather than cool. And unless the primary controller is in ‘fan’ mode, other units set to fan are limited in speed, so I only get max fan if primary is in ‘fan’.
This is more a limitation of the VRF system (and it’s very annoying), so I’m thinking I’ll need to figure out a scripting mechanism to deal with climate control across the house.
Ideally though, HASS would show the actual mode instead.
1 Like
I’m guessing something like an Aqara Zigbee sensor? What gets exposed to HA via the integration for you? I also have two Daikin separate split systems so need to figure out the best way to get those integrated too.
Would be keen to see your automations for this, sounds very logical.
Are you using the official integration or the HACS one? What gets exposed to HA from the Airbase?
Unfortunately the current ones at Officeworks are not able to be flashed 
Time to crack it open…
I think I need to have a climate template to achieve what I want. I have a bunch of Mi temp/humidity sensors through ESPhome. Very cheap!