@jim1 I have Energy on the right and I have those settings you mentioned in Preferences. There are 6 of them.
Do you have a light or something plugged into it so it draws power?
Does it draw more than 2.6 watts? Won't read less than that.
I changed "Power Change Report Value" to 1. But wall transformer reads Input at 120VAC at .2 Amps and output as 5VDC at 1 Amp.
That's 24 watts so it should be showing a value for power and current. Again, though, if you are running old firmware on the plug then it definitely won't report power, etc.
Wouldn't happen to have a Almond Securifi+ laying around the house? Or maybe a friend who does?
No I unfortunately don't have one. I guess I will have to use it as a on/off device which will be OK for the cameras. Thanks for your help. Let me know if a new way comes along to get it to work.
Does you driver do anything to the repeater part of this outlet? Better, no change?
I hear they are excellent repeaters and my driver shouldn't do anything to change that.
Thanks for trying it.
Thanks, @jim1 !
I used your code with only minor modifications, mostly cosmetic.
My Almond 2015 reported values that were different than the driver, but the code seemed correct from my reading of the Zigbee Electrical Measurement Cluster spec.
It turns out the driver is correct and the Almond is wrong, because measurements with a Kill-A-Watt matched the driver.
Sweet!
Thanks for the feedback. If you like, you can do a pull request and I can include your changes.
Jim, I just flashed my Peanut (damn that sounds wrong). It seems to report power much better than the inbuilt Generic Zigbee Switch driver.
I think the report rate on the current is probably defaulted to a bit long, but it reported a reasonable 10 Amps when I plugged the Vacuum into it.
Seems to work really well!
S.
1 Like
@jim1 I'm seeing a lot of warnings that appear to be unparsed messages:
dev:7052019-07-31 08:23:26.815 pm warnDID NOT PARSE MESSAGE for description : catchall: 0104 0B04 01 01 0040 00 0596 00 00 0000 07 01 8D000805
dev:7052019-07-31 08:23:24.727 pm warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0596 00 00 0000 00 00 D000
dev:7052019-07-31 08:23:20.766 pm warnDID NOT PARSE MESSAGE for description : catchall: 0104 0B04 01 01 0040 00 0596 00 00 0000 07 01 8D000505
dev:7052019-07-31 08:23:18.721 pm warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0596 00 00 0000 00 00 CD00
dev:7052019-07-31 08:23:14.767 pm warnDID NOT PARSE MESSAGE for description : catchall: 0104 0B04 01 01 0040 00 0596 00 00 0000 07 01 00
dev:7052019-07-31 08:23:12.717 pm warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0596 00 00 0000 00 00 CA00
dev:7052019-07-31 08:23:10.760 pm warnDID NOT PARSE MESSAGE for description : catchall: 0104 0006 01 01 0040 00 0596 00 00 0000 07 01 00
dev:7052019-07-31 08:23:08.709 pm warnDID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0596 00 00 0000 00 00 C800
dev:7052019-07-31 08:23:02.724 pm warnDID NOT PARSE MESSAGE for description : catchall: 0104 0003 01 01 0040 00 0596 00 00 0000 04 01 00
Doesn't appear to be a functionality issue...but it is messy! lol
1 Like
@jim1 - this works awesome. Thank you for porting over the driver. I noticed one of my space heaters reporting 300 watts using the generic zigbee outlet driver and knew that wasn't right. I updated to use your driver and now it reports right around 1000 as expected. Thanks for taking the time to share with the community!
I believe I've identified a weakness or bug in this driver. First, let me describe the problem that led me here.
First, thank you for the driver! Using HE I attempted to group two Peanut outlets. In the group, it would always show as 'Group-Dimmer 2.1'. I separated the two units and was going to group them in Alexa as a workaround. However, both units showed when discovered as 'Bulbs'.
In the driver, on line 44 is 'capability "Light"
I commented this line, and re-discovered and the device showed in Alexa as 'switch'.
This is important to me as the automation of Alexa has a generic 'Goodnight' that turns off all Lights. the Peanut was connected to the heated blanket and obviously not what I desired. After making this customization to the driver, the problem was resolved. I am now going back into HE to determine if the group as a Dimmer has been resolved as well. PS. the reporting of the power meter is spot on with an ammeter I was checking with.
1 Like
Many reports on this forum of these plugs wreaking havoc on the zigbee mesh, by rapidly changing routes, almost nonstop. I've pulled all 4 of mine off the hub
Search "great peanut panic"
3 Likes
Also randomly reporting ridiculous power spikes. Also, on two of mine the ground plug fell off and ended up stuck in the outlet. I’ve never had that happen with any device ever.
1 Like
Whoa! That's horrible. Did you get the grounding pin out or replace the outlet?
I keep forgetting about it, but I have a box of outlets and will probably just replace it the next time I have to shut off the power to that circuit. It is flush with the outlet and didn’t look like it would come willingly. Of course these were outlets I replaced when we moved here a few years ago.
Easy Fix! 
5 Likes
I am getting these messages in the log for my Hub. Washing Machine Plug is my Peanut plug. Is this normal behavior?
sys:12021-02-04 07:32:30.937 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.924 pm Unable to execute hubAction:he wattr 0x61AA 0x01 0x0003 0x0000 0x21 {0000} {} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.924 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.927 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 05 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.926 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 04 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.928 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.928 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.923 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 03 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.922 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.918 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 02 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.911 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.908 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 01 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.907 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.905 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.905 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 00 06} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.900 pm Unable to execute hubAction:he cr 0x61AA 0x01 2820 1288 41 60 7200 {0100} {} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.898 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.892 pm Unable to execute hubAction:zdo bind 0x61AA 0x01 0x01 0x0B04 {000D6F0004F74E78} {} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.890 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.885 pm Unable to execute hubAction:delay 2000 sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.887 pm Unable to execute hubAction:he cr 0x61AA 0x01 2820 1285 41 60 7200 {3000} {} sent from Washing Machine Plug, invalid or unspecified protocol.
sys:12021-02-04 07:32:30.887 pm Unable to execute hubAction:he raw 0x61AA 1 0x01 0x0B04 {10 00 00 08 05} sent from Washing Machine Plug, invalid or unspecified protocol.
