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
Ebusd version 3.2 has been running happily since 2018 (didn't even realise it'd been that long, realise it's an older version) collecting data from Valiant EcoTec Plus boiler.
Following an unscheduled reboot (power filature) this week, my collection scripts have all failed with error "ERR: element not found"
Using ebusctl presents the same result.
ebusctl scan result shows:
08;Vaillant;BAI00;0204;9602
84;Vaillant;OTS00;0205;9101
I'm feeling like this is a config issue - and can see that 08.bai.csv was recently changed. Is this likely to be related?
Any pointers please? It's been so long since I've touched this, as its just worked!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Ebusd version 3.2 has been running happily since 2018 (didn't even realise it'd been that long, realise it's an older version) collecting data from Valiant EcoTec Plus boiler.
Following an unscheduled reboot (power filature) this week, my collection scripts have all failed with error "ERR: element not found"
Using ebusctl presents the same result.
ebusctl scan result shows:
08;Vaillant;BAI00;0204;9602
84;Vaillant;OTS00;0205;9101
I'm feeling like this is a config issue - and can see that 08.bai.csv was recently changed. Is this likely to be related?
Any pointers please? It's been so long since I've touched this, as its just worked!
Beta Was this translation helpful? Give feedback.
All reactions