Simple question. I bought one of the Presence Sensor ES1 for my kitchen and it works great. Just bought one for my master bath. It is in my office right now for testing first. I can not figure out why it is RED it enrolled good. Any ideas?
Did you refresh the device page? Those icon do not update dynamically.
You may also want to use the Community Driver, those are also illuminance sensors, if you have any need for indoor illuminance.
That icon just indicates that motion was active when the Devices page was refreshed. It does not indicate a problem. 
Note: The icon status on the Device page does not continuously refresh as device status changes - you need to reload the Device page to refresh the displayed status.
Examples:
Motion:
Contacts:
Yes sir, I did both - Note: The icon status on the Device page does not continuously refresh as device status changes - you need to reload the Device page to refresh the displayed status.
Not sure what you mean by above. Are you saying that the M1 Master Bath isn't showing the correct current state on the Device tab, even if you refresh the page?
Does the device show the correct current state on it's Device page, like below? Note that I'm using the community driver that @chrisbvt linked to above, so the details of my Device page for the Linptech will be different from yours, but the "Motion" in Current States on yours should correctly show active or inactive, and does update as soon as the state of the device changes.
I agree, that should always match the motion state, so I wonder if the device is paired correctly and actually changing the motion attribute. It would be very odd for those not to match after a device page refresh.
That is strange. I did use the built-in driver for a period of time, but I don't remember there being just a single attribute for motion. Those report distance as well, so you should have more attributes than that.
Does it ever go inactive? Maybe those can mismatch if the device is not actually connected.
Yup...if the status on the M1 Master Bath device page isn't updating in real time he might need to do a reset/re-join of the sensor just to be sure things are connected/communicating as expected.
I switched one of my sensors to the built-in driver, and I'm seeing the same as above...only Motion. Illuminance is shown as a Capability but doesn't seem to work, I get a "null" result when I try to use the built-in driver illuminance capability as a trigger in a rule.
Preferences does show Lux reporting settings, but no lux reported yet. Never used this driver so not sure if that's a known issue or not.
Using the built-in driver motion does update as expected, immediately on the individual Device page, and after a refresh on the Device tab.
@Randy513 - I'd do a reset/re-join of the sensor. Start Zigbee pairing on your hub, then put the Linptech back in pairing mode and you should see the hub report that it found a previously joined device. The device will re-join as the same device it currently is, and you can see if that re-join helps get the device in a better state/better communication.
OK, so you've reset/rejoined the sensor. You should check to see that reported Motion status updates in real time on the sensor's individual Device page, and that motion status upates correctly when you do a refresh on the Devices tab.
You should know that these Linptech sensors are known to sometimes fall off the Zigbee mesh. They look like they are working but stop reporting motion events. Not all users experience this problem, and not all devices on a users's hub may experience the problem. But it's a real issue.
Those of us who experience this issue (me included) have the sensors connected via a smart plug and reboot them on a scheduled basis (weekly-ish) to keep them connected. Very much a YMMV issue that you may or may not run into this issue. Doesn't matter which driver you use, the issue is independent of the driver.
Lots of info on this device and the community driver in the Linptech driver topic that Chris posted above...
I have my Kitchen reset every night at 2:00 am 
No - very difficult to parse, screen caps of logs are always preferred.
I've no idea what your current status is...does the motion status of the sensor update in real-time on its individual device page after the reset/re-join? If so, you could have a weak connection to the sensor in its location, you could try moving it closer to your hub and see if the real-time reporting works. If so, you might need a Zigbee repeater between your hub and the sensor.
Hi Randy,
Troubleshooting this device using the HE stock/inbuilt driver is not easy, but it is possible. Lets try to understand first where the problem is.
When a device does not work as expected, try first to understand whether it stays connected to your C8 hub. Don't think about the automation rules it is used in at this first stage. Concentrate on troubleshooting looking at the device logs and events only. When you see that the sensor reliably reports motion active / motion inactive for at lest several minutes, you can continue with the automations.
The first thing to to is to enable the Debug logging from the device web page Preferences tab. Click on the toggle control to set it enabled, then click on the green Save button :
Then switch to the Logs tab and click on the refresh icon (on the top right corner of the screen). You should see a 'debug logging is: true' warning message in the log.
When the device is online and connected to your hub, you will see also some other Debug messages as in my screenshot example :
dev:41982026-07-18 07:45:02.721debugskipped:[raw:8E3701E0020805E02005, dni:8E37, endpoint:01, cluster:E002, size:08, attrId:E005, encoding:20, command:0A, value:05, clusterInt:57346, attrInt:57349]
dev:41982026-07-18 07:45:02.176debugskipped:[raw:8E3701E0020804E02005, dni:8E37, endpoint:01, cluster:E002, size:08, attrId:E004, encoding:20, command:0A, value:05, clusterInt:57346, attrInt:57348]
dev:41982026-07-18 07:45:02.128debugskipped:[raw:8E3701E0020A0AE0215F00, dni:8E37, endpoint:01, cluster:E002, size:0A, attrId:E00A, encoding:21, command:0A, value:005F, clusterInt:57346, attrInt:57354]
dev:41982026-07-18 07:45:02.079debugskipped:[raw:8E3701E0020A0BE0215802, dni:8E37, endpoint:01, cluster:E002, size:0A, attrId:E00B, encoding:21, command:0A, value:0258, clusterInt:57346, attrInt:57355]
dev:41982026-07-18 07:45:00.681debugskipped:[raw:catchall: 0000 8021 00 00 0040 00 8E37 00 00 0000 00 00 0100, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:8E37, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[01, 00]]
dev:41982026-07-18 07:45:00.530warndescription logging is: true
dev:41982026-07-18 07:45:00.528warndebug logging is: true
dev:41982026-07-18 07:45:00.526infoupdated...
These "skipped:[raw:catchall: 00 .....", "skipped:[raw:8E3701E0020A0BE0215802, dni:...." debug messages means that something was received from this device. It is online and communicating to the hub.
Go to the Commands tab and click on the Refresh button :
Then, switch back to the Logs tab and click on the refresh Icon. You should see a response from the Zigbee device :
If you don't see all these debug logs (as in the screenshots that you posted so far), your device has disconnected and is not more reachable by the hub. Stop here with any other tests (RM rules, dashboards, etc..).
What to try next :
- Enable the Debug logging and click on Save.
- Pair the device once again to your hub.
- Quickly click on the 'Found and reconnected ...." hyperlink, this will re-open the device web page
- Go to the logs tab. Click on the refresh icon.
Do you see a lot of Debug messages? If yes, this means there was successful communication during the re-pairing process. But this is not enough - the device must stay connected to the hub!
Next (most important) :
- Wait one minute.
- Click on the Refresh command button (Commands tab).
- Go back to the Logs tab, refresh. Do you see new Debug logs?
If yes - your Zigbee device has stayed connected and you can continue testing the motion active/inactive functionality.
If there are no new Debug logs, this means the device has left the Zigbee network. Stop here. You will need to try some alternative Zigbee pairing methods.
What is your case?
It is about 2:45 am and I just got up to get a drink of water and saw your message. I did as you said above and here is a screenshot of the log.
It is now about 2:55 am
I am going back to bed hope this is a help
Can you explain to me why kitchen works fine? Same device, same driver.
I got excited, walked in my office and lights came ON - first time. I went out of the office for a few minutes lights they did go off. However it appears to be working more like a motion, because if I just sit in my office it does not trigger.
Just sitting here - for 10 minutes
Not picking me up. Bedtime
Hi Randy,
We are making progress because each test gives us more information. However, the office light turning on and off does not yet prove that this sensor is communicating with the hub. I suspect the built-in driver may generate motion events when the Configure button is clicked, so those events could be misleading.
Your kitchen sensor working confirms that this model can work with your hub, but it does not confirm that the Master Bath sensor is currently connected. We need the Debug logs from the new sensor to determine that.
In your screenshots, I still do not see the Debug messages that I need. Please do just this next step:
- Open the device page for M1 Master Bath Presence Sensor.
- Open the Preferences tab.
- Turn Debug logging on.
- Click the green Save button.
- Open the Logs tab and click the refresh icon.
- Take a screenshot showing the new log entries and post it here.
The screenshot should include lines marked debug, including “debug logging is: true.”
Please do not worry about the automation rules yet. First, we need to confirm from the Debug logs that this sensor is staying connected to your hub. Once we confirm that, we will continue one step at a time.