For what it’s worth, I was able to reproduce various issues with the Securifi Peanut plug on Hubitat.
Hubitat discovered the Peanut plug quickly, but didn’t associate a meaningful device driver to it. It was just left as the generic device after pairing it. (eg. it had no commands, no state, etc)
After changing the driver to Generic Zigbee Outlet, the commands for turning the device On / Off came available and whenever I pressed them, the device would turn on/off accordingly, but the state never showed up in Hubitat and no events showed up in the device event history in Hubitat.
That being said, I think this is somewhat the expected result. If I remember correctly, the
configure command of a device driver is automatically run when a device is first paired, but is not run when you manually change the device driver. So because the Peanut Plug wasn’t recognized with a meaningful driver, it never ran a
Thus, manually running the
configure command on the device effectively completed the final required step of the pairing process and got the device communicating its status back properly.