Sonoff zigbee switch

peterbrown77.pb · May 2, 2020, 4:00am

Oh OK. Sorry I should have read more above. Mine as a Nue switch changes state in the device page when I use a rule or use the deice page links to turn on or off...

Have you tried to delete the device and rediscover it or change it to a nue switch device type. I am sure its above but I'm being lazy truth be told

I know this doesn't help much , but at least some hope

njanda · May 2, 2020, 4:04am

Thx man.
Interesting. Mine does not respond at all when the Driver is set to Nue Switch, Configure saved etc..

gadgetshed · May 2, 2020, 7:07am

Just to clarify the situation I am seeing is that when I switch it manually using the physical button on the sonoff I see the state change instantly on the device page but when I click on the on or off links on the device page there is no change on the Sonoff itself or in it's state on the device page. It reports back to HE fine when I do a physical change but I just can't seem to switch in on or off from the HE device page.

Also when I click configure all I get in logs is

2020-05-02 08:11:26.250 infoBASICZBR3 is off [digital]

2020-05-02 08:11:26.214 debugdescMap: [raw:47E80100060800001000, dni:47E8, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

2020-05-02 08:08:41.160 debugrefresh...

2020-05-02 08:08:41.083 warnconfigure...

Nothing after that.

njanda · May 2, 2020, 7:15am

There’s something weird here for sure because whilst the “current state” doesn’t update on mine, I can use the On and Off buttons on the Drivers page to turn on and off my shed light.
FYI: I’ve also used the Ikea Tradfri Control Outlet driver as that provided routing info and this driver behaves in the same manner.

at9 · May 2, 2020, 7:18am

Mine updates fine either way.

What do the logs say if you switch the driver to device? It should check-in every 5 mintues with its state.

njanda · May 2, 2020, 7:41am

I get this ;

at9 · May 2, 2020, 7:49am

Very odd as I get the same.
Value 1 is on and 0 is off.

steve.maddigan · May 2, 2020, 9:45pm

I purchased two more of these and they do not seem to be behaving the same way as the first two. Different FW maybe?

The initialization does complete properly and therefore no driver is automatically selected.

Manually selected Generic Zigbee Outlet and hit configure.

Yes the switch reports current state back to HE but no control from HE to the switch.

at9 · May 3, 2020, 12:27am

I pieced this together which works for me so maybe try it?

github.com

at-9/hubitat/blob/master/Drivers/SONOFF-BASICZBR3

/**
 *  SONOFF BASICZBR3

 *  Device Driver for Hubitat Elevation hub
 *  Version 0.1
 *
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *  Basically just lifted from the SmartThingsPublic zigbee-switch.groovy removing code not relevant to Hubitat and adding a little
 *  https://github.com/SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zigbee-switch.src/zigbee-switch.groovy
 */
metadata {

This file has been truncated. show original

steve.maddigan · May 3, 2020, 12:59am

Wow. Thanks Adam for providing the driver.

I switched to it for my two already working devices and they still work. And one is used as a repeater from my Hudson Bay fan controller and I can still talk to that.

But it still doesn’t change the behaviour or my two newer devices.

dev:20862020-05-02 09:01:50.238 pmdebug[raw:catchall: 0000 8021 00 00 0040 00 EFC2 00 00 0000 00 00 6300, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:EFC2, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[63, 00]]

steve.maddigan · May 3, 2020, 1:07am

This is what I get with debug logs enabled controlling a working one.

dev:20862020-05-02 09:06:26.996 pmdebug[name:switch, value:off]

dev:20862020-05-02 09:06:26.984 pmdebugdescription is catchall: 0104 0006 01 01 0040 00 EFC2 00 00 0000 0B 01 0000

dev:20862020-05-02 09:06:26.958 pmdebug[name:switch, value:off]

dev:20862020-05-02 09:06:26.953 pmdebugdescription is read attr - raw: EFC20100060800001000, dni: EFC2, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

njanda · May 3, 2020, 1:11am

Cheers Adam,
Yep, on mine , the On and Off button on the Devices page controls my BasicZBR3 (as does the physical switch on the ZBR3) but the Current State or Variables, do not update to reflect the state of the ZBR3.

at9 · May 3, 2020, 1:36am

are those 2 logs from different devices ?

njanda · May 3, 2020, 1:38am

Hmmmm.. mine doesn't even report every On / Off action when done via the buttons on the Device page BUT the ZBR3 turns my shed light on and off each time, as expected.
Note: my ZBR3 is running through 2 x repeaters

steve.maddigan · May 3, 2020, 1:40am

Yes, the first one is from the new device that does not work.

The second one is from one of teh devices that was working properly before and still does with Adam's driver.

My gut feeling is my two new devices are just not working properly.

at9 · May 3, 2020, 1:42am

well they both have the same device network ID (EFC2) which is probably why the states aren't changing.

steve.maddigan · May 3, 2020, 2:25am

interesting. i'll look into this more tomorrow. EFC2 is definitely the device that IS working.

E9A2 is teh device with issues. maybe i C&P wrong from ,y phone, but not sure how i could have done that since i was only turning debug logging on one at a time.

But lets assume that i screwed up.

njanda · May 3, 2020, 2:29am

Nah, there's something weird going on for sure with these devices !
I've just paired my 2nd ZBR3 and it was detected only as Device, and provided this ..
dev:22132020-05-03 12:21:02.304 pm traceZCL version:01

dev:22132020-05-03 12:21:02.302 pm traceSoftware Build Id:unknown

dev:22132020-05-03 12:21:02.301 pm traceModel:BASICZBR3

dev:22132020-05-03 12:21:02.299 pm traceManufacturer:SONOFF

dev:22132020-05-03 12:21:01.948 pm debuggetting info for unknown Zigbee device...

dev:22132020-05-03 12:21:00.931 pm infoZigbee parsed:[raw:384D0100060800001000, dni:384D, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:22132020-05-03 12:21:00.268 pm infoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 384D 00 00 0000 00 00 004D38E288721E004B12008E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:384D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 4D, 38, E2, 88, 72, 1E, 00, 4B, 12, 00, 8E]]

dev:22132020-05-03 12:20:59.929 pm debugconfigure() called...

dev:22132020-05-03 12:20:52.864 pm infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0004,0005,0006", outClusters:"0000", model:"BASICZBR3", manufacturer:"SONOFF"

I've now changed it to Adams, Sonoff BasicZBR3 driver, hit config/save etc and the ZBR3 is completely uncontrollable from HE BUT when the physical button on the device is pressed it does update the Current State on the Devices page!

steve.maddigan · May 4, 2020, 12:06am

Yes. Identical to my situation.

Again my first two I bought are fine.
Purchased two more from the same amazon listing and they have issues.

markus · May 4, 2020, 12:56am

@steve.maddigan Have you tried re-pairing without deleting the device from HE? When bind and reporting commands don't take it could still be that. Re-pair and then run Configure. The radio on these is somewhat weak, so having them in a non-optimal location could also cause this.
I have three of them and they work really well together with the strong signal from Ikea repeaters.