Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot set Availability for Wallbox Commander 2s #1457

Open
rhpijnacker opened this issue Jan 1, 2025 · 0 comments
Open

Cannot set Availability for Wallbox Commander 2s #1457

rhpijnacker opened this issue Jan 1, 2025 · 0 comments

Comments

@rhpijnacker
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant