0.88: Persons, Command line auth and event subscriptions

Blog
96

look at any of your mqtt components, this one has been around for a number of releases so you need to change the mqtt configs

97

Whats up with the docker releases? For the past 1-2 months all of the 86.1, 87.1 and 88.1 etc is not updated before days after relase? The main release is ok with a few hours behind but the 0.1 releases are not updatet before days later. If we have a bug that is fixed in the 0.1 release its a long wait :slight_smile:

2 Likes
98

I’m getting this extra keys warning for the iTach remote component but my configuration matches the example configuration and does not contain any unsupported keys:

Your configuration contains extra keys that the platform does not support.
Please remove [name].  (See /config/remotes.yaml, line 0).

My remotes.yaml config:

- platform: itach
  name: Cinema
  host: 10.1.1.19
  devices:
    - name: Cinema Amp
      modaddr: 1
      connaddr: 1
      commands:
        - name: "ON"
          data: "0000 006A 0000 0024 0154 00B3 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0600 0154 0055 0016 0F18"
        - name: "OFF"
          data: "0000 006A 0000 0026 015D 00B5 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0042 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0042 0016 0042 0016 0042 0016 0042 0016 0016 0016 0016 0016 0016 0016 0042 0016 0016 0016 0016 0016 0016 0016 0016 0016 0042 0016 0042 0016 0042 0016 060B 015D 0056 0016 0EA3 015D 0055 0016 00B5"
        - name: "Dolby" # Dolby DSP
          data: "0000 006A 0000 0026 0154 00B4 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0600 0154 0055 0016 0E7D 0154 0055 0016 0F18"

etc…

Example config from here: https://www.home-assistant.io/components/remote.itach/

# Example configuration.yaml entry
remote:
  - platform: itach
    name: Living Room
    host: itach023fdc
    devices:
      - name: TV
        connaddr: 2
        commands:
          - name: "ON"
            data: "0000 006D 0000 0022 00AC 00AC 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0689"

I’ll open an issue.

Edit: or maybe I wont: https://github.com/home-assistant/home-assistant/issues/21300

Docs just need updating.

99

Any one else getting periodic crashes?

Assistant
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; 
   Active: failed (Result: signal) since Fri 2019-02-22 18:39:39 GMT; 6h ago
  Process: 26248 ExecStart=/home/rob/homeassistant/bin/hass -c /home/rob/.ho
 Main PID: 26248 (code=killed, signal=KILL)

Feb 22 18:39:12 squeezeserver hass[26248]:                                  
Feb 22 18:39:13 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:15 squeezeserver hass[26248]:   % Total    % Received % Xferd  
Feb 22 18:39:15 squeezeserver hass[26248]:                                  
Feb 22 18:39:15 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:21 squeezeserver hass[26248]:   % Total    % Received % Xferd  
Feb 22 18:39:21 squeezeserver hass[26248]:                                  
Feb 22 18:39:21 squeezeserver hass[26248]: [158B blob data]
Feb 22 18:39:39 squeezeserver systemd[1]: [email protected]: Main p
Feb 22 18:39:39 squeezeserver systemd[1]: [email protected]: Failed
101

I get these warnings in my log 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to lock.lock to be instead: entity_id: all 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to light.turn_off to be instead: entity_id: all 2019-02-21 22:30:00 WARNING (MainThread) [homeassistant.helpers.service] Not passing an entity ID to a service to target all entities is deprecated. Update your call to switch.turn_off to be instead: entity_id: all

so I do as it says and add the entity_id: all and it breaks my script so I remove it and live with the warning as my script works the way I want it to

so I understand why people get fustrated when they decide to break something that is working as the so called fix breaks it

102

It’s a warning for now but expect it to break the component in the future so I suggest you work out how to fix it… ie fix your script to work with it.

See for example here Not passing an entity ID to a service to target all entities is deprecated. Use instead: entity_id: "all"

103

I did try what is said in the warning and it broke that script so if it is not the proper way to update the script why post the incorrect info

I even use the script builder in configuration section put in exactly the only way it will take it “entitiy_id”:“all” and this is what I get for my troubles

Error executing service <ServiceCall script.1550718691920 (c:35ae31c2c9b445ed821e85afb55ac133)>

I take it out and leave it blank it works with warnings

104

There is a hidden group you can turn on with homeassistant.turn_on service.

{
“entity_id”: “group.all_scripts”
}

105

Open a new topic and post your script.

106

Anybody else having problems with HassIO-deconz-0.88.1.
Had to fall back to 0.87.1

107

My scipt is working as it should as long as I leave the entity out of it

108

What issue?

109

I get these warnings but really don’t know how to fix them:

20

Any hints? Are they related to what?

110

Only because HA is currently ignoring the error in it. This may not continue to be the case.

Do you want help to fix this or not?

111

The primary reason I posted was to point out that the info that the warning tells you to put in to fix the issue breaks the script as far as when my script breaks I can install the entity_id: and put all my devices in separated by comma it will make a little longer script but it works I like how it works now as leaving it blank is cleaner but oh well

112

It breaks your script the way you have done it, but without you actually posting your script we can’t see what you have done wrong.

113

I’m not sure if it’s already been mentioned but the extra keys error messages give the wrong line numbers if there are comments at the top of the YAML file

114

I installed just yesterday for the first time Deconz addon for Hassio and a Conbee stick on 0.88.1 and I’m not getting any issue so far.

115

I’m having issues with the image_processing tensorflow not working on 0.88, It worked fine until 0.87.1.

Any suggestions?

Because I had to compile my own tensorflow, I had to put it in a custom python folder outside Docker (accessible via \config\deps\lib\python3.6\site-packages), has that changed in any way? Everything else seems to be working fine.

116

Since updating the notify service for Discord have stopped working for me. Anyone else experiencing this? Trying to gather more info before making an issue.