So I saw a post a while back saying that the Peanut zigbee switches needed an Almond hub to push a software update that allowed power monitoring, that the shipped software did not support it. The poster said he just acquired an Almond hub and would report back on results. I couldn’t find the results posted so I went hunting on the interwebs…
(UPDATE: I do not believe the steps below work. You have to have an actual Almond router to upgrade the peanut firmware, but if you get and Almond router you can flash the firmware on the peanuts to report power usage Please see additional comments in this series.)
The device both, a. does not show amps/volts/watts and b. says it is on the latest firmware
Tried with and without having the router connected to an almond account, and with and without the router having a web connection.
I will try on a few more Peanuts. However, based on initial testing either: a. Securifi changed something so you can no longer flash devices or b. These devices are on the latest firmware, and just do not report power information.
The first one tried reported zero power readings to the Securifi router as well as HomeAssistant.
I will try some more things:
Different Peanut plugs
Different firmware versions on HomeScreen router
I ordered a used Almond + off Ebay. Just to see if firmware update is disabled on the HomeScreen device.
Ok, so the HomeScreen with Almond 2015 firmware does not update firmware on the Peanuts. I tried older versions of the Almond firmware, but no dice. I bought a used Almond + off ebay, upgraded the software, and it flashes new firmware onto the peanut switches. I have confirmed that the new firmware does indeed measure current.
You do not have to have the router attached to an Almond account to upgrade the peanut firmware, but it does have to see the internet on the WAN port.
Very strange. Followed the articles noted and was able to flash 2 of my Peanuts using the Almond 2015 firmware on the Home Screen. Without ethernet connection, the Home Screen showed no updates for the Peanut and all the Power information was 0. Plugged the Home Screen to the top port (the WAN cloud icon) to my network, it changed to stating the Peanut had firmware update. Took about 5 minutes and got the Upgrade Success. Now I see Power wattage, current amps and Voltage with correct information. Not sure why you had no luck with the Home Screen, but wanted anyone else viewing this thread to know that it seems to be possible.
I have a stack of them here along with the flashed HomeScreen and an actual Almond display. I pulled them and replaced them with Aqara (because the other battery powered Aqara devices I had did not get along with the peanuts)… The peanut switches were great though and their touch screen panel was pretty nice too…
I had no luck with the flashed Homescreen router updating firmware on my switches, but cinghialino reports success. I had success with an actual Almond device. I don’t know of anything other than the Securifi software that will update the firmware in your peanut switches… So if anyone wants some Securifi hardware I’ve got ~6 almond switches a flashed Homescreen router (zigbee only) and an Almond 2015 that are collecting dust…
I caved in and got an Almond router for the sole purpose of updating the peanuts plugs. I guess I’ll return it when I’m done with it. Anyone needs an update?
I actually just paired mine to zigbee2mqtt and ran ota in there and it updated the firmware, after which I paired it directly to home assistant. After using the plug with smartthings for years, I finally have power info.
Follow the directions on the zigbee2mqtt site as the plug doesn’t publish it’s model number. Zigbee2mqtt displays volts, watts, and amps, while HA only displays watts.
…but I’m running into a wall at step 2. I suspect it’s something wrong with the equivalent of the “WSDCGQ01LM.js” file in the example.
Would you mind sharing your equivalent of that file? I’d immensely appreciate your help, because I’ve been banging my head against this for a few hours!
UPDATE: Problem solved! I was looking at the wrong directions. These are the correct directions: