This is not good :
May be due to an unstable Zigbee network ... The device disconnects and then re-joins the HE zigbee network.
Leave the debug logs on for 24 hours, then search for the 'announcement' keyword on the device logs page - how many times do you see this message?
i dont use repeaters. the ikeas lately became unreachable
Also this problem may be related to the same issue..
Don't you have any mains-powered Zigbee devices? Typically Zigbee plugs/outlets .. ?
Parent child parameters
EzspGetParentChildParametersResponse [childCount=3, parentEui64=0000000000000000, parentNodeId=65535]
Child Data
No information for Child 0
child:[Mijia Button, 6CA9, type:EMBER_SLEEPY_END_DEVICE]
No information for Child 2
Neighbor Table Entry
[Bathroom strip, 096F], LQI:254, age:4, inCost:1, outCost:1
[Desk lamp, 19A3], LQI:253, age:3, inCost:3, outCost:1
[Under bed light, 6E87], LQI:255, age:4, inCost:1, outCost:1
[TV Backlight, 75FD], LQI:253, age:3, inCost:3, outCost:1
[bed light, CE89], LQI:254, age:4, inCost:1, outCost:1
Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [TV Backlight, 75FD] via [TV Backlight, 75FD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Stairs Light, 981B] via [Under bed light, 6E87]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garden Light Strip, 5247] via [Desk lamp, 19A3]
status:Active, age:64, routeRecordState:0, concentratorType:None, [LUMI Bedroom, A7B4] via [Desk lamp, 19A3]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Hallway light, EE7A] via [bed light, CE89]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bathroom , AAA5] via [Bathroom strip, 096F]
status:Active, age:64, routeRecordState:0, concentratorType:None, [LUMI illuminance 2, 88D0] via [TV Backlight, 75FD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [LUMI illuminance, 4D30] via [bed light, CE89]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Mijia Humidity, 655B] via [bed light, CE89]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Bedroom motion, DF08] via [bed light, CE89]
status:Unused
all the are working without a hitch
smartthings and swann outlets and gledopto usb lightstrips
You have Zigbee bulbs acting as repeaters.
Are these powered on all the time?
What model/make are they (the devices in the 'Neighbor Table Entry' section) ?
Some Zigbee bulbs are known to be very bad repeaters, causing problems for the rest of the Zigbee devices.
EDIT just read your second post - so these are not lights, but outlets ?
bathroom strip - gledopto usb
desk lamp - smarttings outlet
underbed light - tuya usb strip
tv backlight - tuya usb strip
bedlight - swann outlet
and there is one sengled classic bulb , but as far as i know they dont work as repeater
Rest of my lights are on hue hub witch cocohue integration
i removed the ikea usb repeaters the fell off as well . they are not in.
This issue is definitely related to your Zigbee mesh health, so I propose to continue the troubleshooting here : Ikea repeaters not working any more
version 2.6.0 was pushed for update via HPM. It adds the new 'healthStatus' attribute, which can be used to determine whether the device is online or offline to HE hub.
Updated the driver from the developer branch. Noticed i had done that for 2.5.1 already but the driver was never adopted by the scene controller, its still on 2.5.0
Same now for 2.60, is there a way to force the device to start using the new driver?
Kkossev wrote
Important: Due to the Tuya specific initialization that these devices require, these scene switches must be obligatory re-paired to HE hub in order to work properly.
So i need to re-pair it?
Check in the Drivers Code web page if you don’t have multiple instances of the same driver. So you are updating one instance via HPM , but your actual devices are using other instance of the same driver, same driver name. This happened once to me and was a pain to find and fix.
I removed the developer code and double checked the Tuya Scene Controller was installed through HPM. Ugh this thing is a PITA to get to work…
Edit:
Seems im slowly making progress
Is this a 4 button scene switch, or a 4 button remote?
Yes, you need to pair it with this driver being automatically selected. Otherwise these will not work, they are one of the most weird Tuya devices.
Whats in a name, is the MoesGo 4 button device
Ok, delete it from HE, and pair it again as a new device. Is the TS004F driver selected automatically?
While pairing as a new device, there will appear a link ‘more info’. Please copy everything from this pop up window before you continue with setting up the device name.
@kkossev, Thanks for adding the new "healthStatus" attribute, all working great 
Are you planning to add to all your drivers, including motion sensors?
Kudos to @kkossev. He made this work in a heartbeat! 
For those running into issues with combinations of drivers installed in the custom section and through HPM a few things i learned;
First, let me say THANK YOU for writing this Driver. The Tuya devices are very afforable, and I'm really looking forward to seeing how well they do!
I got the XUELILI version of the 4 button switch. I added the driver from the Hubitat Package manager, and it paired right out of the gate. It seems to have identified as a TS0044:
Where it gets interesting is that it is reporting as a 3 button switch, but, as you can see from the current state, the driver does recognize button 4:
Is there some way to edit the "numberOfButtons" variable to change it to "4"? It looks like I can use this in Rule Machine, and Basic rules with no problem, but the Button Controller app won't let me set up actions for button 4 because it thinks it only has 3 buttons...
Hi @dvdptr1 ,
Please update to the latest version 2.6.1 (you can use the Import button within HE Drivers Code editor). Then click on the Configure button, and let e know if the numberOfButtons changes to 4
I have added some extra logging in this version.
And it may be a good idea to add in a future version a Preference for overwriting the automatic detection logic for the number of buttons. This will be useful, especially for new models, which fingerprints are not included in the driver.
Download the Hubitat app
