I did quite a few updates at the same time (core, os, zigbee), but I’m assuming this is due to the zigbee update (everything had been up to date as of a month or so ago).
Anyway, I have some scripts that depend on the illuminance value from a couple of motion sensors. However, the conditions in my Automations now have a title like Current <unknown entity> illuminance with a Condition of Unknown condition
If I try to manually re-add the condition, by selecting one of the devices, like my Xiaomi light sensor, the only selectable condition is the battery level.
What’s making my really lost about what’s going on is that when I go to the device in z2mqtt, it still shows the lux reading. I just now seem to have no way to access it.
Did I make a mistake by upgrading? Am I missing something obvious that’ll bring back the missing properties? (I’m having the same issue with missing illumination from a Philiips Hue motion sensor - all other values like temp and presence are selectable when building an automation, but illuminance isn’t)
Thanks for that - had totally missed. explains the illuminance issues.
I was able to downgrade back to 1.42 and my scripts/automations started working again.
Do you happen to know if these are permanently breaking changes, or if the illuminance value from devices like these will become available in automations again sometime in the future?
Yes. Enabling the new sensor and renaming the use of it in automations etc worked for me. Btw, it will show unavailable for a bit after enabling. It’s only ephemeral.
