Repeating logs for Zigbee Iris motion sensor

🛎️ Get Help
1

I'm seeing logs like this for my Iris motion sensor using the built in driver:

2018-11-30 10:52:26.970 am infoMBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

2018-11-30 10:52:17.939 am infoMBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

2018-11-30 10:52:09.989 am infoMBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

2018-11-30 10:51:59.890 am infoMBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

2018-11-30 10:51:50.821 am infoMBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

[dev:397](http://192.168.13.46/logs#dev397)2018-11-30 10:51:41.788 am [info](http://192.168.13.46/device/edit/397)MBR Motion Sensor by Door (Iris 2) temperature is 62.08°F

Any idea why it would do that? Is that a zigbee issue? I've seen this with other devices but starting with this one as it's a built in driver and pretty common device.

2

Isn't this just normal logging?
I don't think it's anything to be concerned with.
I might not be understanding the issue.

3

Can you post a screenshot of your Device Events page (from Device Detail page click "Events") for the corresponding time-frame?

4

That's definitely not normal. It's repeating the same temp change.

5

It's repeating the same "rounded" temperature is what I am thinking...

2 Likes
6

hmm I thought it would report on an interval regardless of what the value was. I don't pay enough attention to mine clearly.

7

I've seen the same issue, here is a contact sensor that had two open messages before the close message. I know the door was opened and then closed only once. It causes headaches with my rules if the door is opened and closed in a couple of seconds and then the second phantom open message comes in and I start getting alerts. I've seen it with Iris, NYCE, and Visonic sensors,

dev:1692018-11-30 10:37:39.319 am infoGarage Refrigerator Door Sensor was closed

dev:1692018-11-30 10:37:28.053 am infoGarage Refrigerator Door Sensor was opened

dev:1692018-11-30 10:37:22.543 am infoGarage Refrigerator Door Sensor was opened

8

When my Iris devices start acting up it is ALWAYS related to battery state, regardless of what the actual battery reading is.

J

2 Likes
9

I have a similar behavior, strange is on the events there is nothing about temp.

Screenshot_20181130-133131_Chrome
Screenshot_20181130-133131_Chrome.jpg1799×195 121 KB

Screenshot_20181130-133224_Chrome
Screenshot_20181130-133224_Chrome.jpg2220×466 105 KB

10

@bobbyD - 1 event

image
image1818×350 41.4 KB

I think you are looking over the timestamps. 6 times over a 2 minute period.

Maybe it is normal...but it looks off from most of my other devices.

11

I overlooked them when I spoke.

12

I've seen this with other sensors too...but I'm narrowing scope right now and this one is pretty common at least to start with.

Yep, changed that just to make sure. It's very consistent.

13

I had one of these do it when the battery was new but it was on the very outer edge of the zigbee network. Also had one do it when battery was low.

14

Iris motion devices only report the temperature when it actually changes; they do not do it on a non-adjustable firmware built-in schedule. This is what a normal report should look like:

image
image.png985×245 92.3 KB

J

15

Correct, similar behaviour with iffy Zigbee signal devices; nothing a repeater cannot solve!

16

I have XBee and Smart Outlets for repeaters, I've tried new batteries, healing the mesh, rediscovering the devices, and turning off everything else that is on 2.4 Ghz in the house but I still have the problem.

17

Ouch!!!!!
Need to get myself an XBee some day.
Sorry, and all fresh outta ideas then.