It’s the little things that make me smile. Like this improvement. =)
The “unavailable” is clear and to the point. =)
Thanks for the update’s and Happy 6th birthday.
It’s the little things that make me smile. Like this improvement. =)
The “unavailable” is clear and to the point. =)
Thanks for the update’s and Happy 6th birthday.
anyone know how to render the unused devices table with slate theme? Mine shows up all white
Same! Ikea Tradfri not working. Hoping it´s fixed in 0.99.1
File “/usr/src/homeassistant/homeassistant/components/tradfri/config_flow.py”, line 55, in async_step_auth
self.hass, host, user_input[KEY_SECURITY_CODE]
File “/usr/src/homeassistant/homeassistant/components/tradfri/config_flow.py”, line 164, in authenticate
key = await api_factory.generate_psk(security_code)
File “/usr/local/lib/python3.7/site-packages/pytradfri/api/aiocoap_api.py”, line 195, in generate_psk
self._psk = await self.request(command)
File “/usr/local/lib/python3.7/site-packages/pytradfri/api/aiocoap_api.py”, line 155, in request
result = await self._execute(api_commands)
File “/usr/local/lib/python3.7/site-packages/pytradfri/api/aiocoap_api.py”, line 146, in _execute
_, res = await self._get_response(msg)
File “/usr/local/lib/python3.7/site-packages/pytradfri/api/aiocoap_api.py”, line 95, in _get_response
Scroll 11 posts back.
EDIT: Sorry, 10
yea i tried that and the unused devices still shows up white
From the slate.yaml:
paper-card-background-color: '#292929' # this line is already there
card-background-color: "var(--paper-card-background-color)"
Services -> frontend.reload_themes
didn’t reload the theme thank you!
Thanks for the theme fix, just added it and it’s working great for me now.
Had the same problem.
Try saving the addon config again, then take a look at the hassio logs (System log) at Hassio -> System.
I got WARNING (MainThread) [hassio.secrets] Home Assistant secrets have a invalid format
.
Turns out that secrets.yaml can not contain lists.
Same here, also under the device list, is there any way to remove the devices from that list? Would be nice if there could be a shortcut to disable, hide, customize, when you click on them
It shows Z-Wave devices that I thought i removed from HA, like none of their entities are present in the Entities Registry yet they show up in the Device list.
Love this view, hopefully the new Unused Device view can be integrated into other parts of HA like the Entities Registry, or even Customization (so you can bulk disable things, and see which ones have been working etc)
There are docs missing for (at least deCONZ) device automations in YAML.
I was able to ‘track’ them by adding automation in UI and looking at the file, but couldn’t find the description anywhere near automations nor deCONZ on website.
Good job anyway!
It can take up to an hour or so for the status to be updated. Just wait. Donb’t keep removing and readding!
I have replaced the old config with;
sensor:
- platform: pi_hole
Currently 99.2 is the latest release, but in dockerhub 99.1 is tagged as latest: https://hub.docker.com/r/homeassistant/home-assistant/tags
Ok, thnx for info? But how to fix it then? Still not clear to me? Make 1 secret for that whole config section?
Also experiencing this issue with the Withings integration. FWIW more detail will appear in your browser console:
ha-config-entries-dashboard.ts:170 Uncaught TypeError: Cannot read property ‘item’ of undefined at HTMLElement._continueFlow (ha-config-entries-dashboard.ts:170) at _.handleEvent (parts.js:434) at HTMLElement.__boundHandleEvent (parts.js:400)
_continueFlow | @ | ha-config-entries-dashboard.ts:170 | |
---|---|---|---|
handleEvent | @ | parts.js:434 | |
__boundHandleEvent | @ | parts.js:400 |
Could anybody tell me if something is needed to be added to the config.yaml for Home Assistant Cast other then;
cloud:
Im trying to cast a lovelace view, but all custom elements are displaying ‘null’ in a red box.
its working fine on my Phone and computer. (im using the custom button card)
I did subscribe to nabu casa.
Try removing that from sensor.yaml.
I only have this in my configuration.yaml, and nothing in sensor.yaml
pi_hole:
host: 192.168.1.101:4865
Thank you for the suggestion but removing it hasn’t changed the errors