Support for Schneider Wiser products?

kkossev · April 1, 2024, 8:41pm

The first tests were successful on my C-7. I will publish the driver this weekend.

The bad news is that I couldn’t pair it with my C-8 hub… what model is your hub?

magnus.s · April 2, 2024, 10:58am

I use a C-7

SamuelS · April 3, 2024, 8:17am

For the update, I have four units working with C-8, thee can be connected after several attempts but they seem to drop offline or something, because they don't work at all.

Could you @kkossev code online status to driver to see how they stay online?

kkossev · April 3, 2024, 12:35pm

I will try a few ideas how to better determine the online/offline status of the switch.

It has a healthStatus attribute even now, you can use it with the Device Activity Check app, however it is updated relatively slow - 12 or 13 hours after the last battery report.

SamuelS · April 3, 2024, 3:24pm

I tried it now with Ikea driver and it works when pressing virtual buttons in Hubitat devices interface. The device itself still doesn't work. With Ikea driver it shows online status as well.

SamuelS · April 3, 2024, 3:34pm

Got back to your beta driver. It shows number of buttons 7. With working units it shows 4 as it should. Now it has the online status showing.

Non working unit:

Current States

Status : clear
checkInterval : 3600
healthStatus : online
numberOfButtons : 7
powerSource : unknown
pushed : 2
released : 3

State Variables

lastTx : 1712157560082
lastCx : 3.9.0
lastRx : 0
endpointId: 15
firmwareMT: 105E-0016-020901FF

Working unit:

Current States

Status : clear
battery : 100
healthStatus : online
held : 2
numberOfButtons : 4
pushed : 2
released : 2

State Variables

reportingEnabled : true
lastTx : {}
lastRx : {batteryTime=1712144351277}
driverVersion : 3.0.4 2024/04/01 11:13 PM (FLS/SYSTEM-M/4 Schneider Electric) (C-8 2.3.8.134)
stats : {battCtr=7, rxCtr=62}
health : {checkCtr3=1}
zigbeeGroups : {}
states : {lastButtonNumber=2}
endpointId: 15
application: 02
firmwareMT: 105E-0016-020901FF
manufacturer: Schneider Electric
model: FLS/SYSTEM-M/4
softwareBuild: 020901FF

kkossev · April 3, 2024, 3:48pm

The non-working unit has some artefacts remaining from Marcus’s driver…

It is not easy to clean up these - you must take the risk to completely delete the device from your C-8 hub (use the “REMOVE DEVICE “ red button) and then pair it again as a new one. The test driver should be automatically selected during the pairing.

Test with only one of the non-working devices.

@magnus.s I will publish the link to the test driver a few hours later tonight.

kkossev · April 3, 2024, 7:16pm

@SamuelS @magnus.s this is the latest code :

https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Zigbee%20Button%20Dimmer/Zigbee_Button_Dimmer_lib_included.groovy

It has just some minor bug fixes and improvement compared to the first test version.

I tried again to pair the Schneider switch to my main C-8 hub without a success.
I am awaiting a new C-8 Pro in the next few days, and I am pretty sure that the switch will pair to the new C-8 on the first try,,,, until the C-8 hub is new. After some days or weeks when I pair a bunch of other Zigbee devices, the C-8 will stop pairing to the Schneider switch again - I am almost sure about this. This is my experience with the C-8 and other Zigbee 3,0 devices in the past year.

SamuelS · April 4, 2024, 5:43am

I updated the driver. Removed one of the non working devices. I tried to add it back with old and new driver installed to hubitat, but it gets stuck in initializing phase, even if I tried to pair with exchange keys in clear.

kkossev · April 4, 2024, 5:46am

Don't remove the remaining switches, they may end up not being able to pair again.

Please post the device details section for one of the non-working switches - I can add the modified model ID to the driver.

The working switches have FLS/SYSTEM-M/4 model - what is the model of the non-working ones?

kkossev · April 4, 2024, 6:15am

OK, I run the Zigbee - Generic switch driver and this is the result :

I don't know why Marcus was doing this in his drivers (stripping the special characters from the model name), there may have been a good reason in the past. Now, there is no such need.

Please wait, do not remove and repair the Scheider switches again - later today I will include the stripped model name into the driver code, so that it is recognized automatically by this driver.

SamuelS · April 4, 2024, 6:22am

First is FLS/SYSTEM-M/4
Second FLS/SYSTEM-M/4
So those are the same. The one, which don't connect I dont know at the moment. One non working device can be added as already installed device if not removed. After checking details it shows it's offline.

SamuelS · April 4, 2024, 10:30am

I have removed most of the lighting from Hue bridge and added those to Hubitat. Rebuilt hubitat network and I've already got 2 of 3 non working switches connected. It seems that the switches dont like to be connected straight to Hubitat and needs stonger mesh. I'll continue swapping devices from Hue to Hubitat and hopefully get all switches to work.

kkossev · April 5, 2024, 4:49am

Please update to the latest code of the Zigbee Button Dimmer 3.0.5 2024/04/05 7:24 AM

added 'FLSSYSTEM-M4' alternative model name, when modified by the Zigbee - Generic Switch driver.

You may need to pair the switch again (without deleting it!), but first try just updating the driver.

And ...
... I surprisingly managed to pair the Scheider switch to my C-8!
I successfully paired it when I was holding it at the most distant place in my apartment, far away from the C-8 hub!

Obviously, a Tuya Zigbee plug has been used used as a router/repeater during the pairing ...

Go figure ...

magnus.s · April 7, 2024, 1:18am

Thank you @kkossev ! Sorry for the delay in my reply. I will test the driver tomorrow and return with my findings.

magnus.s · April 7, 2024, 10:19am

@kkossev , I have now installed the new driver and Hubitat is now recognicing that the button does things. Unfortunately it does not work as such, but there are log entries that might add information about what is happening?

As you can see in the log file I pressed the button and also pressed the 'Configure' in the app. I executed a button push in the app as well just to se that the rule is working, which it is (it starts a fan). I also did a double tapp and a long press on the physical button.

I look forward to test any changes you may want to do and please let me know if I can be of help in any way.

Cheers,

PS. Before installing the new driver I re-paired the device as I thought I had removed it, but it turns out I had not. But I find conencting the device difficult. Not because it was already connected, but according to the instructions you are supposed to press the button 3 times within 0,5 seconds, which is tricky. And the light that turns on inside the button is so faint that you almost need to do it in a completely dark room to see if the pressing of the button was successful. Do you have the same experience or is my button a bad production example? What is your experience regarding the reliability of the button when trying to connect it @SamuelS ?

Device

Device setup

Log file

dev:6252024-04-07 12:13:25.751debugBadrummet Schneider Wiser button clearing the Status event

dev:6252024-04-07 12:12:46.150infoBadrummet Schneider Wiser button button 1 was pushed [digital]

dev:6252024-04-07 12:12:46.148debugBadrummet Schneider Wiser button push button 1

dev:6252024-04-07 12:12:42.131infoBadrummet Schneider Wiser button button 1 was pushed [digital]

dev:6252024-04-07 12:12:42.128debugBadrummet Schneider Wiser button push button 1

dev:6252024-04-07 12:12:37.940errorjava.lang.NullPointerException: Cannot set property 'isDigital' on null object on line 2019 (method on)

dev:6252024-04-07 12:12:37.933debugBadrummet Schneider Wiser button on() currentState=n/a

dev:6252024-04-07 12:12:30.695errorjava.lang.NullPointerException: Cannot set property 'isDigital' on null object on line 2019 (method on)

dev:6252024-04-07 12:12:30.675debugBadrummet Schneider Wiser button on() currentState=n/a

dev:6252024-04-07 12:12:25.794infoBadrummet Schneider Wiser button executed 'configureNow'

dev:6252024-04-07 12:12:25.793warnBadrummet Schneider Wiser button sendZigbeeCommands: no commands to send!

dev:6252024-04-07 12:12:25.783debugBadrummet Schneider Wiser button sendZigbeeCommands(cmd=[[he raw 0xDDA8 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200], zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147])

dev:6252024-04-07 12:12:25.779debugBadrummet Schneider Wiser button configure(): returning cmds = [[he raw 0xDDA8 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200], zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147]

dev:6252024-04-07 12:12:25.730infoBadrummet Schneider Wiser button sent device configuration

dev:6252024-04-07 12:12:25.729debugBadrummet Schneider Wiser button customConfigureDevice() :

dev:6252024-04-07 12:12:25.728infoBadrummet Schneider Wiser button configureDevice...

dev:6252024-04-07 12:12:25.682debugBadrummet Schneider Wiser button customInitializeDevice() : [zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147]

dev:6252024-04-07 12:12:25.679debugBadrummet Schneider Wiser button Schneider Electric WDE002924

dev:6252024-04-07 12:12:25.676infoBadrummet Schneider Wiser button initializeDevice...

dev:6252024-04-07 12:12:25.672infoBadrummet Schneider Wiser button tuyaBlackMagic()...

dev:6252024-04-07 12:12:25.670debugBadrummet Schneider Wiser button configure(): settings: [logEnable:true, reverseEP:false, txtEnable:true]

dev:6252024-04-07 12:12:25.668infoBadrummet Schneider Wiser button configure...

dev:6252024-04-07 12:12:25.667infoBadrummet Schneider Wiser button configure(Configure the device)...

dev:6252024-04-07 12:12:15.687infoBadrummet Schneider Wiser button executed 'configureNow'

dev:6252024-04-07 12:12:15.686warnBadrummet Schneider Wiser button sendZigbeeCommands: no commands to send!

dev:6252024-04-07 12:12:15.668debugBadrummet Schneider Wiser button sendZigbeeCommands(cmd=[[he raw 0xDDA8 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200], zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147])

dev:6252024-04-07 12:12:15.657debugBadrummet Schneider Wiser button configure(): returning cmds = [[he raw 0xDDA8 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200], zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147]

dev:6252024-04-07 12:12:15.556infoBadrummet Schneider Wiser button sent device configuration

dev:6252024-04-07 12:12:15.555debugBadrummet Schneider Wiser button customConfigureDevice() :

dev:6252024-04-07 12:12:15.553infoBadrummet Schneider Wiser button configureDevice...

dev:6252024-04-07 12:12:15.550debugBadrummet Schneider Wiser button customInitializeDevice() : [zdo bind 0xDDA8 0x15 0x01 0x0001 {680AE2FFFE6A7007} {}, delay 141, he cr 0xDDA8 0x15 1 33 32 300 14400 {01} {}, delay 141, zdo bind 0xDDA8 0x15 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 142, zdo bind 0xDDA8 0x15 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 144, zdo bind 0xDDA8 0x16 0x01 0x0006 {680AE2FFFE6A7007} {}, delay 145, zdo bind 0xDDA8 0x16 0x01 0x0008 {680AE2FFFE6A7007} {}, delay 146, zdo bind 0xDDA8 0x15 0x01 0x0005 {680AE2FFFE6A7007} {}, delay 147]

dev:6252024-04-07 12:12:15.545debugBadrummet Schneider Wiser button Schneider Electric WDE002924

dev:6252024-04-07 12:12:15.485infoBadrummet Schneider Wiser button initializeDevice...

dev:6252024-04-07 12:12:15.480infoBadrummet Schneider Wiser button tuyaBlackMagic()...

dev:6252024-04-07 12:12:15.474debugBadrummet Schneider Wiser button configure(): settings: [logEnable:true, reverseEP:false, txtEnable:true]

dev:6252024-04-07 12:12:15.472infoBadrummet Schneider Wiser button configure...

dev:6252024-04-07 12:12:15.470infoBadrummet Schneider Wiser button configure(Configure the device)...

dev:6252024-04-07 03:14:22.750infoBadrummet Schneider Wiser button button 1 was pushed

dev:6252024-04-07 03:14:17.435infoBadrummet Schneider Wiser button button 1 was pushed

dev:6252024-04-07 03:14:00.028debugping() is not implemented

kkossev · April 7, 2024, 12:13pm

Hi @magnus.s ,

You need first to successfully pair the Schneider switch to the HE hub with this driver pre-installed.

This driver must be selected automatically during the pairing process, otherwise it will not work.

I will think what I can do in the driver to help others to avoid such mistakes (thinking that clicking on the Confgure() button will have any effect on sleepy battery-powered devices….). Unfortunately, HE user interface for the drivers page is very limited as possibilities..

Yes, pairing is a bit tricky wit this device. You can try also to factory reset it - quickly press 3 times and on the 4th click hold the button down for 10 seconds. The switch LEDs will blink differently, depending on whether the device was successfully reset to the factory settings or just switched into pairing mode.

It will be better to complete delete the device from the HE hub first (use the REMOVE DEVICE red button) and then pair it again. As your hub is a C-7, there shouldn’t be any risk in deleting and re-pairing.

magnus.s · April 7, 2024, 10:09pm

Having removed the device using the red remove button I am unfortunately so far unable to reconnect it again. I can now fairly easily get it into paring mode but it does not connect. So I think it needs a factory reset before being able to connect again. The problem is, I cannot get it to reset. I press three times and then a fourth but nothing happens after 10 seconds when a red light is supposed to blink. I must have tried it 15 times by now.

I have tried doing four consecutive fast clicks, in which case no lights come on at any time.
I have done three fast clicks and waited for half a second or so and then pressed the button and held it, before the lights start to blink.
I have pressed three times quickly and then waited for the light to blink before pressing the fourth time and holding.
I have pressed three times quickly and waited for the light to stopp blinking and then pressed and hold for 10 seconds.

Unfortunately the device never blinks after 10-15 seconds to acknowledge a reset. As it wont connect I assume there never is a reset. Some times a random l blink has occured after 3-5 seconds when no blink should occure, but it does not reset. Very frustrating.

How do you do the fourth click? Three fast clicks, waith for half a second or so and then hold? Do you wait for the device to start blinking before pressing and holding?

EDIT: I have also changed the batteriy.

SamuelS · April 8, 2024, 3:57am

Gog morgon @magnus.s.

Connecting Schneider devices in C-8 is a pain. Connectin procedure in button itself goes like three clicks ~0,5sec between cliks. So that's moderate frequency. Resetting device, is the same way, but four clicks. Fourth click you should keep pressing the button 10sec, after 5 seconds yellow led blink and after 10 seconds red leds blink and it's time to release the button. Then it's reset. I think on 4 button models its top right button and two button models the top one.

If I understood @kkossev right the C-7 is not so hard to connect straight to hub, but you can try the same thing that I did with my C-8. Go near the furthest mesh repeater and try to connect the button next to it. As far away as possible from Hubitat main unit.

magnus.s · April 8, 2024, 10:38pm

Hyvää iltaa Samuel,

Thank you for your advice and suggestions! I think mine might be broken. If I do four clicks and hold on the fourth click, I get no lights at any time. I'll try again tomorrow.

Cheers,