Easun IGridSV-IV5.6KW + USB + raspbery py 3 -inncorect buffer start stop bytes
I did not modified inverter.conf due to the fact that I try now with USB cable(my only available option)
Should I use
qpiri=103
qpiws=56
qmod=5
qpigs=110
This is my firmware versions:
Main CPU Firmware Version: 005600
Secondary CPU Firmware Version: 08025
I think there is an error on the script about the “Battery redicharge voltage” variable.
I noticed it’s always 0.
An input from my inverter is like this one:
230.0 15.6 230.0 50.0 15.6 3600 3600 24.0 25.5 24.0 29.2 28.5 2 010 040 0 2 2 1 01 0 0 27.0 0 1
the battery redicharge voltage is the “27.0” value near the end of the line.
So I checked the main.cpp file and the line which (I suppose) makes the scan:
sscanf(reply2->c_str(), “%f %f %f %f %f %d %d %f %f %f %f %f %d %d %d %d %d %d - %d %d %d %f”, &grid_voltage_rating, &grid_current_rating, &out_voltage_rating, &out_freq_rating, &out_current_rating, &out_va_rating, &out_watt_rating, &batt_rating, &batt_recharge_voltage, &batt_under_voltage, &batt_bulk_voltage, &batt_float_voltage, &batt_type, &max_grid_charge_current, &max_charge_current, &in_voltage_range, &out_source_priority, &charger_source_priority, &machine_type, &topology, &out_mode, &batt_redischarge_voltage);
Assigning values to each variable they are correct at the beginning.
They are the final ones:
…
&batt_float_voltage, 28.5
&batt_type, 2
&max_grid_charge_current, 010
&max_charge_current, 040
&in_voltage_range, 0
&out_source_priority, 2
&charger_source_priority, 2
&machine_type, 1
&topology, 01
&out_mode, 0
at this point the script has only 1 missing variable:
&batt_redischarge_voltage);
but the data from the inverter still have 4 values to assign:
0 27.0 0 1
so the script assigns 0 to the &batt_redischarge_voltage, while the following variable (27.0V) is the correct one.
It’s correct? Maybe the problem is only about my inverter?
Any idea to fix it?
Thank you
Michele
Thank you. I did it, and now I receive all data.
Unfortunately, when I send commands to the inverter, all replies now are “NAK” (before all were working and correctly replied “ACK”).
EDIT: PCP and POP work (ACK), while PBDV and PBCV do not (NAK). Before both were working.
What did you do…?
PBCV25.5 for example have 8 characters+crc witch on original repository do not support on usb connection. Maxim of 5 characters it is possible. On my fork it is solved.
docker exec -it voltronic-mqtt bash -c ‘/opt/inverter-cli/bin/inverter_poller -d -r PBDV27.0’ for example.
Mon Jun 27 16:15:46 2022 INVERTER: Debug set
Mon Jun 27 16:15:46 2022 DEBUG: Current CRC: 50 63
Mon Jun 27 16:15:46 2022 DEBUG: Send buffer hex bytes: ( 50 42 44 56 32 37 2e 30 50 63 0d )
Mon Jun 27 16:15:46 2022 DEBUG: 8 bytes written, 8 bytes sent, 3 bytes remaining
Mon Jun 27 16:15:46 2022 DEBUG: 3 bytes written, 11 bytes sent, 0 bytes remaining
Mon Jun 27 16:15:46 2022 DEBUG: 7 bytes read, 7 total bytes: 00 28 4e 41 4b 73 73 0d
Mon Jun 27 16:15:46 2022 DEBUG: Found reply at byte: 7
Mon Jun 27 16:15:46 2022 DEBUG: PBDV27.0: 7 bytes read: (NAK
Mon Jun 27 16:15:46 2022 DEBUG: PBDV27.0 query finished
I have USB cable adapter with serial.
The output for one MPP Solar U5648MS is every time 0 for “PV_in_watts” and “PV_in_watthour”.
What can I do to have this values also?
INVERTER: wattfactor from config is 1.01
{
“Inverter_mode”:3,
“AC_grid_voltage”:222.0,
“AC_grid_frequency”:49.9,
“AC_out_voltage”:222.0,
“AC_out_frequency”:49.9,
“PV_in_voltage”:273.1,
“PV_in_current”:0.3,
“PV_in_watts”:0.0,
“PV_in_watthour”:0.0000,
“SCC_voltage”:0.0000,
“Load_pct”:7,
“Load_watt”:351,
“Load_watthour”:2.9250,
“Load_va”:421,
“Bus_voltage”:412,
“Heatsink_temperature”:36,
“Battery_capacity”:0,
“Battery_voltage”:2.00,
“Battery_charge_current”:0,
“Battery_discharge_current”:0,
“Load_status_on”:1,
“SCC_charge_on”:1,
“AC_charge_on”:0,
“Battery_recharge_voltage”:46.0,
“Battery_under_voltage”:42.0,
“Battery_bulk_voltage”:56.4,
“Battery_float_voltage”:54.0,
“Max_grid_charge_current”:30,
“Max_charge_current”:60,
“Out_source_priority”:1,
“Charger_source_priority”:3,
“Battery_redischarge_voltage”:-0.0,
“Warnings”:“000000000000000000000010000000010000”
}
you could try my fork.
Hi,
similare issue for me, warnings returns this: 
Voltronic VMIII 50000W, firmware U1:47.00, U2: 02.70, U3: 00.24
Did anybody find a solution for it?
Thanks for everyone who’s contributed to this. Just tried the @catalinbordan fork and was quickly able to get data into Home Assistant right as the sun was setting. Saw PV data streaming in and it was great.
Now that the sun is down, I wanted to see the load data. Turned on my inverter via the switch (usually is off to only run the mppt side of things), and doesn’t seem to show load info. It says 0, but I’m definitely charging my computer from it right now. Any idea why load data might not be working? It’s a PIP1012LV-MS and using the USB cable from it into the pi.
*Note, I didn’t look at my inverter serial number and thus didn’t change it in mqtt.json, but I assume that doesn’t effect anything other than a label…
sudo docker exec -it voltronic-mqtt bash -c ‘/opt/inverter-cli/bin/inverter_poller -d -1’
pi@betty:/opt/ha-inverter-mqtt-agent $ sudo docker exec -it voltronic-mqtt bash -c '/opt/inverter-cli/bin/inverter_poller -d -1'
Wed Jun 29 03:50:41 2022 INVERTER: Debug set
Wed Jun 29 03:50:41 2022 DEBUG: Current CRC: 49 C1
Wed Jun 29 03:50:41 2022 DEBUG: Send buffer hex bytes: ( 51 4d 4f 44 49 c1 0d )
Wed Jun 29 03:50:41 2022 DEBUG: 7 bytes written, 7 bytes sent, 0 bytes remaining
Wed Jun 29 03:50:41 2022 DEBUG: 8 bytes read, 8 total bytes: 28 42 e7 c9 0d 00 00 00
Wed Jun 29 03:50:41 2022 DEBUG: Found reply <cr> at byte: 5
Wed Jun 29 03:50:41 2022 DEBUG: QMOD: 8 bytes read: (B
Wed Jun 29 03:50:41 2022 DEBUG: QMOD query finished
Wed Jun 29 03:50:41 2022 DEBUG: Current CRC: B7 A9
Wed Jun 29 03:50:41 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 47 53 b7 a9 0d )
Wed Jun 29 03:50:41 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Wed Jun 29 03:50:41 2022 DEBUG: 8 bytes read, 8 total bytes: 28 30 30 30 2e 30 20 30
Wed Jun 29 03:50:41 2022 DEBUG: 8 bytes read, 16 total bytes: 30 2e 30 20 31 31 39 2e
Wed Jun 29 03:50:41 2022 DEBUG: 8 bytes read, 24 total bytes: 30 20 36 30 2e 30 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 32 total bytes: 30 30 30 20 30 30 30 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 40 total bytes: 20 30 30 30 20 32 30 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 48 total bytes: 20 31 33 2e 30 39 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 56 total bytes: 30 30 20 30 34 39 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 64 total bytes: 34 39 36 20 30 30 30 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 72 total bytes: 20 30 30 30 2e 30 20 31
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 80 total bytes: 33 2e 32 30 20 30 30 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 88 total bytes: 30 31 20 31 30 30 31 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 96 total bytes: 30 30 30 20 38 33 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 104 total bytes: 35 20 30 30 30 30 30 20
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 112 total bytes: 30 30 30 77 9c 0d 00 00
Wed Jun 29 03:50:42 2022 DEBUG: Found reply <cr> at byte: 110
Wed Jun 29 03:50:42 2022 DEBUG: QPIGS: 112 bytes read: (000.0 00.0 119.0 60.0 0000 0000 000 200 13.09 000 049 0496 0000 000.0 13.20 00001 10010000 83 05 00000 000
Wed Jun 29 03:50:42 2022 DEBUG: QPIGS query finished
Wed Jun 29 03:50:42 2022 DEBUG: Current CRC: F8 54
Wed Jun 29 03:50:42 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 52 49 f8 54 0d )
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 8 total bytes: 28 31 32 30 2e 30 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 16 total bytes: 38 2e 33 20 31 32 30 2e
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 24 total bytes: 30 20 36 30 2e 30 20 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 32 total bytes: 38 2e 33 20 31 30 30 30
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 40 total bytes: 20 31 30 30 30 20 31 32
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 48 total bytes: 2e 30 20 31 32 2e 38 20
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 56 total bytes: 31 31 2e 39 20 31 34 2e
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 64 total bytes: 36 20 31 34 2e 36 20 32
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 72 total bytes: 20 32 30 20 30 36 30 20
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 80 total bytes: 30 20 32 20 32 20 2d 20
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 88 total bytes: 30 31 20 31 20 30 20 31
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 96 total bytes: 33 2e 33 20 30 20 30 41
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes read, 104 total bytes: 82 0d 00 00 00 00 00 00
Wed Jun 29 03:50:42 2022 DEBUG: Found reply <cr> at byte: 98
Wed Jun 29 03:50:42 2022 DEBUG: QPIRI: 104 bytes read: (120.0 08.3 120.0 60.0 08.3 1000 1000 12.0 12.8 11.9 14.6 14.6 2 20 060 0 2 2 - 01 1 0 13.3 0 0
Wed Jun 29 03:50:42 2022 DEBUG: QPIRI query finished
Wed Jun 29 03:50:42 2022 DEBUG: Current CRC: B4 DA
Wed Jun 29 03:50:42 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 57 53 b4 da 0d )
Wed Jun 29 03:50:42 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Wed Jun 29 03:50:43 2022 DEBUG: 8 bytes read, 8 total bytes: 28 30 30 30 30 30 31 30
Wed Jun 29 03:50:43 2022 DEBUG: 8 bytes read, 16 total bytes: 30 30 30 30 30 30 30 30
Wed Jun 29 03:50:43 2022 DEBUG: 8 bytes read, 24 total bytes: 30 30 30 30 30 30 30 30
Wed Jun 29 03:50:43 2022 DEBUG: 8 bytes read, 32 total bytes: 30 30 30 30 30 30 30 30
Wed Jun 29 03:50:43 2022 DEBUG: 8 bytes read, 40 total bytes: 30 fe 82 0d 00 00 00 00
Wed Jun 29 03:50:43 2022 DEBUG: Found reply <cr> at byte: 36
Wed Jun 29 03:50:43 2022 DEBUG: QPIWS: 40 bytes read: (00000100000000000000000000000000
Wed Jun 29 03:50:43 2022 DEBUG: QPIWS query finished
Wed Jun 29 03:50:43 2022 DEBUG: Start loop
INVERTER: ampfactor from config is 1.00
INVERTER: wattfactor from config is 1.00
{
"Inverter_mode":4,
"AC_grid_voltage":0.0,
"AC_grid_frequency":0.0,
"AC_out_voltage":119.0,
"AC_out_frequency":60.0,
"PV_in_voltage":0.0,
"PV_in_current":0.0,
"PV_in_watts":0.0,
"SCC_voltage":13.2000,
"Load_pct":0,
"Load_watt":0,
"Load_va":0,
"Bus_voltage":200,
"Heatsink_temperature":496,
"Battery_capacity":49,
"Battery_voltage":13.09,
"Battery_charge_current":0,
"Battery_discharge_current":1,
"Load_status_on":1,
"SCC_charge_on":0,
"AC_charge_on":0,
"Battery_voltage_offset_for_fans_on":83,
"Eeprom_version":5,
"PV_charging_power":0,
"Charging_to_floating_mode":0,
"Switch_On":0,
"Dustproof_installed":0,
"Battery_recharge_voltage":12.8,
"Battery_under_voltage":11.9,
"Battery_bulk_voltage":14.6,
"Battery_float_voltage":14.6,
"Max_grid_charge_current":20,
"Max_charge_current":60,
"Out_source_priority":2,
"Charger_source_priority":2,
"Battery_redischarge_voltage":13.3,
"Warnings":"00000100000000000000000000000000"
}
Wed Jun 29 03:50:43 2022 INVERTER: All queries complete, exiting loop.
1.What it is the protocol code for your inverter?(command for that it is QPI). It should be PI30.
2. According to the manual you have a warning: “LINE FAIL”
QPI returns PI30
Do you know what Line Fail means?
Also, after yesterday’s success, today I can see data using the inverter_poller command directly, but nothing is getting passed to home assistant. Everything says “UNKNOWN.”
pi@betty:~ $ sudo docker exec -it voltronic-mqtt bash -c '/opt/inverter-cli/bin/inverter_poller -r QPI'
Reply: PI30
@Andre_Magro @catalinbordan
Hello, thank you so much for help. I found how to read the data from my inverter Isolar Hybrid 5.5kw. I used catalin’s fork and andres’s set baud rate.
Catalin’s fork and after that this
sudo stty -F /dev/ttyUSB0 sane (to first clean all the settings)
sudo stty -F /dev/ttyUSB0 2400 raw -echo (without the first command this one did not work)
cat /dev/ttyUSB0 (to confirm that data is passing by the rs232 usb adapter)
Thank you very both for help now I can read data from inverter.
Cheers
1.strange, your raw output from debug it is not according manual.
2. do not know, manual do not say…
3. did you do step 8. 1? sudo nano config/mqtt.json (change it with your variables)
Question. Why I have that in warnings, it is number 17 and in manual mean eeprom fault, is it problem or how to fix it.
pi@raspberrypi:/opt/ha-inverter-mqtt-agent $ sudo docker exec -it voltronic-mqtt bash -c ‘/opt/inverter-cli/bin/inverter_poller -d -1’
Thu Jun 30 12:49:01 2022 INVERTER: Debug set
Thu Jun 30 12:49:01 2022 DEBUG: Current CRC: 49 C1
Thu Jun 30 12:49:01 2022 DEBUG: Send buffer hex bytes: ( 51 4d 4f 44 49 c1 0d )
Thu Jun 30 12:49:01 2022 DEBUG: 7 bytes written, 7 bytes sent, 0 bytes remaining
Thu Jun 30 12:49:01 2022 DEBUG: 5 bytes read, 5 total bytes: 10 00 00 28 4c 06 07 0d
Thu Jun 30 12:49:01 2022 DEBUG: Found reply at byte: 5
Thu Jun 30 12:49:01 2022 DEBUG: QMOD: 5 bytes read: (L
Thu Jun 30 12:49:01 2022 DEBUG: QMOD query finished
Thu Jun 30 12:49:01 2022 DEBUG: Current CRC: B7 A9
Thu Jun 30 12:49:01 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 47 53 b7 a9 0d )
Thu Jun 30 12:49:01 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Thu Jun 30 12:49:02 2022 DEBUG: 10 bytes read, 10 total bytes: 32 39 2e 30 20 35 30 2e
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 22 total bytes: 39 2e 30 20 35 30 2e 30
Thu Jun 30 12:49:02 2022 DEBUG: 11 bytes read, 33 total bytes: 38 37 20 30 36 38 36 20
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 45 total bytes: 34 34 39 20 35 34 2e 30
Thu Jun 30 12:49:02 2022 DEBUG: 15 bytes read, 60 total bytes: 30 30 20 30 30 34 34 20
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 72 total bytes: 20 31 36 39 2e 33 20 30
Thu Jun 30 12:49:02 2022 DEBUG: 11 bytes read, 83 total bytes: 30 20 30 30 30 30 30 20
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 95 total bytes: 30 31 31 31 20 30 30 20
Thu Jun 30 12:49:02 2022 DEBUG: 11 bytes read, 106 total bytes: 30 30 36 30 38 20 31 31
Thu Jun 30 12:49:02 2022 DEBUG: 4 bytes read, 110 total bytes: 38 20 31 31 30 a9 5f 0d
Thu Jun 30 12:49:02 2022 DEBUG: Found reply at byte: 110
Thu Jun 30 12:49:02 2022 DEBUG: QPIGS: 110 bytes read: (229.0 50.0 229.0 50.0 0687 0686 012 449 54.00 000 100 0044 03.5 169.3 00.00 00000 10010111 00 00 00608 110
Thu Jun 30 12:49:02 2022 DEBUG: QPIGS query finished
Thu Jun 30 12:49:02 2022 DEBUG: Current CRC: F8 54
Thu Jun 30 12:49:02 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 52 49 f8 54 0d )
Thu Jun 30 12:49:02 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Thu Jun 30 12:49:02 2022 DEBUG: 9 bytes read, 9 total bytes: 32 33 30 2e 30 20 32 33
Thu Jun 30 12:49:02 2022 DEBUG: 15 bytes read, 24 total bytes: 30 20 35 30 2e 30 20 32
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 36 total bytes: 35 35 30 30 20 35 35 30
Thu Jun 30 12:49:02 2022 DEBUG: 11 bytes read, 47 total bytes: 38 2e 30 20 34 36 2e 30
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 59 total bytes: 30 20 35 36 2e 34 20 35
Thu Jun 30 12:49:02 2022 DEBUG: 11 bytes read, 70 total bytes: 20 32 20 32 30 20 30 32
Thu Jun 30 12:49:02 2022 DEBUG: 12 bytes read, 82 total bytes: 31 20 33 20 31 20 30 31
Thu Jun 30 12:49:02 2022 DEBUG: 15 bytes read, 97 total bytes: 2e 30 20 30 20 31 53 bc
Thu Jun 30 12:49:02 2022 DEBUG: 1 bytes read, 98 total bytes: 30 20 30 20 31 53 bc 0d
Thu Jun 30 12:49:03 2022 DEBUG: Found reply at byte: 98
Thu Jun 30 12:49:03 2022 DEBUG: QPIRI: 98 bytes read: (230.0 23.9 230.0 50.0 23.9 5500 5500 48.0 46.0 44.0 56.4 54.0 2 20 020 0 1 3 1 01 0 0 54.0 0 1
Thu Jun 30 12:49:03 2022 DEBUG: QPIRI query finished
Thu Jun 30 12:49:03 2022 DEBUG: Current CRC: B4 DA
Thu Jun 30 12:49:03 2022 DEBUG: Send buffer hex bytes: ( 51 50 49 57 53 b4 da 0d )
Thu Jun 30 12:49:03 2022 DEBUG: 8 bytes written, 8 bytes sent, 0 bytes remaining
Thu Jun 30 12:49:03 2022 DEBUG: 12 bytes read, 12 total bytes: 30 30 30 30 30 30 30 30
Thu Jun 30 12:49:03 2022 DEBUG: 11 bytes read, 23 total bytes: 30 30 30 31 30 30 30 30
Thu Jun 30 12:49:03 2022 DEBUG: 11 bytes read, 34 total bytes: 30 30 30 30 30 30 30 45
Thu Jun 30 12:49:03 2022 DEBUG: 2 bytes read, 36 total bytes: 30 30 30 30 30 45 18 0d
Thu Jun 30 12:49:03 2022 DEBUG: Found reply at byte: 36
Thu Jun 30 12:49:03 2022 DEBUG: QPIWS: 36 bytes read: (00000000000000000100000000000000
Thu Jun 30 12:49:03 2022 DEBUG: QPIWS query finished
Thu Jun 30 12:49:03 2022 DEBUG: Start loop
INVERTER: ampfactor from config is 1.00
INVERTER: wattfactor from config is 1.00
{
“Inverter_mode”:3,
“AC_grid_voltage”:229.0,
“AC_grid_frequency”:50.0,
“AC_out_voltage”:229.0,
“AC_out_frequency”:50.0,
“PV_in_voltage”:169.3,
“PV_in_current”:3.5,
“PV_in_watts”:0.0,
“SCC_voltage”:0.0000,
“Load_pct”:12,
“Load_watt”:686,
“Load_va”:687,
“Bus_voltage”:449,
“Heatsink_temperature”:44,
“Battery_capacity”:100,
“Battery_voltage”:54.00,
“Battery_charge_current”:0,
“Battery_discharge_current”:0,
“Load_status_on”:1,
“SCC_charge_on”:1,
“AC_charge_on”:1,
“Battery_voltage_offset_for_fans_on”:0,
“Eeprom_version”:0,
“PV_charging_power”:608,
“Charging_to_floating_mode”:1,
“Switch_On”:1,
“Dustproof_installed”:0,
“Battery_recharge_voltage”:46.0,
“Battery_under_voltage”:44.0,
“Battery_bulk_voltage”:56.4,
“Battery_float_voltage”:54.0,
“Max_grid_charge_current”:20,
“Max_charge_current”:20,
“Out_source_priority”:1,
“Charger_source_priority”:3,
“Battery_redischarge_voltage”:54.0,
“Warnings”:“00000000000000000100000000000000”
}
Thu Jun 30 12:49:03 2022 INVERTER: All queries complete, exiting loop.
The load output seems to be intermittent. Not sure why, but I would guess something to do with the inverter.
I did do step 8.
After some testing (restarting the container, restarting the pi, changing mqtt.json), it seems I can only get the container to pass along data to home assistant if I go through all the steps, edit the mqtt.json, and rebuild the container. Everything else didn’t change the “unknown” data. But first load after fresh build of the container has data stream into home assistant. Even maintained connection after an overnight where the inverter turns off. So that’s a success.
Is there a way to debug, or walk through the steps of the mqtt side of things? The inverter-cli continually has returned data even when it hasn’t seemed to send it via mqtt.
Good morning. I hope not to bother anyone with my question…
I am a rookie of home assistant I am very willing to acquire data voltronic axpert ad home assistant…
since I’m not good bike I asked you for kindness if you can oientarmi to understand… Can I use an old pentium4 3.2 PC with USB port to capture data and send it over the network?
what software do I need to install docker must be installed u windwos or on linux.
thanks
Hi, can you help with crontab code. To work catalin’s fork I should set baud rate raw, without raw in sudo stty -F /dev/ttyUSB0 2400 raw doesn’t work. And after every reboot I should set baud rate with raw to work. Can you help me to modify your script to seting baud rate 2400 raw after reboot?
Hi, I got everything setup and working with home assistant, but i want to add influxdb. In HA, I have added the user “solar” to influxdb and made a database named “solar”. In the mqtt.json file, I have it enabled and also filled the info in. When everything is started, nothing shows up in the database. I am also using @catalinbordan 's fork.
This is my mqtt.json file.
GNU nano 5.4 config/mqtt.json {
"server": "192.168.0.90",
"port": "1883",
"topic": "homeassistant",
"devicename": "max",
"manufacturer": "Kodak",
"model": "PIP3024MSXE",
"serial": "6969",
"ver": "20.13",
"username": "mqtt",
"password": "********",
"influx": {
"enabled": "true",
"host": "http://192.168.0.90:8086",
"username": "solar",
"password": "********",
"device": "max",
"prefix": "solar",
"database": "solar",
"namingMap": {
"Inverter_mode": "output_mode",
"AC_grid_voltage": "grid_voltage",
"AC_grid_frequency": "grid_frecuency",
"AC_out_voltage": "ac_output_voltage",
"AC_out_frequency": "ac_output_frecuency",
"PV_in_voltage": "pv_input_voltage_1",
"PV_in_current": "pv_input_current_for_battery",
"PV_in_watts": "pv_input_watts",
"PV_in_watthour": "pv_input_watthour",
"SCC_voltage": "battery_voltage_from_scc",
"Load_pct": "output_load_percent",
"Load_watt": "output_load_watt",
"Load_watthour": "outpu_load_watthour",
"Load_va": "ac_output_power_va",
"Bus_voltage": "bus_voltage",
"Heatsink_temperature": "inverter_heat_sink_temperature",
"Battery_capacity": "battery_capacity",
"Battery_voltage": "battery_voltage",
"Battery_charge_current": "battery_charging_current",
"Battery_discharge_current": "battery_discharge_current",
"Load_status_on": "load_status_on",
"SCC_charge_on": "scc_charge_on",
"AC_charge_on": "ac_charge_on",
"Battery_recharge_voltage": "battery_recharge_voltage",
"Battery_under_voltage": "battery_under_voltage",
"Battery_bulk_voltage": "battery_bulk_voltage",
"Battery_float_voltage": "battery_float_voltage",
"Max_grid_charge_current": "max_grid_charge_current",
"Max_charge_current": "max_charge_current",
"Out_source_priority": "output_source_priority",
"Charger_source_priority": "charger_source_priority",
"Battery_redischarge_voltage": "battery_re_discharge_voltage"
}
}
}
what needs to change for it to work?
Thank you