Got it. Thanks! I’m now able to get data into HA! Woo!
From your suggestions I started the console in the container and was able to install nano and edit the inverter.conf and mqtt.json files. For anyone looking for them they’re in /etc/inverter (up a folder from where it places you in opt).
I think the big issue I’d been having was how I deployed the container. I tried via ssh, but there was no docker-compose installed on Raspberry Pi OS, and when I tried apt-get, that also wasn’t there. So I tried copying the docker-compose.yaml file into Portainer stacks. But that kept erroring out too, with issues with the volume and devices not being found.
The success I’ve had so far is just adding a container and copying the image link and manually replicating the docker-compose in Portainer. Removing /dev/ttyUSB0 and adding /dev/hidraw0 to my device list seemed to help. I still can’t get the ./config:/etc/inverter volume to work, it wants absolute paths and I think there’s also permission issues.
But, data from the inverter has got to HA, so that’s a huge step forward after banging my head into this for a few days.
I installed Portainer separately after running into an error, could that be the cause of what seems like permission errors?
Hi.
Anyone managed to get an axpert 5k working with rs232-ttl with esphome?
Ive tried to make 2 rj45-ttl adapters using the micro rs232-ttl converters. but just keep getting the following error
[13:13:40][D][pipsolar:757]: timeout command to poll: QPIRI
[13:13:40][D][pipsolar:840]: Sending polling command : QPIRI with length 5
Im presuming there is an issue with the cable.
I’ve followed the cable pinouts from here
I could not get this to work when running HA in the preferred setup under HassOS.
I ended up doing a fresh install of Debian on my Pi then running a supervised installed of HA in docker on that and this project in its own docker.
This project appears to be running, as I can see entities for inverter info in HA, but there’s no data for me yet (as I chase a different issue with communication with the inverter).
Note that by standing this up in docker alongside HA, that makes my HA install “unhealthy” and unsupported. I have had to stop this stack to update HA core when updates are available, but otherwise it seems fine. It was a fair bit more work than just running HassOS though, but I haven’t touched Linux in 20yrs,
Would someone have an updated firmware for an mpp solar 10kw/Hybrid inverter. the firmware now is Main FW version: 00001.01 ?. Sry for asking for this here. But from what i can read is more realisable with the newest firmware. Kind Regards Michael
InfiniSolar 3P 10kw
I needed the app to read my mpp solar inverter (PIP 5048 GK) using a raspberry pi zero via USB, the docker stuff and all were to heavy, I rewritten a mono app that suits my need feel free to have a look and maybe contribute.
I only have 1 MPPT does the documentation tells how to read both ?
I found all details for mine in product-application_pdf-20190724092401-8519-pip-gk-mk-protocol.pdf
Hi Mark, Sorry I know this dates back some time but a quick question. Is there anything else specifically you needed to do to get all the paralleled inverters to pull the entities for each into HA via MQTT ? I have the same as yourself with giving each container a different MQTT devicename and specified hidraw0,1,2 for the 3 inverters. If i go to the MQTT listener in HA I can see the topics for each but for some reason it will only display the 1st inverter entities (hidraw0). Does the Client ID being the same across the 3 containers matter ?
Hello @henry.joubert, were you able to send MUCHGC002 command in to the inverter please? I’m fighting with the same issue. It seems that it’s possible to send comands into the inverter up to 5 charracters so for example POP00 or PCP01 will work correctly and inverter is understanding, but whenever I’m trying to send some longer command, It’s not working. In my case I’m trying to change operation logic of inverter using command POPLG02
POPLG<nn><cr>: Setting operation logic (Only for KING)
Computer: POPLG <nn.n><CRC><cr>
Inverter: (ACK<CRC><cr> if Inverter accepts this command, otherwise, responds (NAK<CRC><cr>
nn:00: automatically, 01: On-line mode, 02: ECO mode