hi,
using zigbee2mqtt - sensor Aqara motion P1 provided / has reading of the Illuminance level.
After upgrade to the latest HA … inside the automation - i am not able to create condition based on the Illuminance level… any idea?
thanks!
Can you see the illuminance level entity on the device page in HA?
If yes, is it showing a value, or is it unknown?
If it is visible & it’s showing a value, how exactly are you trying to add it as a condition in the automation?
yes
value
the illuminance disappeared from the original automation and there is no Option for it … after upgrade
there was separate item Illuminance
thanks
You were probably using device Id instead of entity Id. Device Ids are subject to change and are not recommended (read this)
To fix your automation, instead of selecting “Device”, choose “Numeric State” and search for a sensor named something like sensor.motion_sensor_2_illuminance. This one will never change and can be used safely.
@ShadowFist not sure what do you mean…
inside the condition I selected Entity → numeric state … but still… illuminance is not there. thx
edi2:
i have also Hue motion sensors… so illuminance is there…
but illuminance from Aqara motion sensors is not exposed there.
might be a bug?
Hmm, hang on. Did you also update Z2M to a version > 2.0.0 recently?
If so, it’s one of the listed breaking changes and I can see the P1 motion sensors on that list (RTCGQ14LM, RTCGQ15LM). Your Philips Hue motion sensors are also on that list (9290012607, 9290019758, 9290030675, 9290030674), so I have no idea why they are still working:
Renamed illuminance_lux to illuminance, this breaks in two ways: illuminance_lux has been removed and the value of illuminance changes. Home Assistant users might have to manually enable this sensor via Home Assistant. This affects the following devices: 83633205, MOSZB-140, MOSZB-153, EFEKTA_iAQ3, EFEKTA_PWS_Max, EFEKTA_PWS_MaxPro, EFEKTA_eON29wz, EFEKTA_eFlower_Pro, EFEKTA_iAQ, E2134, POK004, POK011, ROB_200-070-0, HK-SENSOR-4IN1-A, AU-A1ZBPIRS, RADON TriTech ZB, TS0601_illuminance_temperature_humidity_sensor_1, TS0202_3, S-LUX-ZB, TS0222_light, THE01860A, TS0222, LCZ030, MIR-HE200-TY, XFY-CGQ-ZIGB, TS0601_smart_human_presence_sensor_1, Y1_IN, ZY-M100-S_1, ZY-M100-S_2, WZ-M100, ZG-205ZL, ZG-204ZM, YXZBRB58, ZY-M100-24G, ZY-M100-24GV2, ZY-M100-24GV3, MTG075-ZB-RL, RT_ZCZ03Z, ZY-M100-S_3, ZG-205Z, 8750001213, HSE2927E, ZB003-X, 07502L, JS-MC-SENSOR-ZB, KK-ES-J01W, KMPCIL_RES005, RTCGQ11LM, RTCGQ12LM, b-parasite, 7A-SS-ZABC-H0, 5AA-SS-ZA-H0, RTCGQ14LM, RTCGQ15LM, ZNCLBL01LM, GZCGQ01LM, GZCGQ11LM, 07047L, 9290012607, 9290019758, 9290030675, 9290030674, 545D6306, CCT595011, ZSS-ZK-THL, 4512770, TERNCY-PP01, MBD-S, CTM_MBD_Dim, 3RSNL02043Z, WB-MSW-ZIGBEE v.3, MS100, USM-300ZB, PIR313-E. In case you want to have the old illuminance_lux values, enable the illuminance_raw option device specific settings (will be available from Z2M 2.1.0)
Fix should be as simple as enabling the sensor. Post a screenshot of your device page with all the disabled entities showing if you get stuck.
@ShadowFist
i am running Zigbee2mqtt version 2.1.1.
Then follow my instructions pls. Enable the “new” illuminance sensor and you should get it back.
ah, thank you so much for help! it seems it works now … no clue why they did such a change.
It very important to read all the breaking changes before updating and to provide all info when creating a topic. If you had said that you also updated Z2M in your first post, I could have solved your problem 2 days ago.
Please take the time to mark my post with the Solution tag so that others with the same problem can find the answer immediately.