I thought I would save a few dollars and ordered some smart plugs that >claimed< to work with Hubitat. Fortunately, they were ordered from Amazon ( Eightree Zigbee Smart Plug). In the chart on the product page, they had Hubitat. I think they just copied the chart from Sonoff since it looks pretty much the same. However, when attempting to pair them, they would pair as "device" and even if the driver were switched to the appropriate "generic Zigbee outlet," they would not work. They ended up going back to Amazon pretty quickly. I then remembered to check the compatibility list and sure enough, they were not on the list.
I then ordered THIRDREALITY ZigBee Smart Plug 4 Pack after finding that they are on the compatibility list. What a difference! They paired quickly and two of the four are now in service with the other two to follow shortly.
These are replacing Iris Gen 1 smart plugs which just don't want to pair anymore with the latest platform on a C7 hub. I had them working for years on a C5 hub, but wanted to upgrade the hub. I know, "If it ain't broke, don't fix it!" but I went ahead and fixed it anyway. Thus, I found that Iris V1 devices are well past their prime and really need to be retired.
Now, when I remove the last of the Iris V1 devices, it will eliminate why I set up a separate hub in the first place. The idea was to isolate the Iris V1 from the more modern Zigbee and Z-Wave devices. Once that is done, I no longer will need to run the second hub.
Which leads to a question. Is there any way to reprogram/repurpose a C5 or C7 hub for other use? It would be nice if there were a way to do so.
Be carefull with the energy reporting settings with the third reality. They sre known to be chatty and too many of them all constantly reporting can tie up the hub.
There must have been some firmware updates or something from Third Reality.. I have 4 of the non-energy monitoring plugs on HE and 4 on HA brought back into HE. All 8 of them only log entries when they are turned on and off. I have one that hasn't cycled in over a couple weeks. So long that the logs for it are empty.
I have 3 of the energy monitoring plugs and as long as you have a stable power flow they don't chat much. They do however send info every time the power level changed but honestly they have had no impact on C8 Pro.
Nowhere on the Amazon site was it mentioned about using a Tuya driver. If it had been mentioned, I might have kept them. As it was, there was just a $2.00 difference between those and the ones that were on the list and worked without having to use a 3rd party driver that was not documented.
I'm not seeing the Third Reality as being "chatty." The Iris V2 smart plug has many more entries in the log than the Third Reality smart plug for the same time period.
CPU load/load percentage: 0.14/3.5%
I don't think I am at risk of overloading the C8 Pro hub.
When I tested the TR plugs in 2023 in zigbee2mqtt they produced 3 or 4 messages for every action and periodic reports (several per minute) as to their status.
IRC I might have read a post on the HE forum about TR updating their firmware to reduce the chattiness. I haven't tested them since.
This is no way reflects anything bad about TR, I just thought they were too chatty, so I tried the Sonoff S40 Lite at the same time and they were much quieter.
Yea i got reports every 20-30 secs for no reason. I switched to others switches. The non power reporting version didnt have that issue. As mentioned a fw update may have fixed it.
Lots of devices not on Hubitat's compatibility list work fine with Hubitat using either built in generic drivers or a community driver. In the case of the above it works with a community driver. I'd buy those without hesitation. Pop in @kkossev's driver and be happy.
The zigbee2mqtt may have influenced the results. I'm using straight Zigbee. Or, it may be that the firmware was updated. I have other Third Reality devices and have been pleased with them.
Okay. I did not scroll down to read all the reviews. Still, if it had mentioned in the product description that the Hubitat compatibility required the use of the community driver, I might have kept them. E.g. I read the headlines and didn't dig down to the 3rd column on the 5th page.
when devs have the devices in hand and can test themselves. Typically as long as a device uses standard zigbee or z-wave it will work fine with generic drivers built in for that class. Some stuff like Tuya is off enough that it requires someone like kkosev to really dig in and find the exposed command classes and write a driver. Hubitat devs don’t have time to waste with such products and leave it to the community and people step
up.
I've got four of the EIGHTREE power monitoring outlets. They work fine with the generic zigbee driver, except watt reading is off by a factor of ten. Shows 10 when it's 100 for example. I've modified my rules to take this into account but would be great if the generic driver has an option for multiple!
Here's the info on it, if the Habitat team @bobbyD would have any desire to add that feature!
