All press modes can be activated by changing the device type to a scene controller, and using a customized json file.
The Fibaro Button seems to set a variable “sl_CentralSceneAttr” to different values depending on how the button was pressed. Values are as follows: 0=one click, 1=hold and release, 2=button is being held (set to → 1 when released), 3=double click, 4=three clicks, 5=four clicks, 6=five clicks. Scene number (variable “sl_CentralScene”) seems to always be 1.
To anyone who’s interested, here’s how I made it work:
I’ve made a quick and dirty json for enabling all the press modes. Get the file from [url=http://pastebin.com/raw/9BgxNkyj]http://pastebin.com/raw/9BgxNkyj[/url] and save it as D_FibaroButton1.json
Upload the json file to you Vera: Apps → Develop Apps → Luup Files → Upload
Then go to Devices → Your Button → Advanced, and change the following fields:
To reload the luup engine, go to Apps → Develop Apps ->Test Luup code (Lua), and write “luup.reload()” (without the quotes) to the code field and press GO (btw, is there an easier way to do this?).
You can now create scenes for different press modes by entering scene number “1” to “Which scene number” field and selecting the appropriate press mode from the dropdown menu, under the “Whenever a scene is activated” option.
Hope this helps anyone struggling with Fibaro Button and Vera!
Hi I tried your fix for the fibaro button but I can’t seem to get it working… (I am also completely new to this z-wave thing…)
I got as far as getting the file in and changing the button to a scene controller but when I want to make a scene I have to type a scene into the settings?..
It looks like this:
Whenever My Button…
A scene is activated
Which scene number (Here I can only type a number but I don’t know what to type)
How is the button pressed: “The key is pressed 1 time” (Scroll down menu)
I am a bit clueless here so I hope you can assist ;D THX
I have tried Jakki’s solution and although I can activate a scene with one click, I cannot manage to achieve a second scene (with two clicks). All that happens is the first scene runs again.
Is there something I’m missing? I have the scene number set to 1 (tried 2, no luck).
An email to MCV support elicited the following response:
<<I’ve addressed this to my colleagues from the development department and since we’ve received various requests to integrate this device with our system, we will look into it but I don’t have an ETA for when it will be released.>>
That is good news, especially for a newbie like myself
I don’t if the team is reading this but it would be great if the integration supports some kind of toggle mode. (1 press for “on” 1 press for “off”)
The same way as the inputs on the Fibaro RGBW controllers or the Fibaro Dual switch.
That way it would be easy to integrate the button into an excisting lighting installation using it for both scenario activation as well as light on/off.
My button works fine using a single press to activate a scene, however Vera permanently has the device as ‘no longer connected’ which is annoying because I like the green happy face! Does anyone else have this issue, or is there a way to override the device detection for the button to stop it being reported as offline?
The Beta firmware seems to have addressed the issue with battery devices showing offline. Hopefully when they release it officially it will resolve your issue.
How can I pair devices with the standad method? It seems the vera unit tries to pair with the secure method by default. How can I tell the unit to pair with the standard method?
Hi: I can add the Button but I get the following message:Waiting for wakeup to configure device.
Four clicks is suppose to wake it up, but nothing happens?
Can someone help?
Thank you.
ciro307
Usually a secure add can only occur if the device is close to the Vera. Try adding the device from a long way away, that may force it into unsecure add mode.
Hi
I have applied the provided jason script. Unfortunately after first initial success something went wrong.
When I added first Fibaro Button it wasn’t working. Then I have found this solution and applied it. It made Button working with one press and it was fine for me so added the second button then.
Next day had to travel and when returned back my wife told me the buttons are not working. Her mobile app is not working and in fact nothing was working. I couldn’t operate anything, I couldn’t run scenes. The UI completely froze although I could login to box with putty.
I mailed the support saying what was changed but they only recovered from last backup. The next response from support mentioned they did several tests. And nobody has paid attention to my first mail saying I was playing with these buttons. Of course my Vera Edge is still not working. OK, it is working, consuming energy but can’t operate it.
So my question:
Is there any way to remove this D_FibaroButton1.json file manually without using UI just from shell?
I couldn’t find any useful info on where and in what way json files are stored (zip/tar?). Couldn’t also find the file using linux command: find . -name "*D_FibaroButton1.json*" from root. Even couldn’t find any “json” file at all.
[quote=“jakki, post:21, topic:193627”]All press modes can be activated by changing the device type to a scene controller, and using a customized json file.
The Fibaro Button seems to set a variable “sl_CentralSceneAttr” to different values depending on how the button was pressed. Values are as follows: 0=one click, 1=hold and release, 2=button is being held (set to → 1 when released), 3=double click, 4=three clicks, 5=four clicks, 6=five clicks. Scene number (variable “sl_CentralScene”) seems to always be 1.
To anyone who’s interested, here’s how I made it work:
I’ve made a quick and dirty json for enabling all the press modes. Get the file from [url=http://pastebin.com/raw/9BgxNkyj]http://pastebin.com/raw/9BgxNkyj[/url] and save it as D_FibaroButton1.json
Upload the json file to you Vera: Apps → Develop Apps → Luup Files → Upload
Then go to Devices → Your Button → Advanced, and change the following fields:
To reload the luup engine, go to Apps → Develop Apps ->Test Luup code (Lua), and write “luup.reload()” (without the quotes) to the code field and press GO (btw, is there an easier way to do this?).
You can now create scenes for different press modes by entering scene number “1” to “Which scene number” field and selecting the appropriate press mode from the dropdown menu, under the “Whenever a scene is activated” option.
Hope this helps anyone struggling with Fibaro Button and Vera![/quote]
Hi.
I am new to z-wave and i am now struggling with The Button. I have Vera Plus.
I have tried to change the json file, and did as described in this post. But then the button disappear.
I have tried several times, factory resetting the button. But i dont understand what im doing wrong.
My experience with Vera, and zwave are limited. So I hope you can help me…
