You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running V4.2.1 of the modbus sungrow add-on on a Raspberry Pi 3B+.
As per the attached document (Communication Protocol of Residential Hybrid Inverter-V1.1.4.pdf), could the modbus sungrow add-on be expanded to provide access to:
Running state - register 13000
Power flow status - register 13001
MPPT3 voltage - register 5015
MPPT3 current - register 5016
MPPT4 voltage - register 5115
MPPT4 current - register 5116
The changes are beyond my ability but I am able to assist with testing (I have a SH10RS inverter).
Hey,
yes i'm still involved, but have little spare time at the moment.
As mentioned in the forum already (https://community.openhab.org/t/sungrow-binding/147442/99?u=soenke)
this is possible but needs a little refactoring. If one would just add these registers this would break the compatibility with inverters that don't provide this registers (as mine ;)).
So thanks for the issue, ill try to find some time - but can't give you a date for this.
Until then, you might just add a generic modbus poller thing for the missing registers.
@soenkekueper - thanks for the info. Yes, I guess you would need to interrogate input register 5000 (Device type code) to determine which registers are valid and stop the addon making invalid queries.
Thanks for pointing me in the direction of the modbus poller thing. I can use that in the meantime.
I am running V4.2.1 of the modbus sungrow add-on on a Raspberry Pi 3B+.
As per the attached document (Communication Protocol of Residential Hybrid Inverter-V1.1.4.pdf), could the modbus sungrow add-on be expanded to provide access to:
The changes are beyond my ability but I am able to assist with testing (I have a SH10RS inverter).
Communication Protocol of Residential Hybrid Inverter-V1.1.4.pdf
The text was updated successfully, but these errors were encountered: