That’s what is so odd. Running smartthings devices does not show any devices of this driver type, so I don’t think it was a delete issue.
I am not sure what would be causing blocking like that, especially after trying a hub reboot. Logs do show other zigbee device activity as normal - there’s just nothing for this driver, but in the past, I’ve been able to easily get logs even if just init.
It’s possible your driver is locked up or stuck in a reboot loop. I would modify your init file and comment out the guts of it. Reinstall that with a few log statements for sanity. If it is locked up, this should get it out. Then you can reintroduce your logic and debug the cause.
Already been down that path. Also tried another working test driver that really doesn’t do much of anything. I simply changed the driver name and package key in the config file. Same deal - installs fine, but never gets kicked off.
Hi everyone. Thank you for adding your comments on who else is experiencing this behavior. I already asked the team about this.
Are you using the iOS or Android ST app? @brbeaird, @TAustin, @Davec
Well, I didn’t scan any new zwave/zigbee devices just to test. Nor have I installed any LAN style drivers to test with.
But to test I did remove the vEdge Creator tile (driver already installed on both firmwares). Do a scan on either hub and it reappears as expected, and the green hub lights blink while scanning.
Yes, this is what the engineering team detected, I just asked to confirm it was your case as well.
Anyway, this is already reported, we’ll let you know the feedback.
Thank you for your reports!