Hi, I’m still new to Zigbee and Home Assistant but I am trying to set up an automation with this socket where it is connected to a switch to turn a lamp on and off. All that works fine but when I turn off the lamp using the button on the side of the unit the light turns off but it doesn’t trigger an event at the Home Assistant. I need to capture the act of turning off the lamp and turn off the switch using an HA automation. I get a logbook entry for the main switch and the lamp remotely being switch on, but the button on the side of this unit doesn’t create a logbook entry.
Any ideas please?
First, start with the essentials: are you using ZHA, Zigbee2MQTT or a Sonoff Zigbee hub with a Sonoff/Ewelink integration ?
Thanks for your reply,
I’m using a HA Green with a ZBT-1 zigbee dongle. I can trigger the socket using HA but I can’t detect when it is manually selected on the side of the unit.
Pete
ZBT-1, so I’ll assume you use ZHA. Did you try a state trigger ?
Piggy backing on this if I may …
I recently bought two Sonoff S60ZBTPG Zigbee smart sockets with power monitoring and currently have one powering a 600W oil filled radiator.
I have the latest supervised HA on an X86 slim PC and using ZHA.
The socket was detected and integrated first time round and I have added all the fields to my dashboard and whilst it displays the current stats (Voltage, Current, Power etc), they don’t drop back to zero when the switch is turned off (Current / Power etc)?
However, when I turn the socket back on, those value drop back to zero then quickly go back to reading correctly?
Whilst I have a fairly large Zigbee network (PIRs, temp / humidity sensors, door sensors, smart sockets, lamps etc) and a good few WiFi devices (Commercial smart sockets, ESP devices etc), I’m not very good with the more technical fault finding type stuff. ;-(
I’ll try the second plug in case it’s just the first one but I’d also appreciate any pointers please.
Wondering if you ever managed to figure a solution to your SONOFF S60ZBTPG socket power monitoring issue. I’ve just installed one today and seem to be running into the same issue (albeit with a small Zigbee network, not as extensive as yours).
Hi and no, TBH I’ve not looked into it since but I think it might be better if you are using the ‘other’ Zigbee integration not (ZHA etc)?
The people who seem to report them ‘just working’ (and who would presumably have highlighted the issue we see if they were also) are using Zigbee2Mqtt?
I’m not sure if you can use them both simultaneously and with over 100 Zigbee devices … ;-(
Yeah from what I’ve seen, they do seem to be working with Z2MQTT.
I think you could theoretically use ZHA and Z2MQTT simultaneously, but only by running them separately. I.e. you could run a second device (say, another raspberry pi or separate container somewhere, with another zigbee dongle) which HA could integrate (alongside the existing ZHA using the existing zigbee dongle/radio/whatever). And would result in two separate Zigbee networks. Not something I fancy trying just to work around one specific issue with these particular devices.
I’ve run into this issue on GitHub which I think is the thing we’re experiencing (albeit the reported specifics seem a little less definitive than what we have here in this thread). It seems like potentially this is an issue in ZHA. I’m hoping that’s the case, as it means potentially we might have a solution in a future HA update.