There is in the device log. Top line and bottom line.
I wonder if it has anything to do with the motion sensor and light switch names being identical. Wouldn't think so, but ??
I understand, but it's not in the app log. Look at the device events.
I know... That's the problem.
Why isn't there one in the app log, when there is in the device log?
The app log has the first motion event... Why doesn't it get any of the subsequent ones, when they are clearly showing up in the device logs?
The firmware seems to be
dev:16362019-02-08 06:27:35.573 pm infoVersionReport- applicationVersion:5.27
dev:16362019-02-08 06:27:35.571 pm infoVersionReport- zWaveProtocolVersion:4.34
1 Like
Not the log, the events. Two very different things. The driver writes the log, and it sends the events. An app can't see the logs, only events. So show the device events page.
Sorry, I was mangling the terminology. (I should know better, that's what I get for being in a hurry)
What I posted above as device log is the data from the device event page.
Could you show a bit more, where it has the active event that did turn on the lights, as well as the one that does not?
I'm away from the house but I can post more in an hour or so.
But if you look in the event log above the very bottom event is the motion event that turned on the light and is reflected in the app log, and the event at the very top of the list is the one that did nothing in the app.
I will say, anecdotally, that when I tested that motion with a DIFFERENT light earlier it seemed to work fine. That's why I still wonder if it is something about it being the same name/device for both motion and light switch.
But I'll do another more controlled test when I get home.
Here are the logs after I once agai set up a motion light app for Master Bath Toilet Light:
first time the motion is recognized and the light set to 80%
second time motion recognized but no turning on of the light...
2019-02-08 06:41:41.695 pm infoMaster Bath Toilet Light is inactive
dev:16362019-02-08 06:41:41.693 pm debugAlarmReport zwaveAlarmEvent:0, zwaveAlarmType:7
dev:16362019-02-08 06:41:41.690 pm debugparse description: zw device: 21, command: 7105, payload: 00 00 00 FF 07 00 00
dev:16362019-02-08 06:41:21.830 pm infoMaster Bath Toilet Light is active
dev:16362019-02-08 06:41:21.827 pm debugAlarmReport zwaveAlarmEvent:8, zwaveAlarmType:7
dev:16362019-02-08 06:41:21.822 pm debugparse description: zw device: 21, command: 7105, payload: 00 00 00 FF 07 08 00
dev:16362019-02-08 06:41:15.291 pm infoMaster Bath Toilet Light was set to 30% [digital]
dev:16362019-02-08 06:41:15.277 pm debugdimmerEvents value: 30
dev:16362019-02-08 06:41:15.274 pm debugBasicReport value: 30
dev:16362019-02-08 06:41:15.270 pm debugparse description: zw device: 21, command: 2003, payload: 1E
dev:16362019-02-08 06:40:13.563 pm infoMaster Bath Toilet Light is inactive
dev:16362019-02-08 06:40:13.559 pm debugAlarmReport zwaveAlarmEvent:0, zwaveAlarmType:7
dev:16362019-02-08 06:40:13.555 pm debugparse description: zw device: 21, command: 7105, payload: 00 00 00 FF 07 00 00
dev:16362019-02-08 06:39:55.705 pm infoMaster Bath Toilet Light was set to 80% [digital]
dev:16362019-02-08 06:39:55.696 pm debugdimmerEvents value: 80
dev:16362019-02-08 06:39:55.693 pm debugBasicReport value: 80
dev:16362019-02-08 06:39:55.690 pm debugparse description: zw device: 21, command: 2003, payload: 50
dev:16362019-02-08 06:39:53.633 pm debugsetLevel value: 80, duration: 1
dev:16362019-02-08 06:39:53.536 pm infoMaster Bath Toilet Light is active
dev:16362019-02-08 06:39:53.534 pm debugAlarmReport zwaveAlarmEvent:8, zwaveAlarmType:7
dev:16362019-02-08 06:39:53.531 pm debugparse description: zw device: 21, command: 7105, payload: 00 00 00 FF 07 08 00
Ok, here are more logs and events.
- App only shows motion at
- 06:28:21
- Device events show motion at
- 06:28:21
- 06:48:36
- 06:49:33
- 06:54:02
So that is the root of my question - why are the other events not getting captured by the motion lighting app???
Note, the light was manually turned ON/OFF at 06:49:11 and 06:49:30, respectively. Needed to do that because I couldn't see in the garage since the motion light app didn't turn on the lights. 
Any other logs or events that would be useful in troubleshooting this @bravenel? Like I said, it isn't a critical issue to me, as the exact same thing seems to work fine in an RM rule, but it still seems like it would be a good thing to understand / fix.
Motion Lighting App Logs
app:6502019-02-08 06:30:35.847 pm infoTurning off
app:6502019-02-08 06:30:35.825 pm infoOverride ended by Garage Light turned off
app:6502019-02-08 06:30:35.825 pm infoTurned off by Garage Light button off
app:6502019-02-08 06:30:35.416 pm infoTurning off
app:6502019-02-08 06:29:35.356 pm infoDelaying off for 1 minute
app:6502019-02-08 06:29:35.327 pm infoMotion inactive Garage Light
app:6502019-02-08 06:28:21.278 pm infoTurning on switch [Garage Light]
app:6502019-02-08 06:28:21.255 pm infoMotion active Garage Light
Device Events
| Name | Value | Unit | Description Text | Source | Type | Date |
|---|---|---|---|---|---|---|
| motion | inactive | Garage Light is inactive | DEVICE | 2019-02-08 06:54:48.937 PM CST | ||
| motion | active | Garage Light is active | DEVICE | 2019-02-08 06:54:02.425 PM CST | ||
| motion | inactive | Garage Light is inactive | DEVICE | 2019-02-08 06:49:54.394 PM CST | ||
| motion | active | Garage Light is active | DEVICE | 2019-02-08 06:49:33.898 PM CST | ||
| switch | off | Garage Light was turned off | DEVICE | physical | 2019-02-08 06:49:30.220 PM CST | |
| motion | inactive | Garage Light is inactive | DEVICE | 2019-02-08 06:49:30.138 PM CST | ||
| switch | on | Garage Light was turned on | DEVICE | physical | 2019-02-08 06:49:11.616 PM CST | |
| motion | active | Garage Light is active | DEVICE | 2019-02-08 06:48:36.116 PM CST | ||
| switch | off | Garage Light was turned off | DEVICE | digital | 2019-02-08 06:30:35.790 PM CST | |
| motion | inactive | Garage Light is inactive | DEVICE | 2019-02-08 06:29:35.294 PM CST | ||
| switch | on | Garage Light was turned on | DEVICE | digital | 2019-02-08 06:28:23.101 PM CST | |
| motion | active | Garage Light is active | DEVICE | 2019-02-08 06:28:21.213 PM CST |
I don't know what's going on here, but you're still not showing comparable logs. You app logs just above are between 6:28:21 and6:30:35. During that period the device shows motion active and motion inactive, same as the app log.
Exactly. There are NO motion lighting app logs after that... Nothing. I showed all there was.
There SHOULD be more app logs, as there are more motion events, but there are not.
That is what others have reported too. The first motion event triggers the motion lighting rule, but no motion event after that does.
@Linvale is seeing the same thing.
It seems to be something specific to using the jasco/ge motion switch or dimmer in motion lighting as the motion AND light device.
Don't know what the exact issue is, but it is weird.
Unless the Motion Lighting app is paused, when a motion event happens it logs that event. It's not seeing the motion inactive events either. It's as if it stops seeing any events.
The only other thing you could check would be to look at the app subscriptions after it has stopped responding. It should still have the subscriptions to the motion active and motion inactive events.
Sending you a pm.
1 Like
Thanks to both of you for looking at this. One of the great things about this system is the responsiveness of the founders to this type of problem. At least I know that it wasn't something dumb I was doing (still on the learning curve for RM and other apps). It does seem that these GE/Jasco combined dimmer/lights provide some special challenges. They are great when they work and seem quite popular, so I thought it was worth pointing out something that was causing me frustration. Hope it does get sorted out. I feel a little like a patient, lying in my hospital bed, while the physicians have gone outside to discuss my prognosis. Kinda hoping it's not terminal 
Meanwhile here' s the official position if anyone else is searching for an answer: (I should point out given the title of the post this behavior proceeded the present 2.05 hub update for me)
A small tip from my observations - if you are using simple lighting, be patient, it can take a little while before the automation starts working with these (a few minutes in my case) don't know why, but its an observation. Once working it's very fast and reliable.
1 Like
The latest hot fix release should correct this problem, as long as you do not enable override. A complete fix is planned.
That was quick! Great work, as always.
Let me know if it works now.
Wow - I'll give it a go. Amazing (as always).
Yea - that works!
Now I can get on working out the best way to have motion trigger the light on and it to stay on if the door is closed, turn off when open but not be on when there is no motion and the door is closed. Would this be an override situation - is this an RM task?
You can imagine why I'm trying to do this - significant other complains if the light goes out too soon but doesn't want this light to stay on after the job is done!
Thanks for the prompt response. It would be interesting to know what was the issue - but get that may be a trade secret!
