Contact Sensor not working the same from C3 to C8

🎬 Get Started Using C-8 Pro
1

I have had a C3 unit for a very long time.
I decided to upgrade to C8 Pro a few weeks back.
I had a few botched attempts to migrate from backup, but got it to restore eventually.
Everything I am managing with Hubitat is Zigbee.
I'd let things slide and a lot of devices batteries went flat, and I didn't need the sensors much.
So, as I'm replacing batteries, the devices are not functioning. I re-added the first device (a genric zigbee contact sensor), and it registered, but does not report open/close status.
After trying about 10 times, it just never worked. I also basically had a hard time getting it to register.
I decided to switch back to the C3 hub, and re-register the same sensor on the old hub - it discovered it immediately, and the sensor worked immediately.
Both are on the same version 2.3.9.201

This makes me think that there is something different with the zigbee radio?

I thought maybe I should just rebuild the C8 Pro from scratch rather than bring across the devices (I feel I need to anyway, as much as I dont want to be doing this for everything).

I've also just installed HomeAssistant on my synology NAS, and it's taking care of all my wifi devices and web integrations, but I wanted to keep using the C8Pro for all my zigbee, but now I'm thinking maybe I just try to get my ConBeeII stick working with it if this is the amount of work I'm going to be up for with all my devices.

Old Zigbee radio was on Channel 14, new one was on Channel 20. Could this make a difference?

Should I nuke the C8Pro and start from scratch and hope for the best? Are there known differences between the zigbee radios between C3 and C8Pro that I should be aware of?

2

There were notable Zigbee changes between the C-8/C-8 Pro and previous versions, including a Zigbee 3.0 chip and updated stack on the hub.

What specific device (not just driver) are you using?

Yes, some users have had problems with channel 20 on the C-8 Pro, which you likely also received a notification about (top right corner) on your hub to consider switching if you're having problems. Channels 15 and 25 are often other good choices, though avoiding ones that overlap with 2.4 GHz Wi-Fi in use around you is really the best idea -- these are just widely compatible Zigbee channels that often do avoid this given the most common Wi-Fi channels.

It's also an easy thing to try, especially if you have no other devices (but even if you do, they should catch up, or in the wost case, just re-pair without removing).

2 Likes
3

I decided to do a full reset and see without any legacy stuff on the hub.
I started with Channel 25 (which the hub recommended).
Same deal - found the device but did not register any attributes.
No comms from when I open/close the sensor.

I changed the radio to Channel 14 and rebooted the hub.
Re-registered the device (it found it as an existing device), and same thing - just does not register any attributes for it.

I'm going to try my ConBee II stick in the NAS box and see if it acts any differently.

At this stage I think I'm going to have to revert back to my C3 Hub!

4

How long are you letting the devices ‘sit’ before you do something else to them? (Unpair, re-pair, reset, etc…)

Just curious, really… I had (and still am) having Zigbee issues with a C8P after a migration. I have a subset of devices that re-pair with no apparent issues at all, except they won’t communicate after. Except… they start talking a few hours later. Then go silent for a few hours, then start talking. Rinse and repeat….

I haven’t had a chance to dig in deeper to try and find patterns, much less solutions. Hopefully after the holidays.

5

Still curious about this:

2 Likes
6

Device is a contact sensor
It reports as Feibit - FB56-DOS06HM1.3

Some info about this here:

This is what it looks like

Bought them years ago from this company:
https://www.ebay.com.au/str/googlehome

7

Well, I don't wait too long - I'm resetting the device.

If I have to wait unknown amount of hours/days between each device, it's going to take months to get it all working.

Interstinging, if I plug the old C3 hub in and reset the device, it works immediately.

No luck getting the device to be discovered by the ConBeeII stick though, but honestly, it's plugged in to a NAS box, in a virtual machine inside of HomeAssistant with add-on's and plugin integrations. It's a miracle anythhing functions in there!

It's also in a rack, which is not ideal as it's a bit of a faraday cage in there. But the first device I was trying to setup was right next to it, so who knows.

8

What zigbee channel is the c3 using ? Currently ?
Can you set the c8 to that channel same as c3 .
Then reboot c8 .. then add the device ?
You Also may need to use a different driver ( Default zigbee contact sensor driver. )
do not forget to press the configure button when changing drivers.
Give this a try .. let us know,.

image

9

Gave that a go - didn't seem to make any difference.

Not sure where to from here. Honestly might have to try to go back to the C3 hub!

1 Like
10

Below are the logs from when I try to add the device.
It comes across as "device"
I then change the device type to "Generic Zigbee Contact" or "Generic Zigbee Contact (no temp)" and it just doesn't register anything. Again, on the C3 hub, this worked.

Note the first few lines of the log below. the first line shows the status as CLOSED, the second line shows the status as OPEN.

So the device is reporting properly.
We just don't have the driver right.

Can anyone point me in the right direction? I have 4 of these sensors, but if the answer is they are all now toast, I'll just have to go buy some alternative brands and cross my fingers I guess.

dev:92025-01-04 09:29:20.884 AMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:18.058 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:15.753 AMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:13.141 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:09.548 AMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:08.682 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:08.376 AMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:07.524 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:29:06.815 AMinfoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:28:51.547 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:28:36.053 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:28:28.379 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:28:24.648 AMinfoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0001
dev:92025-01-04 09:27:54.141 AMdebuggetting info for unknown Zigbee device...
dev:92025-01-04 09:27:44.119 AMdebuggetting device info in 10 seconds...
dev:92025-01-04 09:22:58.072 AMwarnconfigure...
dev:92025-01-04 09:22:02.115 AMwarnconfigure...
dev:92025-01-04 09:21:30.859 AMwarnconfigure...
dev:92025-01-04 09:16:23.278 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0502,0500", outClusters:"0000", model:"FB56-DOS06HM1.1", manufacturer:"Feibit,co.ltd ", controllerType: "ZGB"
dev:92025-01-04 09:16:23.150 AMtraceZCL version:01
dev:92025-01-04 09:16:23.147 AMtraceSoftware Build Id:unknown
dev:92025-01-04 09:16:23.146 AMtraceModel:FB56-DOS06HM1.1
dev:92025-01-04 09:16:23.145 AMtraceManufacturer:Feibit,co.ltd
dev:92025-01-04 09:16:22.668 AMdebuggetting info for unknown Zigbee device...
dev:92025-01-04 09:16:13.813 AMinfoZigbee description:enroll request endpoint 0x01 : data 0x0015
dev:92025-01-04 09:16:13.060 AMinfoZigbee parsed:[raw:catchall: 0000 0006 00 00 0040 00 22EC 00 00 0000 00 00 02FDFF0401000200050205, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:22EC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[02, FD, FF, 04, 01, 00, 02, 00, 05, 02, 05]]
dev:92025-01-04 09:16:12.625 AMdebuggetting device info in 10 seconds...