The Devices page looks nice, should be much easier to manage entities than the other methods.
I’m looking forward to trying out the Device automations. Currently though, the trigger is not showing anything for my light switches (Z-Wave), it presents two empty fields which when selected have no effect. I’ve refreshed the UI a few times and I’m using the default theme. Same behavior in both Chrome and Firefox.
It has arrived!
Thank you. Being Updated . . . cheer.
Awesome birthday release!
The UX team is on fire 
!
Congrats to expanding the full time team and kudos 
to all who support HASS with their cloud subscription! What a great sustainable Open Source story!
I’ve updated Hass.io to 0.99.0 and made the changes for Pi Hole as per the docs, and receive the following error on boot;
2019-09-19 13:52:25 ERROR (MainThread) [hole] Can not load data from *hole: pi.hole
2019-09-19 13:52:25 ERROR (MainThread) [homeassistant.components.pi_hole] Unable to fetch data from Pi-hole
Pi Hole is installed via Community Hass.io Add-ons.
Any ideas? Anyone have a working config they can share?
With the further changes to the Unify integration I’d like to try once more to see if I can get an answer to some questions.
I recently got all of my new unifi network equipment running and set up the Unifi integration in HA. And, as expected, it added every single device on my network to my entity registry. That’s OK, since we now have a way to deal with all of those we really don’t want to track.
I went thru the entity registry and selected all of the ones I don’t want to be tracked and turned off the “enable entity” switch. That worked as far as removing them from showing up as entities in the states page. But they all still show as “unavailable” in the entity registry…all 50 or 60 of them… So now I have a very long list of device trackers to scroll thru every time I need to go do any work in the entity registry.
Since we also have the ability to “delete” the entity from the entity registry I thought I would do that to shorten up that list. Then when I click on the “delete” button I’m greeted with this pop up:
What does that mean?
Why would deleting an entity not remove that entity from HA? Where will it still be? in some sort of “.storage” file limbo? Is there anyone who can answer this question?
And as a follow on, let’s say that I decide I don’t want to track an entity so I click the “delete” button so my entity registry isn’t cluttered up with those 60 entries that I don’t care about. Then let’s say that later I decide that I want to actually track the entity again (one of my kids decides to move back in for a while, or whatever). How do I get that entity back into the system again if there is no longer any manual device tracker configuration for individual entities?
Before this new system was implemented the entity was still listed in the known_devices.yaml file and I could just turn the entity tracking (and, hence, it’s existence in the system) on & off at will in there.
I think I may be missing something critical in how this new system is suppose to work.
with the cast.show_lovelace_view service, I can’t get anything to display, it shows the connected screen on my home hub. for the view_path, I have a view with url path defined as downstairs, so I use that for the “view_path” option, yet nothing shows. I can manually cast from the frontend fine.
Hi team,
Thank you for that update!
I’m having trouble integrating withings.
STEP 3 - AUTHORIZE HOME ASSISTANT
-> Conf is valid
-> Home assistant restarted
-> New device discovered: Withings
X issue 1: clicking the configure button next to withings in the integration page doesn’t do anything with the following error log:
2019-09-19 10:17:38 ERROR (MainThread) [frontend.js.latest.201909181] https://mydomain/frontend_latest/chunk.43dcfc6e5b8d18714299.js:1007:164 Uncaught TypeError: Cannot read property 'item' of undefined
I then tried the following workaround for that 1st issue:
-> “+” button / “Withings” works
-> Select user profile and submit ::: Redirected to Withings website
-> Select user profile “Allow this app”
-> Redirected to my home assistant “This step requires you to visit an external website to be completed” / Open website ::: Redirected to Withings website
-> Select user profile “Allow this app”
X issue 2: " 500 Internal Server Error, Server got itself in trouble"
(also tried changing the domain part of the url with local name and got the same result)
Checking the logs, here is what I can find:
oauthlib.oauth2.rfc6749.errors.MissingTokenError: (missing_token) Missing access token parameter.
the failing url looks like this: https://abc.ui.nabu.casa/api/withings/authorize?flow_id=def&profile=ghi&code=jkl&state=mno
Did I miss anything ?
Thank you all
I still manage devices this way, I also use Unifi equipment.
sonoff_5891:
hide_if_away: false
icon:
mac: DC:4F:22:5B:XX:XX
name: sonoff-5891
picture:
track: false
esp_63f006:
hide_if_away: false
icon:
mac: 84:0D:8E:63:XX:XX
name: ESP 63F006
picture:
track: true
I’m having exactly the same issue, except I have a local setup instead of nabu.casa.
I’ve worked out the solution, the documents on this need to be updated - they do not specific the need to list the IP and Port of the Pi Hole host.
Using this as per the docs did not work;
pi_hole:
Using this as per the docs did not work;
pi_hole:
host: IP_ADDRESS
Using this as per the PR page did not work;
pi_hole:
host: pi.hole
Working config in configuration.yaml is;
pi_hole:
host: 192.168.1.101:4865
My Hass.io install is on the machine at 192.168.1.101. I will submit a PR to update the docs with this.
Seeing this error with 0.99 that I have not seen before:
https://10.1.1.100:8123/frontend_latest/chunk.43dcfc6e5b8d18714299.js:1007:141 TypeError: e.model is undefined
Also HA has discovered a certificate expiry integration though I am unable to configure it. Clicking on ‘Configure’ does nothing.
I do have this existing sensor config:
- platform: cert_expiry
host: my_domain_redacted.duckdns.org
Though this sensor is now unavailable in my Lovelace front end.
I could not find any sensor in the dev tools states page similar to my previous sensor.
Is it possible to have two pihole instances?
According to this Github issue, it looks like the re-factoring of the component has broken the ability to have multiple instances running.
Tom - it’s now an integration. Try removing from config, restarting then adding integration, restarting and adjusting the lovelace card.
I will but the docs do say it should be possible manually:
has the name of it changed? check states?
This update killed my trådfri connection. Can’t even reconnect it under integrations. I’m 100% sure that the code is correct. Screenshot_20190919_074337|230x500
Nope. Was working before the update.
After removing the config and restarting the discovery has gone away. Grrr…
manually add it + bottom right. Certificate.
