Closed HBK1 closed 1 year ago
Similar results here with an OrionSmart DC-DC charger. If the charger is off, the output voltage is shown as 327.67 V
. This should be filtered.
Everything else, including data from my SmartSolar 75-15, is displayed as expected. Great Work!
Should the component submit no value (like your filter), 0.0
or NAN
in this scenario? I am unsure what would work best.
My filter is causing HA to keep the last value which may not be so good. I would rather prefer 0.0 as this is the real value and what keshavdv does. NAN will present Unavalible in HA and may disturb further calculations of energy.
Hi @HBK1, can you please test the changes?
You might need to add refresh: 0s
to the external_components
to ensure you use the latest version for testing.
It is working ok with 0.0V , Thanks!
There is a warning in the log, is this anything to be worried about?
[15:30:27][D][sensor:094]: 'SH Time remaining': Sending state 65535.00000 min with 0 decimals of accuracy
[15:30:27][D][sensor:094]: 'SH Battery voltage': Sending state 13.34000 V with 2 decimals of accuracy
[15:30:27][D][sensor:094]: 'SH Starter Battery': Sending state 12.77000 V with 2 decimals of accuracy
[15:30:27][D][sensor:094]: 'SH Current': Sending state 0.11400 A with 3 decimals of accuracy
[15:30:27][D][sensor:094]: 'SH Consumed Ah': Sending state -3.90000 Ah with 1 decimals of accuracy
[15:30:27][D][sensor:094]: 'SH State of charge': Sending state 98.60000 % with 1 decimals of accuracy
[15:30:27][D][text_sensor:064]: 'SH Battery Alarm reason': Sending state ''
[15:30:27][W][component:204]: Component victron_ble took a long time for an operation (0.06 s).
[15:30:27][W][component:205]: Components should block for at most 20-30ms.
[15:30:28][D][victron_ble:247]: [F2:F0:E7:44:35:3D] Recieved BATTERY_MONITOR message.
[15:30:28][D][victron_ble:247]: [C3:9C:38:27:0A:0A] Recieved BATTERY_MONITOR message.
[15:30:28][D][victron_ble:247]: [C3:9C:38:27:0A:0A] Recieved BATTERY_MONITOR message.
[15:30:29][D][sensor:094]: 'MPPT Battery Voltage': Sending state 13.35000 V with 2 decimals of accuracy
[15:30:29][D][sensor:094]: 'MPPT Battery Current': Sending state 1.10000 A with 3 decimals of accuracy
[15:30:29][D][sensor:094]: 'MPPT Yield Today': Sending state 0.11000 kWh with 2 decimals of accuracy
[15:30:29][D][sensor:094]: 'MPPT PV Power': Sending state 15.00000 W with 0 decimals of accuracy
[15:30:29][D][sensor:094]: 'MPPT Load Current': Sending state -0.00000 A with 1 decimals of accuracy
[15:30:29][D][text_sensor:064]: 'MPPT state': Sending state 'Float'
[15:30:29][D][text_sensor:064]: 'MPPT Error reason': Sending state ''
[15:30:29][W][component:204]: Component victron_ble took a long time for an operation (0.05 s).
[15:30:29][W][component:205]: Components should block for at most 20-30ms.
[15:30:29][D][victron_ble:247]: [F2:F0:E7:44:35:3D] Recieved BATTERY_MONITOR message.
[15:30:29][D][victron_ble:247]: [C3:9C:38:27:0A:0A] Recieved BATTERY_MONITOR message.
The warning is because EspHome changed the log level of this message from verbose to warn. Tracking this warning in a seperate issue #22.
Victron Battery Sense reports as Battery Monitor and presents BATTERY_VOLTAGE and TEMPERATURE. Orion Smart DCDC needs a filter on OUTPUT_VOLTAGE since it reports 0x7FFF=32767 when engine is off=Unavalible. Both are working ok together with a Smartshunt and MPPT on the same ESP32.
See below config for DCDC and Battery Sense: