burleanu

Here are the file I currently use, I add a little readme file to know how to set in the console of tasmota. readme.txt This will give the option to be able to access via TCP. Also I think the ready made tasmota-zbbrige firmware have already build in the TCP. Mine is already one year old. For test if you don't have home assistant and also if you want to see all the registers you can use a software call " Radzio! Modbus master simulator" https://en.radzio.dxp.pl/modbus-master-simulator/ After you set up your tasmota then this Radzio software can connect to it via "Modbus RTU over TCP/IP" and there you set the IP and port and after you can connect. Inside this you have to specify what registers you want to access and at what address. For example for me "holdings registers" at address 200+ I can see all the important values I need, you can see it in my first photo. Also if you have HA you have the example how to setup HA to read them over TCP in one of my photo. Once you have tasmota you can flash esphome over and use the other function pongo use and build yours like that, if you use HA. LE: I look again and see that you use Node-Red so you can add the needed parameters inside Node-Red because I see they have a "package" for modbus and is able to read over TCP. So you just need to know what registers you need and add them in. tasmota-zbbridge.bin

Hello, I'm not home right now to see were is the file I had compiled but you can take a look at this https://tasmota.github.io/docs/Serial-to-TCP-Bridge/#commands And there you can compile your own one to support TCP and afterwards you can create the sensors accordingly else you can take the route of @pongo and use it via esphome if you have HA and you know how to do it. Good luck. LE: This way you can just read the values that you configure in the script. (Still need to be complied) https://tasmota.github.io/docs/Smart-Meter-Interface/

Indeed it is not that hard but I did get lost on the part with writing registers. For example the value of the battery or the charging priority or the SBU and SUB modes. That I didn't know how to make it. Via TCP with the help of tasmota I was able to get it work with the default integration in HA and I can change it easier IMHO.

Hello, That's s is how I did configure my tasmota. Have you compile your own tasmota? Because the default doesn't have the modbus implemented. Take care mine is acting as gateway for modbus-rtu and need to create a script in start up to run to activate the port and baud rate for the device to work.

If you plan to use esphome then definitely you can try to flash the dongle if you have one, but is a lot of work to do it in esphome. You can back up the content in case you want to but I think after you get it work you will not want to go back. In my case like I din used tasmota and the dongle became a true gate to have modbus over the Ethernet (modbus-rtu) and everything happens in HA where I created all the sensors accordingly. As bonus I even used the build in LED for statuses. LE: I forgot to tell you that my dongle have implemented inside something that it make it restart after a 1 minute. Probably is waiting for an output from the esp but I didn't know witch one so I bypass the power supply with a wire 🙂

In the picture you can see the inside of my WiFi module. You can open it up and see if is same like mine because I see are different types, don't know how they are inside. The chip used in mine is esp07, so you can find on internet the pinouts and front there you can make it further like on any esp model..... you even have exposed the pins for Rx and Tx, with a flasher for an esp01 or other adapter for USB to TTL you can flash it easy. In the first photo you can see the software used to find the registers, that I was using to see the registers until I got the protocol used.

Hello all, In case is not too late and you didn't abandon the project I can confirm that the above protocol is the one used. After many nights spent to reverse-engineering I was able to attach it to my Home Assistant and indeed it does use modbus protocol. I wish I knew the protocol before starting to sniff the data send between the dongle and the invertor. Like that I didn't had to spend that many nights to discover what they "talk". Anyway I'm happy I was able to add it to my HA instance and now I can control it like it is with his own dongle. I was using a MAX3232 and an ESP8266 flashed with Tasmota (custom version to support ModBus). Also during the time I was sniffing the communication I also discovered that even the WiFi Dongle use the same ESP8266 chip. Now their dongle is flashed with that custom Tasmota firmware and I read the data via modbus-rtu with Home assistant. With tasmota firmware you have two options: - one is just to read and show directly the needed values but this is just read only (at least this is what I was able to do). - the other one is to make it work with same tasmota via modbus-rtu over the network and the values you read directly with Home Assistant and this allowed me also to change the modbus registers and this way can be controlled like with the original software/dongle. Also after many days spent then I also find who made this model of inverter (from them I did get same file for protocol like the above). My finding (at least at that time) was that it is produced by JSD-Solar model Glory M5000 HHP-48. Now I don't see anymore on their website but if you search for the model name you can find it. Mine is also from Easun but they didn't want to help me with the protocol. Also on Easun it looks like that the model that have SMG in the name are the one with modbus protocol comunication. I did look in the manual of the new version (5.6KW) and I see is the same like mine and at the menu 25 is the parameter for the modbus Node ID the same like the older version at 5Kw. B.R.