ADAX Local Bluetooth setup fails when SSID contains special characters (e.g., space)
Opened this issue · 1 comments
The problem
I encountered a repeatable issue when setting up the ADAX Local integration in Home Assistant using Bluetooth. The setup fails with the following error in the logs:
Traceback (most recent call last):
File "src/dbus_fast/message_bus.py", line 797, in dbus_fast.message_bus.BaseMessageBus._process_message
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/manager.py", line 1087, in _parse_msg
watcher.on_characteristic_value_changed(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
message_path, new_value
^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/bleak/backends/bluezdbus/client.py", line 188, in on_value_changed
callback(bytearray(value))
~~~~~~~~^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/adax_local/__init__.py", line 121, in notification_handler
raise InvalidWifiCred
adax_local.InvalidWifiCred
After troubleshooting, I found that the cause was my Wi-Fi SSID containing a space ("My Home 2.4GHz"). When I renamed it to "MyHome24" (no space or special characters), the pairing and Wi-Fi configuration completed successfully.
It appears that the ADAX Bluetooth provisioning process fails when the SSID contains special characters such as spaces, dots, or symbols. This could be related to how the credentials are serialized before being sent to the heater.
It might help to sanitize or quote the SSID and password before transmission to avoid this error.
Or, at least, inform about this in the setup process.
What version of Home Assistant Core has the issue?
core-2025.11.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
adax
Link to integration documentation on our website
https://www.home-assistant.io/integrations/adax/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
Hey there @Danielhiversen, @LazyTarget, mind taking a look at this issue as it has been labeled with an integration (adax) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of adax can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign adaxRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
adax documentation
adax source
(message by IssueLinks)