DEV Community

Joe Block
Joe Block

Posted on • Originally published at unixorn.github.io on

Fix Securifi Peanut issue with zigbee2mqtt

Securifi Peanut plugs have issues with zigbee2mqtt.

I have several Securifi Peanut Zigbee switches. Overall, they’re nice little smart plugs and make good Zigbee routers to strengthen your Zigbee mesh, but they have one annoying issue - zigbee2mqtt doesn’t recognize them perfectly, though there’s a simple fix that I’m going to document here.

Adding Peanut Smart Plugs to zigbee2mqtt

The Peanut Smart Plug does not provide a modelId in its database entry, so zigbee2mqtt can't identify it to know how to handle it. Fortunately, it's an easy fix, though you'll have to do it every time you add a new Peanut plug.

  1. Pair your new Peanut(s) to your zigbee2mqtt instance
  2. Once you've added all the peanut plugs, stop zigbee2mqtt. We're going to need to do some surgery on its database.db file and that can't be done with the service running.
  3. Backup your database.db file. If you mess up the edit, you'll want to be able to revert and try again easily.
  4. Edit your database.db file. Add a "modelId":"PP-WHT-US" to each of your Peanut entries. For example, change ""manufId":4098, to "manufId":4098,"modelId":"PP-WHT-US",
  5. Once you've finished editing database.db, restart the zigbee2mqtt service.

You should now see proper entries with capabilities in zigbee2mqtt and be able to turn the switches on and off, both from zigbee2mqtt and from Home Assistant. Now would be a good time to go to zigbee2mqtt's OTA tab and check if your Peanut plug(s) have any firmware updates.

Top comments (0)