patman15
commented
3 months ago Hi!
I gave it a final look and detected following issues here in my setup (type-A battery)
Thanks a lot!
1. two values are always "0" (Current and Power)This should be fixed in version 1.0.1. Need to dig deeper into the topic, but it should work now. Thanks for spotting this!
2. very important (at least for me) is to see (as displayed in the app) that the battery is either "charging", "discharging" or "idling" => but I suspect that this is just a calculated value derived from simple rule to check whether "Current" is positive, negative or zero value => but would be nice to gave that as an entity too in the integrationYes, the app just goes with the current. I could add a binary sensor
battery_chargingwhich is foreseen by HA. Is that what you would be looking for? (This would not cover the stateidlethough.)3. the switching between using your integration and the offgridtec is currently also a bit quirkyTrue, did not think of this as a real use-case ... Anyway, to switch from the app to the integration, you need to click
Scanningon the right top of the app and confirm to close the bluetooth connection. If you just close the app it still blocks the connection to the BMS and the integration cannot read values. The other way round I need to dig much deeper, as I have not seen how HA cleans up connections on deactivation actively.
gkathan
hi sir,
I gave it a final look and detected following issues here in my setup (type-A battery)
1) two values are always "0" (Current and Power) - it looks like "Current" matches what I see in the offgridtec app (see screenshot), "Power" is not shown in the app ... but should also not be zero
2) very important (at least for me) is to see (as displayed in the app) that the battery is either "charging", "discharging" or "idling" => but I suspect that this is just a calculated value derived from simple rule to check whether "Current" is positive, negative or zero value => but would be nice to gave that as an entity too in the integration
3) the switching between using your integration and the offgridtec is currently also a bit quirky => tested to disable the integration => this worked after some time (30 min) that the offgridtec app again could connect BUT from then on it was no longer possible to re-enable succesfully the integration => it just showed "unavailable error" => only removing the device and the integration and re-adding the integration cured the situation
OK thats it from my side - i hope we can fix these last glitches => then it will be perfect and maybe even point 3) is irrelevant as all relevant data is provided by HA
cheerz greetings from vienna