coarse frost
Hello everyone, I am quite new to all that, but trying to understand something that doesn't make sense (?).
I have 2 different motion detectors:
both of them connected through Zigbee2MQTT. Both of them are not being discovered as motion detection as shown on picture - it only gives Occupancy as Sensors.
I tried setting a light on through motion detection but it all fails... What am I doing wrong?
cunning urchin
Hi, I'm a newbie to HA myself, so I can't debug your configuration, but the following might give you an idea. This is the automation for a (radar) motion sensor connected via MQTT.
description: ""
triggers:
- trigger: state
entity_id:
- sensor.presence_sensor_presence
from: "False"
to: "True"
conditions: []
actions:
- type: turn_on
device_id: f78461e83e538295a7472f063fbb027c
entity_id: 016ecdc09e98677d039f947b9741da3d
domain: switch
mode: single```Something (HA? MQTT? the motion sensor? all of them in combination?) seems to be very picky about boolean values. I spent hours fiddling with values like 1, TRUE, true, on, ON, etc., until the motion sensor's vendor pointed out that it had to be True, with a capital T, rest in lowercase.
coarse frost
Hi, I'm a newbie to HA myself, so I can't debug your configuration, but the foll...
Ok, but when you go to see Setting > Devices and find your motion detector in the Sensors list do you see the MOTION?
viscid crater
Whether the device is set up as a motion sensor or an occupancy sensor isn’t relevant to anything. In either case it is a binary_sensor entity that changes between off and on. The device_class of the entity controls whether the frontend displays it as an occupancy sensor or a motion sensor. Go to developer tools -> states and search for the entity. It will show you what the real state is, rather than the translated state that the frontend displays.
For TRADFRI, the z2m docs show it should be set up as an occupancy sensor, so it appears to be working as designed https://www.zigbee2mqtt.io/devices/E1525_E1745.html
However, your screenshot shows the state as unknown and so if it is not working of course it will not trigger your automation
viscid crater
Something (HA? MQTT? the motion sensor? all of them in combination?) seems to be...
Whatever integration you are using for that motion sensor is improperly coded. The device should be a binary_sensor instead of a sensor which would enforce the proper states of on and off. And you don’t need to guess the states, you can go to developer tools -> states and look for the entity, and it will tell you what state it is in. Then interact with the device to get it to switch to a different state, and observe the result on that page.
coarse frost
coarse frost
However, your screenshot shows the state as `unknown` and so if it is not workin...
No idea why though...
makes no sense
NVM, one things sorted:
coarse frost
ok now... I don't know what I did but I just reset the HA and it works ... it's just plain stupid lol
and actually no... it again stopped running automation even though I did not touch it and it detects occupation.
viscid crater
Are you saying the occupancy sensor is not working correctly, but your automation isn’t working? If so, post the automation code so we can help.
final kayakBOT
viscid crater
If there are any automation traces, please share the most recent. While editing your automation, in the top right are 3 vertical dots; click those and select ‘traces’. Then click that same button again and select ‘download trace’. Paste the contents of that file into a code share site, and give us the link to it.