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?
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.
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.
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.
Please update to the latest code of the Zigbee Button Dimmer 3.0.5 2024/04/05 7:24 AM
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 ...
Thank you @kkossev ! Sorry for the delay in my reply. I will test the driver tomorrow and return with my findings.
@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
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.
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.
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.
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.
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,
I have now added the latest version of the driver to HPM.
For these of us who have already installed it manually, please try to use the HPM "MatchUp" function first.
If 'Match Up' does not work for some reason (it happens sometimes in my environment), you may end up with two drivers named '"Zigbee Button Dimmer".
First, find the devices that are using this driver by filtering for 'Zigbee Button Dimmer'
Then, for each device, manually change the devices that use the old driver to the new one installed via HPM and then delete the old one.
Finally, delete the old driver : ( it has an older 'Last Modified' time stamp) :
HPM 'Match up' did not find the Zigbee Button Dimmer. Please advise.
Cheers
Delete the manually installed driver and install it again using HPM.
I assume it is the 3.0.6 version using the same URL as above?
I got an error in HPM stating 'Invalid Package File'. It worked manually.
PS. I am still having difficulties connecting the button. I can easily get it to flash green with 3 clicks but it will not reset with 4 clicks. Id does not connect with 3 clicks so I assume it is because it was connected once before and it needs a reset. I have asked the electricican to bring another example of the button just to verif that it is nothing physically wrong with the button I have, It might be a few days before he comes around witht he new button and I can test it.
I think that I found and fixed the HPM 'Invalid Package File' issue (it was a typo in the repository file).
This weekend I migrated my old C-7-DEV hub to a new C-8-PRO, and I also had a hard time pairing the Schneider Wiser button. It is obligatory that the device is factory reset when moving between hubs.
The reset procedure that worked for me is - 4 clicks, the first 3 are short and the fourth one is long - you must keep the upper right button pressed until you first see a short green flash around the 5th second and then all the LEDS should start flashing red after the 10th seconds.
Then, the three-clicks procedure puts the device into pairing mode with the new hub,
Thanks for sharing Krassimir. In my case I think there is something wrong with the button (I have the single version with only one button). The electrician came by with a new button today and it lit up as a christmas tree 
This button has bright lights whereas the first one I used, besides never showing any red light, I had to sitt in a complete dark room to see the faint glow. The new one connected instantly and found the correct (your eminent) driver. I did a quick test now just before dinner and it worked well with a simple toggle on off rule. Brilliant Krassimir! Many thanks!
What functionality is implemented in the driver? 99% of the time I am happy with the ability to toggle on / off, but is there support for long press and or double click? What number of buttons are supported?
This is potentially a biggie as it seems to open up Schneider Electrics Exxact Wiser range of products. Have you had a look at them? If one is unlocked, do you think more of them could be unlocked? Are you using any other SE Wiser products @SamuelS ?
Currently, the driver supports pushed, held and released button actions.
For some other types of buttons it also supports a dimmer simulation - the level attribute automatically ramps up or down as you hold the upper or the lower button pressed down. You can use the HE inbuilt app ‘Mirror’ to control one or more dimmable bulbs as example…
Are you interested in dimmer simulation?
Ah, thanks. Excellent.
At the moment, no to be honest. Besides turning lamps on and off, I tend to use buttons for executing rule machine rules. On one off my other buttons, I use single click, double click and hold. For example, single click on the bathroom fan button executes a rule that turns the fan on and automatically turns it off when the humidity is back at 40%. Double click turns the fan on for an hour and then turns it off. Long press turns the fan off. I use it as a back up for a motion sensor in the shower that normally controlls the bathroom fan. Would support for a double click be an option to implement? I guess pressing once in different corners of button, if that would work, could service same purpose (even though it might be less practical to other family members to learn).
Your model supports long press only (followed by a ’released’ event). It is made to be used for dimming lights.
Download the Hubitat app
