-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
Konnected bug in hassio 0.77.3 #16506
Comments
Please fill in the issue template completely. |
Check your configuration.yaml file and make sure you are now using the full MAC address for each Konnected board as described at https://help.konnected.io/support/solutions/articles/32000022556-set-up-konnected-in-home-assistant-and-hass-io Before 0.77 you could use the last six characters of the Konnected MAC in your config file, but 0.77 and above now require the full MAC address. I don't think the docs at https://www.home-assistant.io/components/konnected/ have been updated yet. I just upgraded to 0.77.3 (from 0.77.2) this morning with four Konnected units and everything is functioning normally. |
This is not a bug. The error message is telling you that your Unfortunately for some reason the updated component documentation didn't get merged in time for the 0.77 release, but this is documented on the Konnected website as @gcdonaldson pointed out above. Sorry for the confusion. This issue can be closed. |
Auhh yes I had the full mac address but didn't have it as all lower case. Closing |
Just updated from 76.0 to 77.3 and while everything worked great looks like the konnected component has a breaking bug. I am getting the following error:
Invalid config for [konnected]: value {konnected device mac address} does not match regular expression [0-9a-f]{12} for dictionary value @ data['konnected']['devices'][0]['id']. Got '{konnected device mac address}'. (See /config/configuration.yaml, line 51). Please check the docs at https://home-assistant.io/components/konnected/
Have not changed my configurations at all.
The text was updated successfully, but these errors were encountered: