Closed Saentist closed 1 year ago
QDI Over temperature restart = Unavailable QDI Over temperature restart = Off
I assume this is in home assistant - the entities look to be duplicated, this might be the first update you've done since the change to move boolean variables to 'binary sensors' can you check the details of an unavailable entity and one that is available with the same name?
If one is a sensor and the other a binary sensor, you will either need to delete the unavailable sensor entities or roll back to an earlier version and remove the binary sensors
QPIGS Is AC Charging On = Unavailable QPIGS Is AC Charging On = Off QPIGS Is Battery Voltage to Steady While Charging = Unavailable QPIGS Is Battery Voltage to Steady While Charging = Off QPIGS Is Charging On = Unavailable QPIGS Is Charging On = Off QPIGS Is Charging to Float = Unavailable QPIGS Is Charging to Float = Off QPIGS Is Configuration Changed = Unavailable QPIGS Is Configuration Changed = Off QPIGS Is Load On = Unavailable QPIGS Is Load On = On QPIGS Is Reserved = Unavailable QPIGS Is Reserved = Off QPIGS Is SBU Priority Version Added = Unavailable QPIGS Is SBU Priority Version Added = Off QPIGS Is SCC Charging On = Unavailable QPIGS Is SCC Charging On = Off QPIGS Is SCC Firmware Updated = Unavailable QPIGS Is SCC Firmware Updated = Off QPIGS Is Switched On = Unavailable QPIGS Is Switched On = On
Also note that some of these might change names in the future as I get a better understanding of the inverters (particularly in PI30 and related protocols
eg Is SCC Charging On = Off
would be better as SCC Charging = Off
or Solar Charge Controller Charging = Off
in my opinion
the code is still very beta (hence the 0.xx.y version numbering) and so is likely to have breaking changes from time to time
Im relying on pip/pypi for package distribution currently so have not really gone with release notes or the like
There is a logic,
but what about QPIGS AC Input Voltage
mpp-solar -p /dev/hidraw2 -o screen -c QPIGS
Command: QPIGS - General Status Parameters inquiry
--------------------------------------------------------------------------------
Parameter Value Unit
ac_input_voltage 220.8 V {'icon': 'lightning'}
ac_input_frequency 50.0 Hz
ac_output_voltage 220.8 V
ac_output_frequency 50.0 Hz
ac_output_apparent_power 0 VA
ac_output_active_power 0 W
ac_output_load 0 %
bus_voltage 362 V
battery_voltage 0.9 V
battery_charging_current 0 A
battery_capacity 0 %
inverter_heat_sink_temperature 37 °C
pv_input_current_for_battery 0.0 A
pv_input_voltage 0.0 V
battery_voltage_from_scc 0.0 V
battery_discharge_current 0 A
is_sbu_priority_version_added 0 bool
is_configuration_changed 0 bool
is_scc_firmware_updated 0 bool
is_load_on 1 bool
is_battery_voltage_to_steady_while_charging 0 bool
is_charging_on 0 bool
is_scc_charging_on 0 bool
is_ac_charging_on 0 bool
rsv1 0 A
rsv2 0 A
pv_input_power 0 W
is_charging_to_float 0 bool
is_switched_on 1 bool
is_reserved 0 bool
what about it? has it disappeared?
Yes, all with return "icon"
I also use hassd_mqtt
to send data to HA
yes thats new development, device classes and icons are being added to protocols to improve home assistant support - its a work in progress and will likely change Has it caused a problem?
Minimal, but is bug, hope fixed soon.
how so? the print to screen is used as debug - do you have a use case for the screen output that is needed to not show the extra info?
The PI30MAX protocol has even more info added
~/src/mpp-solar $ mpp-solar -p test -c QPIGS -P PI30MAX
Command: QPIGS - General Status Parameters inquiry
--------------------------------------------------------------------------------
Parameter Value Unit
ac_input_voltage 227.2 V {'icon': 'mdi:transmission-tower-export'}
ac_input_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}
ac_output_voltage 230.3 V {'icon': 'mdi:power-plug', 'device-class': 'voltage'}
ac_output_frequency 50.0 Hz {'icon': 'mdi:current-ac', 'device-class': 'frequency'}
ac_output_apparent_power 829 VA {'icon': 'mdi:power-plug', 'device-class': 'apparent_power'}
ac_output_active_power 751 W {'icon': 'mdi:power-plug', 'device-class': 'power'}
ac_output_load 10 % {'icon': 'mdi:brightness-percent'}
bus_voltage 447 V {'icon': 'mdi:details', 'device-class': 'voltage'}
battery_voltage 54.5 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}
battery_charging_current 20 A {'icon': 'mdi:current-dc', 'device-class': 'current'}
battery_capacity 83 % {'device-class': 'battery'}
inverter_heat_sink_temperature 54 °C {'icon': 'mdi:details', 'device-class': 'temperature'}
pv1_input_current 2.7 A {'icon': 'mdi:solar-power', 'device-class': 'current'}
pv1_input_voltage 323.6 V {'icon': 'mdi:solar-power', 'device-class': 'voltage'}
battery_voltage_from_scc 0.0 V {'icon': 'mdi:battery-outline', 'device-class': 'voltage'}
battery_discharge_current 0 A {'icon': 'mdi:battery-negative', 'device-class': 'current'}
is_sbu_priority_version_added 0 bool
is_configuration_changed 0 bool
is_scc_firmware_updated 0 bool
is_load_on 1 bool
is_battery_voltage_to_steady_while_charging 0 bool
is_charging_on 1 bool
is_scc_charging_on 1 bool
is_ac_charging_on 0 bool
battery_voltage_offset_for_fans_on 0 10mV
eeprom_version 0
pv1_charging_power 879 W {'icon': 'mdi:solar-power', 'device-class': 'power'}
is_charging_to_float 0 bool
is_switched_on 1 bool
is_dustproof_installed 0 bool
PI30MAX work but not correctly with all commands.
Command: QID - No description found
--------------------------------------------------------------------------------
Parameter Value Unit
warning No definition for command QID in protocol b'PI30MAX'
response 53555355535552ý
Is there a way no mater protocol, commands response values to be decoded?
oh thats a bug
I'll get a fix in the next release (its in github now)
Also try QSID
Is there a way no mater protocol, commands response values to be decoded?
No, because the protocol 'defines' how to decode, and it differs by inverter and command
mpp-solar -p /dev/hidraw2 -c QSID -P PI30MAX
Command: QSID - Device Serial Number inquiry
--------------------------------------------------------------------------------
Parameter Value Unit
serial_number 1455355535553555355535
by spec this is:
QSID<cr>: The device serial number inquiry (the length is more than 14)
Computer: QSID<CRC><cr>
Device: (NNXXXXXXXXXXXXXXXXXXXX <CRC><cr>
NN: Serial number valid length, X: Serial number, invalid part is filled as ‘0’, total X is 20.
MAX Communication Protocol for HV7.2k LV5k V00 20200717.pdf
there mus be a table of devices and it's command capability's something as
mpp-solar -p /dev/hidraw2 -o screen -c QMN#QGMN
Command: QMN - Model Name Inquiry
--------------------------------------------------------------------------------
Parameter Value Unit
model_name VMIII-5000
Command: QGMN - General Model Name Inquiry
--------------------------------------------------------------------------------
Parameter Value Unit
general_model_name 037
Axpert KS&MKS&V&KING RS232 Protocol 20180104.pdf page 22 QGMN With model and sub model can have nice database of supported protocol and commands.
yes, although need to get all that info and determine which protocol is relevant also this only works for PI30 protocol
yes, although need to get all that info and determine which protocol is relevant also this only works for PI30 protocol
My inverter has
QMN: MKS2-8000
QGMN: 044
Maybe QPI and QGMN together works, eg PI30-044
for my inverter and PI30-037
for yours
The page 22 you linked to only has values to 024
yes, although need to get all that info and determine which protocol is relevant also this only works for PI30 protocol Maybe QPI and QGMN together works, eg
PI30-044
for my inverter andPI30-037
for yours The page 22 you linked to only has values to 024
Document is older (year 2018) and not provided to end users. QPI#QMN#QGMN Enable Wiki in repo to make this database, and move documentation there.
Good idea Wiki enabled Doc move a really good idea, will take me some time tho
Wiki not enabled yet.
QPI (Protocol ID distribution): 30 for PIP series QMN: VMIII QGMN: 023 PIP-5048MK PIP-5048MK 024 PIP-3024MK PIP-3024MK
King_product-application_pdf-20190724092401-8519-pip-gk-mk-protocol.pdf some more
Communication Protocol. PIP-HS_MS_MSX & HYBRID V Communication Protocol.pdf
! NO QID command supported
QMN<cr>: Query model name(Just for Hybrid V Series)
Computer: QMN<CRC><cr>
Inverter: (MMMM-NNNN-BB-VV-SSSS<CRC><cr> if Inverter accepts this command, otherwise,
responds (NAK<cr>
MMMM: model name, NNNN: Rated output VA, BB: Battery voltage, VV: HV/LV, SSSS:
Special flag
Note: The length of MMMM&NNNN&SSSS may be different for different models
1 PIP-HSE 5K
2 PIP-MSE 5K
3 PIP-HSE 3K
4 PIP-MSE 3K
5 PIP-1648MSX (LV)
QGMN
001 PIP-HSE 5K
002 PIP-MSE 5K
003 PIP-HSE 3K
004 PIP-MSE 3K
005 PIP-1648MSX (LV)
006 PIP-2424LV-MSD PIP-2424LV-MSD
007 PIP-2424LV-HS PIP-2424LV-HS
008 PIP2424MSP PIP2424MSP
009 PIP2424HSP PIP2424HSP
010 PIP4024mSP PIP4024MSP
011 PIP4024HSP PIP4024HSP
012 PIP5048MS 64V PIP5048MS 64V
013 PIP5048HS 64V PIP5048HS 64V
014 PIP5048MS PIP5048MS
015 PIP5048HS PIP5048HS
016 ALFA M-5000 ALFA M-5000
017 ALFA P-5000 ALFA P-5000
018 PIP5048MSD/MST PIP5048MSD/MST
Can you still not get into the wiki? Ive added some pages including the start of a protocol recommendations etc page https://github.com/jblance/mpp-solar/wiki/Protocol-Recommendations I will add a command to build an identifier across a bunch of different protocols this built up of a few different commands to make it easier to build the database
Inverter: (MMMM-NNNN-BB-VV-SSSS
if Inverter accepts this command, otherwise, responds (NAK MMMM: model name, NNNN: Rated output VA, BB: Battery voltage, VV: HV/LV, SSSS: Special flag
I love how none of the items in the table actually follow this spec
Are there any outstanding issues for this item now? Do you need a 'screen' output without the extra info (like icons)?
after run one with P30MAX protocol all icons was set and data function with regular P30
Reopening
After restart of HA, again do not want to receive values with icon on P30 protocol.
In terminal with screen
output all seems OK, but in hassd_mqtt
output there is something weird.
https://github.com/jblance/mpp-solar/wiki/Detailed-Usage#list-available-output-processors
need correction about hassd_mqtt
the icons are in pi30max only atm - is your inverter not best with pi30max?
yes but way fewer that pi30max - do you use the Q1 command? is the icons working there?
QID#QDI#QMOD#QPI#QPIGS#QPIRI#QFLAG
just this one.
91 valid entities
completed i think - let me know if there is still an issue outstanding
latest
Lot of entity's are switched to Unavailable, previously working
No firmware or etc. changed.