sfstar
sfstar
Hello @pvtex, Does the entire integration stop reporting values (while for example the vebus device / inverter is still running) or does only the smartshunt device stop reporting values. Furthermore,...
I need to look into this, I believe that cleaning up the entities should be possible. However, statistics data cannot be removed and imho shouldn't be automatically removed when removing...
Thanks for opening this PR. I understand the issue. The amperage unit was assigned due to the lack of Ah/mAh being a valid unit of measurement. This is indeed incorrect....
The discussion regarding unitofelectriccharge introduction has been stranded here: https://github.com/home-assistant/architecture/discussions/1052 Therefore introducing custom unit of charge in #274. Closing this issue, since it will be resolved by the other PR.
This is an potential breaking change since the sliders kan reset to an out-of-bounds value -32768 or 32768 if the slider has a value that is below or above the...
Hello Florian, The integration reports the data returned by the gx device. Somehow the data being returned changed from 1152 to 497. Has this behaviour happened again since the initial...
Hello and thank you for opening this issue, Unfortunately the integration doesn't yet support multi sites since the entity naming is generated with the unit id that contained the specific...
@Ekkib Perhaps you can open an issue here: https://github.com/victronenergy/dbus_modbustcp/issues. This is the issue tracker of the victron modbus server. All values exposed by victron are documented and/or requested here. Once...
Unfortunately this is a data provider issue. The modbus server does not return these registers with values other than 0 if a can-bus battery is used. In order to get...
The victron modbus TCP spec sheet references only the following return codes for that register address: `12=High battery temperature;13=High battery voltage;14=Low battery voltage;15=VBat exceeds $CPB;21=High alternator temperature;22=Alternator overspeed;24=Internal error;41=High field...