erik3rik
erik3rik
Well it was introduced when updating deCONZ, and is fixed by rolling deCONZ back again. So it is a deCONZ implementation issue.
Same here, rolling back solves the issue. I guess we'll have to wait for a new update before doing anything else.
There should be an EASY way to change the keyboard layout of the OS. Arguments like "well it is only for debugging, you should not need that" as seen above...
> You need to remove the invalid device class This comes automatically from the non-community integrations and the moble app. The sensors are automatically set up by Home Assistant /...
It will not get fixed. Since it kind of is, already. But the problem is that it was not fixed properly. As per my _observation_ there is already a fix...
If you would just read my comment 2 posts up. The workaround was mentioned there. You will have to do this yourself, there is no other fix to this problem...
Copy the problematic entity id from the logs, go to entities, search for the entity with that id, click the entity, click the cogs-icon and then delete.
Not necessarily, as #99 was reported in April but the thing I reported above worked until the specified date in November. It may be related though, simply another instance of...
Similar, not the same. The request I tried DID work 3 days ago, 2023-11-22. If something happened last month (i.e. October) the problem is perhaps similar but not identical.
Same with paths.INSTRUMENT_PATH, both giving 404. Happened 2022-11-24 after the regular "Thursday update" window that normally is every Thursday 07:00 --> 08:00 CET. It was most likely deprecated a long...