So these seem to be good value for money IF used with the right batteries!
Using wrong batteries seems to trigger false positives.
They are quite big, compared to Philips Hue, but just a fraction of the price.
I have read multiple different reports about cooldown time (time needed to detect motion again): what are your experiences?
What about battery life?
@nikscha: it doesn’t seem that the LED can be turned off for this one.
Im looking for a cheaper ZigBee lux sensor. Want to set it in the living room to trigger lights.
Is it any good?
I - and many other long-time users here- would not use a motion sensor in a room where you sit because you will be in the dark inevitably.
What do you mean? I am not interested in the motion sensing capability.
I intend to write an automation to turn on my window lights at sunset and are on until a specific time. Currently I use sun angle to do this. It works OK but on cloudy days the lights should be turned on earlier. Could probably check if weather forecast is cloudy but probably easier to just measure lux. Could use a boolean as well so it only runs once a day.
It should not be used to turn off the light in that room, no. I agree to that. It can still be useful. I have a Vallhorn in my living room and use the motion sensor to turn on the light in the hallway outside the living room. That way the light in the hallway is already on when I enter the hallway. And, as @trallan, I use the light sensor in the Vallhorn, but I use it to turn off the light when the sunlight is strong enough. The primary sensor to turn on and off the light in the living room is an Ikea Parasoll on the door, as we keep the door closed when the rooom is not in use (to keep the cat out of the room).
Okay, that’s a different story.
For that situation, this seems a good, cheap device with decent battery life.
Of course you can just use the illuminance sensing capability of this sensor to measure the brightness outside.
I was referring when used as a motion sensor in e.g. a living room to control the lights in that room.
There are also quite some topics about using a motion sensor in the bathroom or toilet which presents some challanges.
Got one now. Is it possible to decrease the update frequency? It seems to update lux every 5 second. 
I must say I’m a bit disappointed with the VALLHORN product;
had a problem with Vallhorn using 1,5 volt alkaline batteries, it jammed som of my zigbee tempsensors, havent tries 1,2 volt rechargeable celle yet.
changed to 1,2 volt (ikea Ladda) and the problem was soved!
Yes, this has been mentioned multiple times: if not used with the right batteries they misbehave.
I have ordered a couple of them to test.
I have two Vallhorns connected to Home Assistant (under Zigbee Home Automation, via an
Aeotec Zi-Stick). (Home Assistant running in a Docker container in a Raspberry Pi.)
When I’m moving frequently, nearby the sensors, they immediately change the “Occupancy”
state in Home Assistant, after a move close to a sensor.
However, when there has been no motion in an hour, or two hours, they react very slowly.
The change of the “Occupancy” state in Home Assistant is then done 20-55 seconds after a move
close to a sensor.
It seems that the sensors fall asleep. 
Maybe there is a problem with the communication between the Aeotec Zi-Stick
and Vallhorn. They are perhaps not compatible to each other.
The problem arises even when the distance between the devices is short.
Do you see similar performance?
Just got my first VALLHORN sensor with new LADDA 750 mAh batteries. After pairing the sensor stays on “detected”. The Lux values do update but seem to be all over the place, going form 213 to 2 within 30 seconds whilst nothing changed in the room. I’ve also tried to repair the device trough another router device, rebooting Home Assistant and also another set of rechargeable batteries (LADDA 900 mah) without succes.
I’ve noticed the logbook keeps updating every 30 seconds with:
Bewegingssensor woonkamer Attribute Updated event was fired
11:24:07 PM - Now
Bewegingssensor woonkamer On With Timed Off event was fired with parameters: {‘on_off_control’: <OnOffControl: 0>, ‘on_time’: 600, ‘off_wait_time’: 0}
11:24:07 PM - Now
For what it’s worth, the VALLHORN firmware is 0x01000064 and I’m using Sonoff Zigbee 3.0 USB Dongle Plus V2 (the -E variant) with USB extension cable in combination with ZHA on Home Assistant 2024.11.1.
Only when I try to repair the device, without deleting it first, I get it to work once. I’ve tried that a couple of times:
Also playing with the buttons on the back, like @Pelle900 did, seems to do something once.
Since I’m using the right batteries I’m thinking my unit is faulty.
I’ve just bought one and seeing the same with occupancy permanently detected.
Battery only shows 48% so i’m recharging them and will see if that helps
I wonder if that helps. I’m now 3 days further without any improvement. My battery percentage started at 85 percent and is now at 82 percent. I have tried a few (almost empty) alkaline batteries in between but that makes no difference either.
so it was worse with full batteries (LADDA 900) although I have read that it is finicky about the batteries.
I also tried pairing directly to a TRÅDFRI bulb and the light stayed on so I’m thinking that mine is possibly faulty? Will return and try another to see if it is the same.
@drdodge, I’ve tried that as well and the light stayed on.
Yes, that’s why I bought the sensor with those (LADDA 750) batteries. When that still didn’t work after about an hour, I tried my other batteries (LADDA 900). That didn’t make any difference. Then I tried again with used alkaline batteries, but that didn’t make any difference either.
I put the original batteries back and left the sensor on, and now another day has passed, but nothing has improved. I think I’ll go back to the store next week
Ok so I got a replacement from Ikea and the new one functions correctly paired to the TRÅDFRI bulb. Have just paired it to ZHA now and seems to be ok upon first testing! So it seems the first unit was actually faulty.
This is using the LADDA 900 batteries btw
The off delay time can be set through the zha-toolkit:
Maybe I will look into creating a quirk for these 2 config options.
