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

Garadget: Invalid Config after updating HA to 0.86.1 #20420

Open
njloki30 opened this Issue Jan 25, 2019 · 8 comments

Comments

Projects
None yet
5 participants
@njloki30
Copy link

njloki30 commented Jan 25, 2019

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:

  • platform: garadget
    covers:
    37002XXXXXXXXXXXXXXX:
    access_token: 084dXXXXXXXXXXXXXXXXXXXXX

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:

@njloki30 njloki30 changed the title Gargdget: Invalid Config after updating HA to 0.86.1 Garadget: Invalid Config after updating HA to 0.86.1 Jan 25, 2019

@marchingphoenix

This comment has been minimized.

Copy link
Contributor

marchingphoenix commented Jan 25, 2019

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.

@njloki30

This comment has been minimized.

Copy link
Author

njloki30 commented Jan 25, 2019

Thank you for the quick response @marchingphoenix

@njloki30

This comment has been minimized.

Copy link
Author

njloki30 commented Jan 26, 2019

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/

@njloki30

This comment has been minimized.

Copy link
Author

njloki30 commented Jan 27, 2019

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:

@bwdur

This comment has been minimized.

Copy link

bwdur commented Jan 28, 2019

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.

@njloki30

This comment has been minimized.

Copy link
Author

njloki30 commented Jan 28, 2019

Great, Thanks @bwdur . I updated my config per your example and the cover is working again. Thanks so much! Cheers!!

@aelg305

This comment has been minimized.

Copy link

aelg305 commented Jan 31, 2019

confirmed...working! thank you.

@BobbyBleacher

This comment has been minimized.

Copy link

BobbyBleacher commented Feb 1, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment