alexsaas

Unfortunately, no one takes care of that. Since September 2024. 😥

With the new HA Core 2024.6.4 an HAOS 12.4, the error still exists. If I try to sort the not displayed scenes by name, the following is in the logs:...

Congratulations, now with Core 2024.7.3 I also have the error with the companion App on iOS! @homeassistant And so far no one has addressed my problem. 😞 ``` Logger: frontend.js.latest.202407100...

@silamon Thank you very much for your response. Sorry for the cross posting, but since I didn't get a response in the frontend tracker and it's now in the companion...

For another test, I created a scene directly via the Home Assistant UI. Without making any changes to the state. But this scene is not displayed either. However, the number...

Thank you very much for your support and tips to find the error. I won't be able to test all of this until later. Just one thing in advance, the...

Okay, I've tried it with firefox. Same issue but the log says something different with date instead of number: ``` Logger: frontend.js.latest.202407100 Quelle: components/system_log/__init__.py:333 Erstmals aufgetreten: 10:23:43 (1 Vorkommnisse) Zuletzt...

The scenes come from zigbee2mqtt. In the screenshot scene.test I created it today directly with HA UI, as I wrote before: 

Oh! Okay, then you've probably found the origin. Even if "on" is set? Thank you for testing! It would be sad if I couldn't use the states "on" and "off"...

As i wrote before, i set the states "on" and "off" by myself with automations and Python Script. `That said, I'm going to close this one as there's nothing more...