After updating to 0.94 I had to install to pip install yeelight manually or the yeelight component wouldn’t work. I’m running HA on docker. Any ideias why?
Did anyone else lose remote access from nabu casa when they upgraded?
Yeah, I think this transition may have come a little early - documentation isn’t updated and there appears to be some shortcomings with what was possible before. I’m having difficulty with a new phone being tracked with Owntracks too with this new change - the device is appearing as an entity but only shows it being at home, never tracked elsewhere. Like others, devices were doubled up with _2 on the end of the entity name. I’m unsure if you’re able to change/add an image for the person/device now either seeing as known_devices.yaml is no longer used. The person component documentation does not mention that ability.
You can customise the person component to show an image
1 Like
But again, the documentation doesn’t explain how and doesn’t list it as a configuration variable.
For own tracks have you removed it from your configuration.yaml and set it up through integrations
I added picture to person only customise.yaml. I am not home at moment so can’t post config
1 Like
What I’m going to do is remove the Owntracks integration and re-add it and see how that works. That will at least theoretically remove the doubling of entities.
That’s because it’s not a configuration variable.
It is a customization variable just like other entities. you make those changes in the “customize” section under “homeassistant” in configuration.yaml.
Thank you guys,
it is possible to include EVERSPRING SP816 motion sensor as a platform in HA
Regards christian
Please post in “Feature Requests”
Hi,
In my case the autodiscover doesn’t work. I tried to make a
pip install yeelight
as you, seems works fine as you can see in attached file
but seems continue not working
Hi all.
On 0.94.1 I get this new error:
2019-06-11 12:34:18 ERROR (SyncWorker_4) [pyicloud.base.http] Failed to validate the credentials from cookie
2019-06-11 12:34:18 ERROR (SyncWorker_4) [homeassistant.components.icloud.device_tracker] Error logging into iCloud Service: ('Invalid email/password combination.', PyiCloudAPIResponseError('Failed to validate the credentials from cookie'))
2019-06-11 12:34:18 ERROR (SyncWorker_4) [homeassistant.components.icloud.device_tracker] No ICLOUDTRACKERS added
2019-06-11 12:34:18 ERROR (MainThread) [homeassistant.components.device_tracker] Error setting up platform legacy
2019-06-11 12:35:27 ERROR (MainThread) [pyhaversion] Timeouterror fetching version information from PyPi
2019-06-11 12:35:42 ERROR (SyncWorker_1) [pyicloud.base.http] Failed to validate the credentials from cookie
2019-06-11 12:35:42 ERROR (SyncWorker_1) [homeassistant.components.icloud.device_tracker] Error logging into iCloud Service: ('Invalid email/password combination.', PyiCloudAPIResponseError('Failed to validate the credentials from cookie'))
The Tracking service works with the devices in known.devices, but I am unable to get again the 2FA.
Deleted also the file under icloud with no result.
Tryed also to do the commenting of the tracking icloud in config, restarting HA, uncommenting and restarting HA. No 2FA request.
No icloud.xx services also (obviously).
I am sure I am missing something.
Thanks, best regards…
Hassbian under venv on RPi 3.
ps same after rebooting, changing the password etc. It gives “Invalid email/password combination”. These infos should be buried somewhere (not in the icloud file I deleted), but I cannot delete it. Any hint?
Have a similar issue Wemo’s work fine, but sonoffs running Tasmota with Wemo emulation are not detected
You get the _2 device_tracker entity if you still have the old device in known_devices.yaml. That is also why it seems to be stuck as being at home, as the one from known devices (without the _2) will be stuck on its last state before the update. Delete it from known_devices.yaml and then restart Home Assistant.
Edit: You can change the friendly name end entity picture using customize like you can do for any other entity
I assume this has to be done after updating or it will generate config errors.
What is going to happen to the 30 or so friendly names I already have set up for my Lifx lights? Will they all have to be redone? Same for the dozen or so (mqtt discovery) esp devices?
Nothing. The integration hasn’t changed, just how it is discovered. Since you already have it set up, exactly nothing changes 
This mainly impacts new users.
1 Like
I have an Ecobee thermostat already configured in HA. I upgraded from 0.93.2 to 0.94.1 and now it shows under Integrations as a HomeKit Accessory with a Configure button. I’d love to set it up so that I have local control, but nothing happens when I click the Configure button. I don’t see any errors in the log. Do I have to remove the current way it is included in HA before I can configure it via the HomeKit controller?
(I’m running Hassio in Docker on Ubuntu on an older NUC).
Edited to add: After several HA restarts to get my z-wave network to come up in a timely fashion, I it now asks for my HomeKit pairing code when I click Configure. But when I enter my code, it fails with
An unhandled error occured while attempting to pair with this device. This may be a temporary failure or your device may not be supported currently.
My thermostat is supported.
Edited to add: Okay, I finally got it to work, after trying about 6-7 different codes, with multiple invalid code errors and unhandled exceptions, it finally worked. I don’t know why it was so finicky. I’ll leave this post here in case it helps someone else. The answer is: you don’t have to remove the previous integration, this will just make a second climate sensor. If it doesn’t work, just keep generating codes and try again!
@fritz_hh I am using eq3 bluetooth climate devices with 0.94.3 and it works just fine. I am using Raspbian and a manual install of HA. My only problems were updating Python from 3.5 to 3.7 and a complete reinstall of HA to remove all leftovers of Python 3. Bluetooth works just fine.
This no longer works after 0.94 upgrade.
Any ideas how to fix?
updated:
switch:
platform: template
switches:
garagetemplate:
value_template: ‘{{ states.switch.Garage.attributes.sensor_state == “off” }}’
turn_on:
service: switch.turn_on
entity_id: switch.garage
turn_off:
service: switch.turn_on
entity_id: switch.garage
friendly_name: ‘Garage Door’
Suggest you fix up the formatting of your code, as nobody will be able to determine the issue