Came home to everything working, must of just had a hissy fit last night.
Still can't get it to work with Alexa though. 
Sadly not, it was much the same behaviour. Bobby (from support) provided some insight into the device though and shared information about the lights (on device itself) flashing different colours to indicate what the pairing was doing. I will try again and watch for flashing lights.
One thing that occurred to me after reading the information was that I actually have 4 of these devices packed away behind the switch to control all the lights in open area of house. I was trying to get just one working on HE whilst leaving the others up on ST. But it sounds like these devices talk amongst themselves so I may just need to bite the bullet and exclude them all from ST before attempting to add one. I will see what the flashing lights reveal first as I do not want to loose these automations. I seemed to have overcome all of the wifes eyebrow bashing and had them working pretty sweet.
Still no good, infact other than a green light for the exclude I saw no further lights on the device. I also excluded one of the other 212 devices from ST and tried that afresh, get the same response. Pairs ok, but then not able to control it, there is no mention of secure pairing in the logs but HE happily sends its instructions out.
One thing that I did notice that it spends a long time in initializing state (compared to other devices), is there a timeout on the 'securepairing' that can somehow be influenced - probably a question for Fibaro themselves?
I lost quite a lot of time to this but I am finally getting there and lights are now working (although not with all features). So there is something in this device that makes it very sensitive and I possibly ending up adding a few extra steps in that were unnecessary (like switching off the ST hub) but when I finally got it working I just stuck with it.
Here are the steps:
- Turn off the ST hub, can't see why this is necessary as the devices were excluded but when I finally got it working I had done this. Could be coincidence or noise on z wave channels.
- Get the hub/zwave radio near to the device, For me literally this was key, 24 inches was too far away and right next to it was too close. In the end I settled with about 6 inches.
- Generally speaking I had to always repeat many times before it worked, so be prepared for this to take some time.
- You must remove the light cover so you can see the device, the lights are helpful and you need to get to the B button on the device later.
- Exclude the device by clicking remove on HE/ST and then operate the light switch 3 times (very quickly).
- The lights will go into a calibration phase where they go on/off a few times. Leave this to complete the device has a green light that stays on some time after the routine finishes, wait for the green light to clear. The HE/ST screen should refresh and the device is gone.
- Now reset the device by holding down the 'B' button on the device itself. The light (on device) will cycle through several colours, you want the yellow ones (looks green to me) that comes after violet - last one in the series. When the yellow/ light is displayed you release 'B' button and then press it again quickly. The device will flash yellow and then red. Sometimes it would flash yellow once and sometimes several/many times. I suspect this is something to do with the success of the pairing but never quite fully understood it.
- In a tab on your browser goto HE site and open the logs screen.
- In another tab, goto HE and open the devices screen, click 'Add new device' and do a quick 3 click of the actual light switch. The device will normally appear in HE very quickly. If its not there in 5 seconds just do another triple click (you probably were not fast enough).
- It will go off into an initializing state and then come back with a 'Save' option. You can save it but in the end I got into the habit of just leaving it on this screen until I was happy that the device was talking ok.
- Goto the logs screen and after a few minutes you should see the following:
[dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:56.069 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 3A 01 00 1D 2A 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:56.043 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 21 01 01 BE 99 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:56.023 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 20 01 02 B9 CA 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:55.997 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 1F 01 01 60 3D 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:55.973 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 1E 01 02 67 6E 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:55.945 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 0E 01 01 14 6E 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:55.919 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 02 01 63 2D EB 7E 00 [dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:22:55.894 debug Device, parse description: zw device: 36, command: 5601, payload: 70 06 01 01 34 5E A9 7E 00
But then wait and this is where I think I went wrong so many times in that I was not patient and just figured it did not work and went on and tried again. You have to be patient. Some time after you will get some more entries :
[dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:29:19.305 debug Device, parse description: zw device: 36, command: 5601, payload: 31 05 04 22 00 00 79 DB 7E 00
[dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:29:09.474 debug Device, parse description: zw device: 36, command: 5601, payload: 31 05 04 22 02 1B BC E3 7E 00
[dev:554](http://192.168.1.224/logs/past#dev554)2018-09-30 13:29:09.093 debug Device, parse description: zw device: 36, command: 5601, payload: 26 03 00 3E F8 7E 00
- Now you are good to go. If you do not get these 3 lines I started again at step 5. Just be patient and take your time.
- Now I can change the device type. Just use the 'Generic z-wave smart dimmer'.
But I still have not had any success with the Fibaro device handler code published above, maybe I am still not connected securely? But frankly at this point I am happy and can limp along like this as I can now automate the lights in the main area of house. Its early days yet and I may need to fine tune some things but so far so good. I am using the HE Simple lighting app and from what I can tell it does everything I need with 'Override lights with switch' feature, On ST I was using Core to control the switch override. On HE its a lot faster/simpler - zero lag on walking into room. It reminds me that this is why I did this!
I will come back to the 212 device handler at a later stage but for now I am over it. Wasted too much of my life on it. Hopefully I can prevent the same for someone else having to experience the same pain. Oh, I nearly forgot, don't forget to leave out a bit of beer in a walnut shell as an offering to the Home automation fairies, this undoubtedly helps in this process.
I'm trying to use the Dimmer 2 driver and at the moment I don't have momentary switches so need to set parameter 20 to Toggle. This is what I get:
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:54:58.812:errorjava.lang.NullPointerException: Cannot invoke method toInteger() on null object on line 513 (updated)
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:54:58.780:debugconfigureAfterSecure()
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:59.287:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 3A 01 00
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:59.223:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 21 01 00
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:59.161:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 20 01 02
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:59.095:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 1F 01 01
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:59.030:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 1E 01 02
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:58.971:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 0E 01 01
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:58.903:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 02 01 23
[dev:72](http://10.179.185.144/logs#dev72)2018-10-22 09:53:58.837:debugDevice, parse description: zw device: 1B, command: 9881, payload: 00 70 06 01 01 0A
The hub doesn't seem to be able to get the status. I'm using discover which finds the device in an UNKNOWN status, then applying the Dimmer 2 driver. The lights manually switch on and off, but the hub doesn't recognise the action before or after applying the driver.
Any advice?
Use the basic zwave tool installed as driver. Discover devices then set it to be basic z wave tool, Set parameters and set it back to the zwave wave dimmer. Use the logs to see what it's doing.
Thanks Jim. I managed through trial and error to get the modules connected, though very temprementally all the way. I still have one module that works from the web interface, but is not updating from the physical switch. But I believe the very first one was like this and a combination of hub reboots and z-wave repairs got this working.
I'm not exactly sure what the Super basic Z-Wave parameter tool does, but I will take a look at it. Thank for the suggestion.
========
For anyone else with Dimmer 2's using this driver, these are the steps to my somewhat success, albeit it sometimes the sequence needs to be repeated a few times in all sorts of combinations:
-
Install the dimmer 2 driver (obviously) (general instructions)
-
Attempt an include by discovering device then 3 times in/out (momentary switch) or up/down (toggle/rocker switch)
if successfully appears, and saved in devices, go to 3, else try combinations of:
- repeating step 2 one or two times
- settings > Z-wave > Z-wave exclude, then exclude (as per 3 times toggle/switch action), and see if an unknown device is excluded in logs. If it is, then wait for the recalibration to finish, then start at step 2 again
- sometimes includes and excludes seem to work, or devices appear that weren't there before, after a hub reboot
- sometimes settings > Z-wave > Z-wave repair works
- Select custom dimmer 2 from device type list and save
- Use the physical switch (before web interface) to switch the light on or off (up/down if rocker switch) and check to see if the status updates (top-right)
if it does, got to 5, else try:
- excluding the device as per step 2, bullet 2, and start at step 2 again after calibration
- step 2, bullet 4, and step 5 if good, step 2 bullet 2 if not
- Happy days
Other issues you may come across if using a toggle switch, is that the synchronisation of on/off (up/down) to switch a light on might not work and you end up having to do an up/down/up (or vica versa). And it seems parameter 20 to change from momentary to toggle doesn't work in this driver so even if you save it as such, it still acts as a momentary. I'm waiting for my retractive/momentary switches to arrive before I have to redo all of this...
On a positive note, out of roughly a dozens modules installed there were only 2 or 3 that I had to go through all of the combinations above to get them working. All of the others seems to add perfectly if I followed the happy path sequence above.
The Super Basic Z-Wave Parameter Tool is similar in operation to the ZWave Tweeker over on ST. You use it when you discover you'd like your specific ZWave device to work "better/differnet" than what the driver you are using sets up. You know that ZWave devices have Options within, right? Some of them are mandatory, some are optional and some, the option selected by your selected driver, doesn't match what you want. The Super Basic Z-Wave Parameter Tool helps with that ONLY.
Let's imagine you have an LED on your switch/dimmer and it comes on when the light is off.. great as a nightlight, but you don't want that. You go to the Vendor's documentation determine the values you'll need to change that and SWAP the driver you are using with: Super Basic Z-Wave Parameter Tool. The device page changes to display the tool, and you enter the values you got from the manual. Then SWAP back to your original driver... but do NOT click config, since there's a good chance the driver would just overwrite what you did.
In other words, you did a Config at least once using the desired driver, you swap to the Tool, change some parameters and swap back. There's no need for further clicking of the config button.
1 Like
Sounds excellent. I'm sure once I've got the hang of some of the basics of the Hubitat, and venture on to tweaker mode, I'll make very good use of this. Thanks for the advice!
It's rare to need this.. but when you do NEED it, there's nothing else like it 
1 Like
Hi,
I've been running with the driver for a while, but didn't have to congure any of the device settings until now.
I am trying to force a calibration but the configure button ins't there. and the device says' sync pending'...
Any ideas?
I may be misunderstanding you, and I don't know exactly how the parameters work, but I believe you can force a calbiration using parameter 13. You select option 1 or 2 depending on whether you've installed with a bypass, and then save the parameter change.
I used to do this on my Fibaro HC2, but i would imagine it would work the same here. Here's the manual page in case you want to double check I've got it right.
Hi, thanks for the reply. I can see the parameter in the drop down to force a calibration but when I select this and save the device status just reports “sync pending”. There isn’t a “configure” button to make the parameter take effect and start the calibration ...
I know this might sound a silly question, but having done this myself just recently I'm going to ask... Did you press the correct Save button? There's one associated to the parameters, and one further down for saving the device details.
I have the same so it wont let me send the parameters
I am having some issues with this driver and am looking for some advice.
- I have selected Parameter 20 to Toggle Switch (Value 1) and saved it (using both save buttons). The list of Parameters shows "1 - Toggle Switch" even when I refresh the screen, so it looks to have saved, but when I operate the switch it still acts as a momentary switch.
- The device appears to be communicating with HE as when I dim the lights, the "Current States - Level" follows, but the other values remain the same; "energy" remains at 0, and "Switch" remains on regardless of the position the switch is in. "syncPending" also remains at true and does not seem to go to false (it was false earlier in the day).
- I have set up a Dashboard Switch for this, the readout follows the actual % read out of the lights, but does not allow me to control them.
Does anyone know what I am doing wrong? I have followed a number of videos and this one (YouTube) is very good, but it is for a Fibaro HC2, so it doesn't explain the functionality of the HE driver.
You can wait for it to do the configuration changes automatically after a period of time, or you could try pressing the 'B' button 3 times quickly (which puts the device in config mode) and then press the configuration button in the device app. This should update the device with the latest configuration.
Have logging open in another window and you should see the configuration being sent to the device. (I think), 
I tried this, but there is no config button for this. I tried using the set single parameter button, but this didn't work. There is a set levels button with two fields but I am not sure how this works.
What device handler are you j
using?
EDIT: I assume the one at the top of this thread.
Have you tried changing the parameters to what you wish, open a new logging window and then press the B button 3 times?
Can you see the config being pushed to the device?
