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
I've been successfully using this integration on a Wallbox Commander 2s.
However, when I (re)boot Home Assistant I consistently get a notification message about OCPP.
In the logfile it says:
2025-01-01 11:30:03.536 INFO (MainThread) [ocpp] commander: send [2,"764ddda7-6954-4a61-bc4a-a8a55197ed62","ChangeAvailability",{"connectorId":0,"type":"Operative"}]
2025-01-01 11:30:03.555 INFO (MainThread) [ocpp] commander: receive message [3,"764ddda7-6954-4a61-bc4a-a8a55197ed62",{"status": "Scheduled"}]
2025-01-01 11:30:03.559 WARNING (MainThread) [custom_components.ocpp] Failed with response: Scheduled
When I try to enable the Availability manually from the HomeAssistant UI, it does not enable, with the same message in the logging.
Should I be concerned about this?
Can I avoid triggering the notification in some way?
Version of the custom_component
v0.6.3
The text was updated successfully, but these errors were encountered:
I've been successfully using this integration on a Wallbox Commander 2s.
However, when I (re)boot Home Assistant I consistently get a notification message about OCPP.
In the logfile it says:
When I try to enable the Availability manually from the HomeAssistant UI, it does not enable, with the same message in the logging.
Should I be concerned about this?
Can I avoid triggering the notification in some way?
Version of the custom_component
v0.6.3
The text was updated successfully, but these errors were encountered: