If the app is logging that it changed level, then it isn't probably a motion lighting issue.
When the app says it is setting the level, do you see an event on the device event log? Or no event at all?
It's been a while so i'll do it again (it is in this thread but we have had a few updates since) but from memory, yes all logging looked correct and the driver looked like it was sending but i think it was a case that more than 3 messages would be to much for the driver so the last message would just be dropped. then on the next trigger because the light was already on and at the level the colour would then get set.
Wait, which is it?
Is this an app issue, or a device issue? If the app is sending the commands and the device is not working properly, that's a device issue. Which problem are we trying to figure out?
the conclusion from yourself was it might be a driver issue and you tagged @mike.maxwell to check.
I'll grab some logs again to confirm that there have been no changes but I don't recall anything in the release notes.
Motion detector logs
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:56:42.739 pm [debug](http://192.168.1.81/device/edit/596)NotificationReport: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:0, sequence:false, eventParametersLength:0, eventParameter:[])
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:56:42.686 pm [debug](http://192.168.1.81/device/edit/596)parse: zw device: 21, command: 7105, payload: 00 00 00 FF 07 00 00 00
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:56:42.530 pm [info](http://192.168.1.81/device/edit/596)(SmB) Motion motion is inactive
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:56:42.525 pm [debug](http://192.168.1.81/device/edit/596)SensorBinaryReport: SensorBinaryReport(sensorValue:0)
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:56:42.484 pm [debug](http://192.168.1.81/device/edit/596)parse: zw device: 21, command: 3003, payload: 00
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:55:28.010 pm [debug](http://192.168.1.81/device/edit/596)NotificationReport: NotificationReport(v1AlarmType:0, v1AlarmLevel:0, reserved:0, notificationStatus:255, notificationType:7, event:8, sequence:false, eventParametersLength:0, eventParameter:[])
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:55:28.007 pm [debug](http://192.168.1.81/device/edit/596)parse: zw device: 21, command: 7105, payload: 00 00 00 FF 07 08 00 00
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:55:27.797 pm [info](http://192.168.1.81/device/edit/596)(SmB) Motion motion is active
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:55:27.795 pm [debug](http://192.168.1.81/device/edit/596)SensorBinaryReport: SensorBinaryReport(sensorValue:255)
[dev:596](http://192.168.1.81/logs#dev596)2019-02-09 03:55:27.792 pm [debug](http://192.168.1.81/device/edit/596)parse: zw device: 21, command: 3003, payload: FF
the app
[app:742](http://192.168.1.81/logs#app742)2019-02-09 03:56:42.646 pm [info](http://192.168.1.81/installedapp/configure/742)Delaying off for 2 minutes
[app:742](http://192.168.1.81/logs#app742)2019-02-09 03:56:42.607 pm [info](http://192.168.1.81/installedapp/configure/742)Motion inactive (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 03:55:27.957 pm [info](http://192.168.1.81/installedapp/configure/742)Not turning on switch: wrong switch mode Night-Sleep
[app:742](http://192.168.1.81/logs#app742)2019-02-09 03:55:27.905 pm [info](http://192.168.1.81/installedapp/configure/742)Setting color to hue:100 sat:100 level:1
[app:742](http://192.168.1.81/logs#app742)2019-02-09 03:55:27.857 pm [info](http://192.168.1.81/installedapp/configure/742)Motion active (SmB) Motion
the zigbee light
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.442 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent colorMode is CT
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.441 pm [debug](http://192.168.1.81/device/edit/513)evt- rawValue:2, value: CT, descT: (SmB) Pendent colorMode is CT
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.439 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent color is Polar
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.422 pm [debug](http://192.168.1.81/device/edit/513)parse description: read attr - raw: E5A70303000A08003002, dni: E5A7, endpoint: 03, cluster: 0300, size: 0A, attrId: 0008, encoding: 30, command: 01, value: 02
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.234 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent saturation is 100%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.232 pm [debug](http://192.168.1.81/device/edit/513)evt- rawValue:254, value: 100, descT: (SmB) Pendent saturation is 100%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:29.224 pm [debug](http://192.168.1.81/device/edit/513)parse description: read attr - raw: E5A70303000A010020FE, dni: E5A7, endpoint: 03, cluster: 0300, size: 0A, attrId: 0001, encoding: 20, command: 01, value: FE
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.898 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent hue is 100%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.897 pm [debug](http://192.168.1.81/device/edit/513)evt- rawValue:254, value: 100, descT: (SmB) Pendent hue is 100%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.876 pm [debug](http://192.168.1.81/device/edit/513)parse description: read attr - raw: E5A70303000A000020FE, dni: E5A7, endpoint: 03, cluster: 0300, size: 0A, attrId: 0000, encoding: 20, command: 01, value: FE
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.696 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent was set to 1%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.694 pm [debug](http://192.168.1.81/device/edit/513)evt- rawValue:2, value: 1, descT: (SmB) Pendent was set to 1%
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.678 pm [debug](http://192.168.1.81/device/edit/513)parse description: read attr - raw: E5A70300080A00002002, dni: E5A7, endpoint: 03, cluster: 0008, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 02
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.461 pm [info](http://192.168.1.81/device/edit/513)(SmB) Pendent was turned on
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.456 pm [debug](http://192.168.1.81/device/edit/513)evt- rawValue:1, value: on, descT: (SmB) Pendent was turned on
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.452 pm [debug](http://192.168.1.81/device/edit/513)parse description: read attr - raw: E5A70300060A00001001, dni: E5A7, endpoint: 03, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 01
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.403 pm [debug](http://192.168.1.81/device/edit/513)parse description: catchall: 0104 0008 03 01 0040 00 E5A7 00 00 0000 0B 01 0400
[dev:513](http://192.168.1.81/logs#dev513)2019-02-09 03:55:28.158 pm [debug](http://192.168.1.81/device/edit/513)parse description: catchall: 0104 0300 03 01 0040 00 E5A7 00 00 0000 0B 01 0601
the lamp events
the app
and settings
So as you can see everything looks like it says its sent but anything after the level isn't sent so when the light reports back in its still in CT colour mode and has only dimmed down and not gone to the colour.
Zigbee.
something has changed since last time I did all these checks now it doesn't work at all. So before if the app triggered the light would turn on to the correct level but just wouldn't go to red, but if the detector went inactive and the app started its time out and you retriggered the detector then the light would go to red. This is why I believed it was something to do with the driver/light because i believed that the ON being sent then the level and the saturation then hue was tomany for the driver/ lamp to handle at the same time. so when it triggered again the ones that would get missed the 1st time would then get picked up as the driver or app would ignore the ON and the level as it was already on so only the remaining colour values would get sent. This no longer seems to be the case and nothing gets resent instead the app just says motion again and restarts its timer.
Edit:
maybe this is connected to the override fix, as i've never seen the top log before? I'll remove the override option and retest.
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:22:26.810 pm [info](http://192.168.1.81/installedapp/configure/742)Override ended by (SmB) Pendent turned off
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:22:25.551 pm [info](http://192.168.1.81/installedapp/configure/742)Turning off
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:20:25.363 pm [info](http://192.168.1.81/installedapp/configure/742)Delaying off for 2 minutes
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:20:25.331 pm [info](http://192.168.1.81/installedapp/configure/742)Motion inactive (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:19:04.917 pm [info](http://192.168.1.81/installedapp/configure/742)Motion active (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:18:49.589 pm [info](http://192.168.1.81/installedapp/configure/742)Delaying off for 2 minutes
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:18:49.381 pm [info](http://192.168.1.81/installedapp/configure/742)Motion inactive (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:17:26.774 pm [info](http://192.168.1.81/installedapp/configure/742)Motion active (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:17:15.307 pm [info](http://192.168.1.81/installedapp/configure/742)Delaying off for 2 minutes
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:17:15.269 pm [info](http://192.168.1.81/installedapp/configure/742)Motion inactive (SmB) Motion
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:16:00.585 pm [info](http://192.168.1.81/installedapp/configure/742)Not turning on switch: wrong switch mode Night-Sleep
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:16:00.543 pm [info](http://192.168.1.81/installedapp/configure/742)Setting color to hue:100 sat:100 level:1
[app:742](http://192.168.1.81/logs#app742)2019-02-09 04:16:00.499 pm [info](http://192.168.1.81/installedapp/configure/742)Motion active (SmB) Motionosram zigbee and I have 10 all around my hub only other zigbee stuff is ST presence sensors and a xbee device I added after I noticed this issue to see how everything was connected. I think everything is connected to the hub with also multiple other routes back (hub is pretty central with max 10M to each device) strong signal to every device.
nope doesn't make a difference to remove override, but i do believe it's the driver, it seems like because the driver thinks the saturation and hue are correct it doesn't send anything to fix it
Is the light, at the time of that screenshot, in CT mode with color temp 6535? If not, what state is it in?
yes it's in CT mode at 1% at what looks like to me around 6500. I just confirmed by using the driver to send 6500 and nothing changed
What state is it supposed to be in?
1% and RGB RED
before you ask, yes if i send sat of 100 and hue of 100 it goes to RGB and the colour is red
What happens when you set hue to 100? Or 99
Show the device after
a picture of the device or the screen grap of the driver i just did?
Latter
