And can you confirm you did a reset on this device (I can't tell which of the 3 devices you have reset and if this one is included)?
1 Like
I have resetted this device. But only method I know is holding the button while inserting the battery.
Is there another method for reset ?
No, I think that is the correct procedure - at least as far as I have found (which is also what I have done with mine).
1 Like
All I can say is that, this is a very chatty device. Even when on the C5 hub, (where it works) , it takes a while for it to initialize and show open/closed states.
It sends XYZ events continuously , and that may be making it difficult for the C8 hub to pair.
I don't know; just what I see.
I have one on my refrigerator door (to nag family members if the door is left open) and it has worked just fine. I did see a lot of messages about battery life with several different Zigbee hubs when I did a Google search. I didn't find any firmware updates (not surprising as old as this device is). I think, if anything, you have newer firmware than I do. It appears Centralite has replaced it with 3323-C.
1 Like
If this is the only remaining headachy device on your C8, would you ever just consider replacing it with something newer / better compatible?
I understand that sucks to consider -- I ended up having to upgrade / swap out some ZB devices to get my C8 working smoothly. For me, that ended up being the better option sanity-wise (rather than going crazier trying to do endless troubleshooting).
well of course if I have to give up, that's what I'll do.
But it is not easy.
I live in Turkey and I can't get a new one easily here.
I have to order abroad and it will take at least 3 weeks to get a new one.
Besides, I like these contact sensors because they measure temperature besides being a contact sensor.
If I have to replace it, I will have to put 2 devices (one contact sensor, one temperature sensor)
Also, the device is working on C4 and C5 hubs. Why do I have to replace it just because C8 can not work with it. I would expect Hubitat support to analyse the situation.
I just looked at the other two I have. I thought all three were the same - they look exactly the same and all three use the v4 driver. These other two are completely different firmware, software, and manufacturer (SmartThings instead of CentraLite).
interesting !!!
today, I decided to try again.
I tried several times , and in my like 6th or 7th attempt , C8 hub detected the deivce correctly. But it did not report the states (open/close , active/inactive) correct at first.
I decided to leave it alone for some time.
After about 10-15 minutes of no activity it became stable.
Now it reports correct states.
But I am not confident that it is reliable.
I'm worried that it will lose at one point.
Although I tried it at different distances to the hub and seems to work fine.
What I believe is that this device is too chatty and C8 can not process all messages in time.
I think it can be fixed by Hubitat support, but first they must understand the problem.
One of the things I read when searching for any clue that might help you - multiple people (on different brands of hubs) reported that this device was very slow to become fully operational after joining.
If you would like to post a sample of the messages you are seeing, I can compare it to mine. Also, where is it mounted? Anyplace subject to vibration? I don't know if it's that sensitive but I sometimes see an XYZ report for the refrigerator door when nobody is in the kitchen . . .
1 Like
Do you need the xyz reports from this sensor? You can probably try to turn them off if the device is now paired.
As @Eric.C.Miller said, it could be that it’s accurately reporting (very small) changes in position due to vibration.
1 Like
I don't see an option to turn off the XYZ reporting or vary the frequency or sensitivity on the device page.
which messages would you like to see ?
the device is normally installed on a door and the door is not active frequently.
But while pairing I take it on a table.
there is no problem after pairing. I had difficulty in pairing for 1 week.
Today it paired (by chance ?)
BUT, I believe this should be handled on the C8 hub firmware.
C4 and C5 hubs can pair with no difficulty.
So the issue is caused by C8 firmware.
I don’t think you can conclude it’s the firmware.
The C8 has an updated zigbee chip in it compared to older hubs. Ideally it’s completely backwards compatible.
But in reality, for some older devices, like your sensor from 2015, it may result in unexpected behavior.
2 Likes
You said it was very chatty - I think you were referring to the XYZ reporting. I'd like to compare a sample of what you are seeing in your logs to what I am seeing in my logs.
1 Like
What I believe (because what I experience) is that C8 can not handle communication with this chatty device. It might be a design problem on this sensor. But it is easily detected by older hubs. That means, C8 is failing to communicate with it. And I think this can be handled by some adjustments on software of the hub.
This is what I see, I might be wrong of course. Ideally , I wish someone from Hubitat support to check what really is happening.
@Eric.C.Miller - I would like to provide you logs for what's going on but the problem was at the phase of pairing. Now all I see is the log below:
dev:3892024-01-08 00:27:04.607infoBedroom Door is inactive
dev:3892024-01-08 00:27:01.638infoBedroom Door is [x:-16,y:-18,z:-1005]
dev:3892024-01-08 00:27:00.637infoBedroom Door is [x:-21,y:-15,z:-1007]
dev:3892024-01-08 00:26:59.630infoBedroom Door is [x:-20,y:-17,z:-1006]
dev:3892024-01-08 00:26:58.636infoBedroom Door is [x:-18,y:-19,z:-1004]
dev:3892024-01-08 00:26:57.641infoBedroom Door is [x:48,y:-106,z:-1109]
dev:3892024-01-08 00:26:57.037infoBedroom Door was closed
dev:3892024-01-08 00:26:56.626infoBedroom Door is [x:-76,y:-96,z:-998]
dev:3892024-01-08 00:26:55.619infoBedroom Door is [x:-6,y:-32,z:-1004]
dev:3892024-01-08 00:26:54.655infoBedroom Door is [x:60,y:-16,z:-1007]
dev:3892024-01-08 00:26:54.652infoBedroom Door is active
dev:3892024-01-08 00:16:58.099infoBedroom Door is inactive
dev:3892024-01-08 00:16:52.173infoBedroom Door is [x:-10,y:-20,z:-998]
dev:3892024-01-07 23:53:08.999infoBedroom Door temperature is 22.48°C
That looks almost exactly like one of my logs. That pattern of the XYZ reports in groups of three is similar to what I am seeing.
While you can't turn it off from the device page, if you put the magnet on the door (assuming you have the room) you should eliminate a lot of the XYZ reports as the sensor unit will be stationary. You may not want to do that for other reasons (I use this sensor to detect door movement, not necessarily fully closed).
@Eric.C.Miller as I wrote before, this is the log after pairing and it is pretty stable. And I don't have issues so far after pairing. I had the problem while pairing. (I could not pair for about a week)
I believe, finally , by chance it was paired and now it is stable. But for any reason if it is removed, I am worried it will not pair again easily.
This needs to be looked at. Not the current state.
as always , this was abandoned. No reply/no solution from support.
I tried contacting from all available channels... No response.
MY issue is solved by chance. The device is registered now and works. But I am always worried to remove and add this device to the hub. Also, I am worried to add any new zigbee devices.
Before C8 , I didn't have such worries.
