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

0.81.0: 'Value should be a string for dictionary value' #17851

Closed
jamieshaw opened this issue Oct 27, 2018 · 4 comments · Fixed by #17860
Closed

0.81.0: 'Value should be a string for dictionary value' #17851

jamieshaw opened this issue Oct 27, 2018 · 4 comments · Fixed by #17860
Assignees

Comments

@jamieshaw
Copy link

Home Assistant release with the issue:
0.81.0

Last working Home Assistant release (if known):
0.80.3

Operating environment (Hass.io/Docker/Windows/etc.):
Native (PIP); Ubuntu 18.04 under VMware ESXi 6.7

Component/platform:

  • homeassistant.core
  • nest

Description of problem:
It appears that some strings within the config are not being correctly validated as such; I've seen this issue flag with the Nest structure config option, as well as automations calling the new homeassistant.update_entity service.

In regards to automations calling update_entity, it seems entity_id is always passed as a array rather than a string

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

- alias: '_Template Clock'
  initial_state: true
  trigger:
    - platform: time
      minutes: '/1'
  action:
    - service: homeassistant.update_entity
      entity_id: sensor.occupants

Traceback (if applicable):

ERROR (MainThread) [homeassistant.core] Invalid service data for homeassistant.update_entity: value should be a string for dictionary value @ data['entity_id']. Got ['sensor.occupants']

Additional information:

@iuro
Copy link

iuro commented Oct 27, 2018

Same problem here, same version upgrade with nest

@ghost ghost assigned balloob Oct 27, 2018
@ghost ghost added the in progress label Oct 27, 2018
@amelchio
Copy link
Contributor

Thanks. This will be fixed in 0.81.1.

Incidentally, please note that your automation is triggering every second, not every minute.

@ghost ghost removed the in progress label Oct 27, 2018
@tagno25
Copy link

tagno25 commented Oct 29, 2018

I am having this same issue in 0.81.1 with the nest component.

@amelchio
Copy link
Contributor

@tagno25 Please file a separate issue with your relevant configuration.yaml snippet.

@home-assistant home-assistant locked as resolved and limited conversation to collaborators Oct 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants