Is anyone using zha component? I previously had it working and after upgrade to 107 it is looking at the default path /dev/zigbee rather than the one I have defined in the configuration.
I’m guessing (I don’t use it) that the integration is cloud access only. Not local. Interestingly the docs do not include the IoT class information like most integrations.
Or it could be an error in the docs and should be your qvr credentials.
Edit: did a bit of googling. Definitely looks like a documentation error.
In the new Samsung TV integration solution, it seems that for the non-legacy application (samsungtvws) there’s the option to get the currently running application from the TV. The legacy application (samsungctl) does not have this.
Is it possible to make the non-legacy application utilise this functionality even though the legacy application doesn’t support it?
Am I the only one that have the problem that Safari in IOS no longer ask to save credentials and asks for username and password everytime you open HA using 192.168 type URL? Under my user name the number of sessions saved has reached more than 20 in an hour. I have checked that the browser accepts cookies. I have tried to clear browser cache. Safari will not remember the session any more and it does not offer to save the session. This is impossible to live with
Just create a new Lovelace Dashboard. By default, the new created dashboard will be generated (and kept up 2 date) until you modify it manually. It will be a similar experience as the old states UI.
Getting the errors “Custom element doesn’t exist: hui-conditional-card.” and “Custom element doesn’t exist: hui-entity-filter-card.” Neither of these are custom cards so I’m at a loss here. Even stranger, my CUSTOM cards were working fine even before I moved the resources over to configuration.yaml
I’ve done a resource reload, a reboot AND cleared my site cache completely but still unable to find a logical reason these cards aren’t loading… could use some help.
I’m getting “Custom element doesn’t exist: hui-group-entity-row.” with custom:fold-entity-row in 0.107.0, worked fine in 0.106.5. Using YAML mode, config looks like this: