Last working Home Assistant release (if known):
0.85.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/cover.garadget/
Description of problem:
After updating to 0.86.1 Garadget Component continually says invalid config in configuration.yaml even when it's correct. No changes were made to the component config during upgrade.
Message Recieved:
Invalid config for [cover.garadget]: [37002XXXXXXXXXXXXXXX] is an invalid option for [cover.garadget]. Check: cover.garadget->covers->37002XXXXXXXXXXXXXXX. (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
Config entry:
cover:
Additional information:
Log Error
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /config
Failed config
cover.garadget:
- Invalid config for [cover.garadget]: [37002XXXXXXXXXXXXXXX] is an invalid option for [cover.garadget]. Check: cover.garadget->covers->37002XXXXXXXXXXXXXXX. (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
- platform: garadget
covers: [source /config/configuration.yaml:35]
37002XXXXXXXXXXXXXXX: [source /config/configuration.yaml:36]
access_token: 084dXXXXXXXXXXXXXXXXXXXXX
Successful config (partial)
cover.garadget:
Likely caught up by the entity_id naming conventions being enforced. An entity_id of only numbers would be considered invalid so this makes sense. Component will need to be adjusted to fix this issue.
Pinging @JasonCarter80 as he was the original contributor.
Thank you for the quick response @marchingphoenix
I think you're right @marchingphoenix , when I add a few "AAA"'s to the end of the ID and retest I get an invalid slug issue.
Invalid config for [cover.garadget]: invalid slug 3700XXXXXXXXXXXXXXAAAA (try 3700XXXXXXXXXXXXXXAAAA ) for dictionary value @ data['covers']. Got OrderedDict([('3700XXXXXXXXXXXXXXAAAA ', None)]). (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
Update following the 0.86.3 install.
New error in log
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /config
Failed config
cover.garadget:
- Invalid config for [cover.garadget]: [370XXXXXXXXXXXXXXXXXX] is an invalid option for [cover.garadget]. Check: cover.garadget->covers->370XXXXXXXXXXXXXXXXXX. (See ?, line ?). Please check the docs at https://home-assistant.io/components/cover.garadget/
- platform: garadget
covers: [source /config/configuration.yaml:35]
370XXXXXXXXXXXXXXXXXX: None
access_token: 084XXXXXXXXXXXXXXXXXXXXXXX
Successful config (partial)
cover.garadget:
I went to fix this, but it looks like it has already been fixed! The docs don't reflect the needed changes for configuration.yaml.
I updated my config to look like this:
cover:
- platform: garadget
covers:
garadget1:
device: 57XXXXXXXXXXXXXXXXXXXXXX
username: YOUR_USERNAME
password: YOUR_PASSWORD
And all seems to be working.
Great, Thanks @bwdur . I updated my config per your example and the cover is working again. Thanks so much! Cheers!!
confirmed...working! thank you.
Except the name of the cover is no longer tied to the device. I.E., I've got garage left/right and they show up as garadget and garagdet_2... And upon a homeassistant restart those cover names swapped (assume assigned names upon discovery). This is a step backward as my devices uses to be named cover.right, cover.left.
Except the name of the cover is no longer tied to the device. I.E., I've got garage left/right and they show up as garadget and garagdet_2... And upon a homeassistant restart those cover names swapped (assume assigned names upon discovery). This is a step backward as my devices uses to be named cover.right, cover.left.
You should be able to resolve this appropriately using the name: key.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Most helpful comment
I went to fix this, but it looks like it has already been fixed! The docs don't reflect the needed changes for configuration.yaml.
I updated my config to look like this:
And all seems to be working.