I can't get the Sonof SNZB-02P to work with Hubitat. I tried with my Amazon Alexa no problems. I'm a little disappointed with Hubitat, I still think it's one of the best smart home systems. But the handling of the device is not good. I think HUBITAT should put a little more work into it. A good system should be better than Amazon and HomeAssistant.
What driver have you tried?
Thank you for your feedback, do you mind sharing the hub model that you have tried to pair the device?
Need to know the basics first, like hub model, platform version, and what exactly is not working? Does device pair but then not work or can you not get it to pair at all?
C7 and Sonoff driver, generic, and GitHub driver.
It's working now. After several attempts using the Sonoff driver, no battery status.
While I can live without it, I'm frustrated by the overall difficulty of connecting different devices. This is my third smart home using Hubitat, and while I appreciate the system, I wish there was more focus on improving driver compatibility. Especially Tuya Zigbee devices should be prioritized
Well, it doesn't work. No update of the temperature. Who to kick? Works well with Alexa, but I don't want to depend on her. I use Alexa for voice control.
Switch the driver to "Sonoff Zigbee Temperature/Humidity Sensor"
First try running Configure if it has that option.
If that does not help, sometimes on Zigbee devices you need to reset and re-pair them to get them to fully configure on the correct driver. So I would try to reset and pair it again, it will attach to the same "device" in HE and configure using the driver you selected.
If you still have problems with the regular temperature and battery reports of SNZB-02P, you can try also this driver.
This is a very good device, fully configurable as per the ZCL specifications.
Yes, this driver seems to work. I'll try it for a while.
I also have another obscure temperature sensor with a display and clock. I'm going to try this driver with that as well.
Did you write it?
Thank you very much.
//Gustav
By the way, I still think [they/HE] should improve their drivers and focus more on making several devices work.
A lot of times if you're willing to send in a device that has no driver they will try to write one. That said, they cannot do everything and that's the beauty of the community and people like @kkossev (thanx dude for all your work). Hubitat probably adds close to 100 native drivers per year and that's for an incredibly small team of people selling a 100-200.00 device while still doing platform updates and features. Another part of the equation are manufacturer's like Sonoff and others that don't always adhere to the zigbee/z-wave standards. Aqara is the worst. Things are better with zigbee 3.0 but older 1.2 are the worst.
Thanks for the response. I am fully aware that it is not simple to maintain all device drivers. For example, you mentioned Aqara, which you say is terrible—I agree with that. I also think HE is a great system. I would like you to put some energy into Tuya. When looking for various smart home devices, Tuya often comes up.
//G
Most TUYA zigbee devices are supported by @kkossev. I doubt the Tuya WIFI devices will ever be officially supported because they are cloud based.
Tuya is complicated as there are a lot of vendors shipping "Tuya" devices that can have very different FW/HW implementations, supported features, etc.
As I understand it from @kkossev, Tuya is more of an umbrella branding used by many vendors, than a single company/consistent set of devices like Centralite. Look at one of @kkossev's driver topics (the one he linked you to or this one and you see all the HW/FW iterations with quality levels that can range from excellent to crap.
Frankly, I have a different perspective than you. I prefer HE spend more time on broader/bigger platform feature improvements rather than spreading their small team's efforts too thin trying to support a gazillion devices. Especially when, as Rick notes, we have many community drivers that close the gaps very nicely, particluarly in the case of Tuya w/@kkossev's really excellent work. Different strokes for different folks...
The wording of the thread title’s a bit harsh.
We should all strive to do better in all our pursuits, but to suggest the devs “start working” comes off as pretty dismissive of all the work they’ve already done with respect to device support (and everything else this platform needs).
And @danabw makea a really good point re: Tuya.
While many smart home enthusiasts like to buy devices labeled Tuya, the development work required to add and keep those devices on the official compatibility list would be substantial.
Are hardwired Tuya devices even certified by independent safety testing labs like UL (or CSA, ETL etc.)?
Hubitat is not a charity; I have paid for my Hub. I speak highly of Hubitat and often recommend it to others when they ask about smart home solutions. If you are an ambassador for Hubitat, maybe you should think about how you express yourself. Although my previous statement may have been a bit harsh, I would never speak to a client in such a manner. I always strive to be polite and express my gratitude to those who help me.
I hope that my tone was respectful, I certainly intended for it to be. But I don’t work for Hubitat and you’re not my client. So you’re free to express your opinion and so am I .
Then I think we should raise the white flag and continue with our smart home solutions. It's a lot of fun, but also very frustrating at times. Good evening to you as well. It's evening here in Sweden.
Agreed. I do hope Hubitat can meet some users’ demands for compatibility with Tuya or other specific brand devices in the future. But there are always other competing needs to consider .
As I recall there was some discussion a while back about a volunteer group to help with the UI. That seems that is the #1 gripe they get in all the reviews. I know they came out with the Visual Rule Builder ("VRB") but it is extremely basic. With how great the community is, I'm sure there would be plenty of volunteers.