Hi All,
Ok, interesting problem. As i was saying above the Shunt was working, then stopped. I removed everything and re-added it.
and got some pretty strange stuff coming out
HA versions
Some logs,
This error originated from a custom integration.
Logger: custom_components.victron_ble
Source: components/bluetooth/passive_update_processor.py:586
Integration: Victron BLE (documentation, issues)
First occurred: 1 February 2024 at 18:43:43 (55208 occurrences)
Last logged: 10:04:06
Unexpected error updating Slightly Unst Shunt data: (<VictronSensor.MIDPOINT_VOLTAGE: ‘midpoint_voltage’>, <Units.ELECTRIC_POTENTIAL_VOLT: ‘V’>)
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/bluetooth/passive_update_processor.py”, line 586, in async_handle_update
new_data = self.update_method(update)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/config/custom_components/victron_ble/sensor.py”, line 151, in sensor_update_to_bluetooth_data_update
entity_descriptions={
^
File “/config/custom_components/victron_ble/sensor.py”, line 154, in
): SENSOR_DESCRIPTIONS[
^^^^^^^^^^^^^^^^^^^^
KeyError: (<VictronSensor.MIDPOINT_VOLTAGE: ‘midpoint_voltage’>, <Units.ELECTRIC_POTENTIAL_VOLT: ‘V’>)
Anyone have the same issues?
-=-=-=-=-=-=-=-=-=-=-
more information 7/2/24
-=-=-=-=-=-=-=-=-=-=-
Hi All,
Ok, so I have been doing some work in the background on this as it’s a live system.
The background of this is that I run an HA instance on my boat and I had a charger fail that drained the batteries, so a VICTRON Shunt (due to the driver available for HA) was put in to monitor the batteries/ charge and a simple smart switch was put on the charger to be able to power cycle it. All this was a stopgap as it took me a while to buy new batteries. So before the new batteries the Victron Shunt was just monitoring the main battery bank, and that worked with only a small NooB mistake on getting the shunt working with HA.
Fast forward several weeks and I have just finished redoing everything in the battery compartment. To give you an idea of the amount of work I have done here, I have re-built all the battery storage area, replaced the main batteries, separated the diesel engine onto its own starting battery, added the Shunt, added several VE- bussbars and replaced every cable.
The problems started when I added the AUX wire of the Shunt to monitor the starter battery. THe first problem was that the VE- of starter battery was not connected to the shunt. I didn’t realise that.
So, as above, the main and starter are now connected and the Victron APP shows the values correctly, but the HA instance is showing the values as double before ??crashing ?? the device. A reboot of HA show the data, as a static set of values, the next refresh of the screen it changes to unavailable.
Looking at the logs, its getting really upset over the AUX line and being changed to second battery.
In terms of troubleshooting, here is what I have done, rebooted the shunt (dozens of times while testing) shut off the AUX in the settings, removed and re-installed the device in HA and added the VE- line between the batteries.
At one stage I even removed the AUX line and shut off the option for monitoring the starter battery in the shunt, rebooted the Shunt (removing power) and rebooted HA, to still have the logs saying it was trying to see the starter battery and then shutting on and off.
The next thing I am going to do is remove the AUX lead to the second battery, factory reset the Shunt, Delete the instance from HA, reboot HA and re-setup everything. Hopefully, that will prove the issue is the Starter battery monitoring.