Ok, i am pulling my hair out with the third reality gen 1 plugs (gen 2's work fine). I am using a c-7 hub with latest firmware. I am using the third reality gen2 driver with power reporting turned off.
Here is a couple of logs
warn
Canon printer zigbee read METERING_CLUSTER attribute 0x0302 error: Unsupported Attribute
dev:4032025-02-09 09:15:25.416 PM
warn
Canon printer zigbee read ELECTRICAL_MEASUREMENT_CLUSTER attribute 0x0602 error: Unsupported Attribute
warn
1st family lamp zigbee read METERING_CLUSTER attribute 0x0000 error: Unsupported Attribute
So, i would love to follow someones insteuctions on how to fix these warnings.
Thanks in advance.
Sorry, i made a mistake. A couple of the warnings are on a third reality gen 2 plug.
Again, thanks for the help.
That’s a custom driver? Provide a link to it.
I think the built in generic Zigbee plug driver works for those too.
Make sure you update the firmware on them.
@jtp10181
Well, that made it worse. Lol
Now instead of warnings, i am getting errors.
dev:4712025-02-11 03:00:12.160 AM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: GenericZigbeeOutlet.ping() is applicable for argument types: () values:
Possible solutions: find(), print(java.lang.Object), print(java.lang.Object), find(groovy.lang.Closure), print(java.io.PrintWriter), run() (method ping)
dev:6412025-02-11 02:59:58.057 AM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: GenericZigbeeOutlet.ping() is applicable for argument types: () values:
Possible solutions: find(), print(java.lang.Object), print(java.lang.Object), find(groovy.lang.Closure), print(java.io.PrintWriter), run() (method ping
This was using the generic zigbee outlet driver. I am monitoring this device for power usage hence the third reality smart monitoring plug.
One more thing, this device is giving this set of 2 errors about every hour. Dont know if that matters, and i was able to reproduce this problem with two devices. Both were third reality gen 2 monitoring plugs. The driver is doing this With both plugs.
When i was using the driver for the third reality metering plug, no errors but warnings.
Those new errors are from the scheduled ping the other driver setup.
You can go to Logs > Scheduled jobs, and then find it and delete it from there.
Or you can switch the driver to "Device" and then use the command to delete all scheduled jobs, and then switch back.
I have 4 of theses plugs and I am using the system driver on 3 of them.
The built in driver supports that plug: Generic Zigbee Outlet
Make sure you click the Update Firmware button on each one and then watch the logs for it to complete. TR has made a bunch of improvements since that device was released.
The other driver I have used before the system one worked was this custom one: hubitat-public/ThirdReality at main · bradsjm/hubitat-public · GitHub
Which is in HPM under thirdreality / Third Reality Power Meter Plug
3 Likes
Ok, i set it back to device andccleared everything and then switched back to generic zigbee outlet. I will let you know thecresults later today.
As for updating firmware, this has me lost. Everytime i see the button on any device, i click on it and then on ok. It says it sent the command but nothing ever shows up in the logs about firmware.
It will show up in logs but maybe not right away, and not tied to that device. It shows as a sys log. You need to have the main logs window open, unfiltered.
Show us your device data from the info tab, should look like this.
I think the 3058 I have on this one is current.
Device Data
| Application |
41 |
| Firmware MT |
1233-D3A6-10013058 |
| Manufacturer |
Third Reality, Inc |
| Model |
3RSP02028BZ |
| Power Cluster |
0B04 |
| Software Build |
v1.00.88 |
1 Like
Do you mean the top left 3 lines, then click logs. I will check. I will give it an hour or so and then we will see. I tried clicking on 3 different tr plugs for updates, lets see if it does it.
Yes the logs page from the left side bar. If you click the logs tab from the device it will be filtered to the device only and not show the sys firmware messages.
If you already have clicked it on those plugs they probably already updated, so if you check the device info and they are on 3058 already, you are fine.
Well, thanks anyway.
After getting banned from the forum for withdrawing my questions because of the wording people were not understanding what was happening.
The only person that reached out while i was banned, was Krassimir and he understood the problems i was having was not my doing at all and he helped me work through some of it before the hub crashed with blue light only. Also no help on forum for that, go figure. The moral of that one was, it was not my fault, it was a dying hub that refused to work correctly now turned light paperweight.
So, since i only get bad responses from my post for help, i will just not ask anymore. I do read to see if anyone had the problem in the past, but i will not message them for fear of hateful responses. I have a thick skin, but I can only take so much negatively.
1 Like
My best recollection of what happened is that you may have misinterpreted responses from others, some of which included negative (but polite and ostensibly constructive) feedback, as personal attacks on you. Since you deleted so many posts (or edited them to read as gibberish, which got them subsequently deleted for you), it’s hard to refresh one’s memory of what happened.
5 Likes
It is ok, i am not mad at anyone, i am just not putting myself out there anymore. It is just not worth the hassle. It really does not matter anymore since the hub self destructed and now only gives a blue light. What little info i could find in the forum did not work or help in any way. Thanks anyway and Mark, i did not tag you, someone did. Sorry you got dragged into this again. Again, sorry for the inconvenience.
Oh, i almost forgot, when you ban people from this forum, it also bans you from any support from hubitat because even thier support goes through some ofvthe code used in this forum, so the result is the person being put out to dry without any recourse, because even the contact us uses the same code, so in my opinion that you dont care about anyway is that when your opinion doesnt match some elses, you get completly hung out to dry even though you paid for a hub that wont work. I think i got the gist of it
1 Like
You also can't unlike a post....
Paul, when you quote a post by another user, the system notifies them, the same way it would if they were tagged with an @ symbol.
That’s what occurred in this thread that you created this morning.
As Simon already put it, rather eloquently:
Best of luck to you.
3 Likes
Hey Mark, you are right, Simon did state eloquently. Thanks Simon but now my hubitat does not work at all so i wont have to ask for help with it anymore. Mark, you do you the only way you know how.
