That’s alright. Thanks a lot, you’ve been more than helpful. I’ll do my research.
Good to know, thanks. I knew it would be based on the DTH but didn’t think about some of them being supported offline if using standard device types!
Many thanks for your hard work. It works perfectly also for the device Philio PAN06-1B.
Just a note. Please add parameter 2 because it’s very important, you can change the type of the pysical button.
I added this code :
input name: “param2”, type: “number”, range: “1…3”, defaultValue: “1”, required: false,
title: "Change the physical button mode. " +
“1 - Edge mode,\n” +
“2 - Pulse mode,\n” +
“3 - Edge-Toggle mode\n” +
“Default value: 1.”
and this:
zwave.configurationV1.configurationSet(parameterNumber:2, configurationValue:[param2.value]).format(),
With this parameter you can change everything.
Again …thanks a lot.
It should be good to see how many switch can use the same configuration.
Chris
1 Like
Thanks for that, the Fibaro doesnt actually list that specification/param on their website, hence I’ll do some testing of the addition and see what effect it has. If it doesnt cause a problem for the Fibaro then I’ll merge your changes, thanks! Otherwise if it causes a problem I’ll maybe merge them but leave them commented out or something like that.
Cheers,
Chris
Hi Chris,
What exactly does this parameter do? Not quite understanding the selections etc.
Thanks!
I found this description:
Edge Mode: The Position of the external switch determines the switching state of the relay. After a wireless
switching command it may be needed to operate the switch twice to return to the direct relation of switch
position and relay state. This mode is the factory default mode.
Toogle Mode: Each “ON”-Position of the external switch will toggle the state of the relays. This mode is
particularly suited for mono-stable switches.
Edge/Toggle-Mode: Every change of the state of the external switch results in a change of the relay state.
Essentially it permit you choose a pulse button and any press is a status change, change the state only when the physical button is on ON. and change the status at any press but without a pulse button .
For test I was using normal circuit breaker so parameter 3 was used, in the real circuit instead parameter 2 will be used and I will use pulse buttons.-
Anyway try to include in the title also philio 06 and 04. So other people will find this post.
Thx
Chris
1 Like
Hi Chris,
Thanks for the reply.
That sounds very similar to the Fibaro Parameter 14 - ‘Switch Type’ with the exception that there is no ‘Edge Mode’ but as Robin states it is not a ‘Fibaro’ parameter and is (unless I am completely misunderstanding this) actually Parameter 14 for the Fibaro devices.
Yes the parameters will be different, but it may still work. I was going to experiment with what happens if you set excess parameters on the Fibaro which aren’t defined. I’ll do a comparison of the parameters tomorrow and then can decide if the handler can cover both or not (though do agree a second DTH is probably better)
2 Likes
Whilst I am here 
Could it be possible to add an option under the Config page to change the names of ‘Switch 1’ and ‘Switch 2’ please? Just a nice to have and know I can change them in the DH itself of course.
Thanks!
Cheers Robin!
@crazy72
Ive checked it all out and it seems the Philio devices only have two configuration parameters (1 and 2), while the Fibaro uses 30ish (does use 1 but not 2).
Thankfully:
- Parameter #1 is virtually the same between devices (and unlikely to be touched)
- Parameter #2 is only used on the Philio and setting parameter #2 incorrectly on a Fibaro does nothing (that parameter just gets ignored) - I expect the same is true in reverse (setting parameter #3 upwards on a Philio).
Hence I do think it is logical to combine the device handlers so I will work on some wording and submit an update.
@anon36505037 if you think this is not logical then please let me know and I can split it, and submit as a separate DTH.
1 Like
Now updated the DTH for both Fibaro and Philio, thanks all.
It seems that the main 3 options for blind controllers are: Fibaro, Philio, Gubino.
Which one is best?
Sorry for the late reply, you are doing a great job.
Yes I testest parameter 2 and 3 don’t affect the devices that are ignoring them.
You can create an unique DH for both of them.
Thanks
Chris
Sorry I missed this response, I think I figured there wasnt too much I could contribute to the answer! I havent used any of them as this thread is more about the double relay than the specific blind controller (which admittedly is very similar to the blind controller)
I came here looking for a device handler for my Philio PAN06 as all the other dual relay device handlers switch endpoints 1 & 2, and the PAN06 uses 2 & 3 for S1 & S2 respectively. I’d already updated erocm1231’s generic dual relay handler and was using his sync smart app to create virtual devices, however this is a much better solution!
So I’ve taken the code you’ve already written and stripped out all the fibaro stuff, added a few UI tweaks and published a handler specifically for the Philio PAN06.
If anyone else is looking for a handler just for the Philio PAN06 / TKB TZ06 Dual Relay in-wall module then check it out…
1 Like
Hi all,
Firstly a huge thank you for all the hard work that so many of you are contributing with these device handlers etc. I’ve only very recently bought a Smartthings hub, but I’m amazed at its versatility, much of which is thanks to the code you’re creating and maintaining.
As I say, I’m pretty new to all this and still getting the hang of adding new device handlers etc. Maybe I’ve jumped in at the deep end somewhat with the FGS222 - I figured I had to start somewhere, but I have unfortunately run into some problems.
- I’ve gone into the Dev Tools and added the code at the start of this thread as a new device handler and published it.
- I then powered on the FGS222 and used the android app to add it to my smartthings hub. It finds it and adds it as ‘Z-Wave Device Multichannel’.
- I then go back into the Dev Tools, find the device, click edit and changed the Type to ‘Fibaro FGS-222 Double Relay’
- Going back into the app, I noticed that the listing of the device has changed somewhat and when I click on it, it presents a new graphical interface showing the two different switches
- At this point, however, I’m still unable to control the relay from this screen (or any other), so after a bit of playing about, I ended up pressing the ‘Service button’ on the device itself… and all of a sudden it sprang to life.
- I can now control each of the relays separately from the graphical screen which comes up in the smartthings app when I click on the parent device - yay!
- However, I still needed the two child devices to appear in my device list so I could control them independently etc. I clicked on the gear icon as instructed and renamed the device and pressed save… but unless I am missing something, the child devices are still missing and have not appeared in my devices list.
I’d appreciate any help, advice, tips or tricks on how to get this working.
Thank you in advance for your help
Chris
Hi Robin,
Yes, I noticed this being mentioned as a possible fix on the thread, so I tried it it a few times, including changing the device name and also some of the values in the variables, then pressing save… but to no avail.
Can you try repeating with live logging open (in the same webpage you added the device handler at the top and then you can filter for the Fibaro by clicking on it after the first log is received). After opening and closing settings there should be a hint about what is going wrong.
The other option you can try is filling in every value with the default before pressing save.
OK, I’ve opened and closed the settings with live logging enabled. This is the output:
5:10:41 PM: debug Executing 'configure’
5:10:41 PM: debug Preferences have been changed. Attempting configure() and update
5:10:41 PM: debug Executing 'configure’
5:10:41 PM: debug Preferences have been changed. Attempting configure() and update
I really feel like I am missing something which is very obvious to someone more experienced with ST. As I’ve said, I can control each of the relays independently, but only from the interface screen which appears when I hit the parent device. Am I looking for the child devices in the wrong place? (I’m looking for them to be listed as two separate entries on my ‘Things’ tab in the app. Is there a pre-requisite smartapp I need installed? On the parent device graphical interface screen, in addition to the cog in the top right to access configuration, there is a ‘configure’ button at the bottom of that screen (with a spanner and screwdriver symbol) - pushing that button does nothing - is that a known limitation - or does that give some further insight into what’s going wrong in my instance?
Again, your help is very much appreciated.