Domoticz

Hi all,
Does anyone know if the "The Button" works in domoticz. Could not find any information about it.
http://www.vesternet.com/z-wave-fibaro-button

Hi there, in the actual beta it is recognized but does not work. From what I've read there are changes in OZW necessary, because the Button needs support for central scenes which will be implemented with OZW 1.6

Thanx for that So it just to wait and see then.

In case this helps anyone, you can actually use the Fibaro FGPB101 Button with Domoticz through zwave associations, meaning you can associate one or more zwave devices with the Fibaro Button using association group 2 (for on/off) or 3 (for dimmers) for the buttons...

Using Domoticz 3.5942 I have been able to drive a Fibaro FGS223 Double Relay (new version notoriously difficult to handle for zwave controllers) with two Fibaro FGPB101 Button, using multichannel association from the openzawave control panel: my first button has a group 2 association with the FGS223 switch 1 using node x.1 and the second button also a group 2 association with the FGS223 switch 2 using node x.2 (where X is the zwave node number of the FGS223

Obviously I am however eagerly waiting for openzwave/domoticz to support zwave central scenes and use the Fibaro Button for more complex automation.

Logread wrote:In case this helps anyone, you can actually use the Fibaro FGPB101 Button with Domoticz through zwave associations, meaning you can associate one or more zwave devices with the Fibaro Button using association group 2 (for on/off) or 3 (for dimmers) for the buttons...

Using Domoticz 3.5942 I have been able to drive a Fibaro FGS223 Double Relay (new version notoriously difficult to handle for zwave controllers) with two Fibaro FGPB101 Button, using multichannel association from the openzawave control panel: my first button has a group 2 association with the FGS223 switch 1 using node x.1 and the second button also a group 2 association with the FGS223 switch 2 using node x.2 (where X is the zwave node number of the FGS223

Obviously I am however eagerly waiting for openzwave/domoticz to support zwave central scenes and use the Fibaro Button for more complex automation.

Have you been able to control S2 for scene activation via the FGPB101-button? I have only been able to control S1 (where my light is connected). I have nothing connected to S2, but I would like to be able to activate a scene by pushing the FGPB101 - button.

question... what is exactly a zwave central scene?

i use domoticz and I have the OCTAN Remote and i can execute actions, if i click button 1 then execute scene A ...

I mean, i can execute zwave scenes using the remote.. so, what am i missing related to the fibaro button?

thanks in advance for the explantaion,

nim

foogy wrote:Have you been able to control S2 for scene activation via the FGPB101-button? I have only been able to control S1 (where my light is connected). I have nothing connected to S2, but I would like to be able to activate a scene by pushing the FGPB101 - button.

I actually have two Buttons, each associated with a channel on the FGS223... so one Button controls S1 and the other S2... it is kind of hard coded so to say... when scenes get supported by openzawave then the click sequences (eg 1click, 2 clicks, etc) could control different actions/devices by the controller with just one button... At least that's my understanding.

i am still confused. i see you control your fibaro via association, but I can activate scenes via the OCTAN Remote. I use the remote to control, for instance, one click executes scene a, double click scene b, and so on.

I go to domoticz scenes, set up my scene, then click on Activation Devices - add decives and i get a differente device base on the combination of button clicks (up to 16)

What is exactly then a Central Scene?

nizaga wrote:i am still confused. i see you control your fibaro via association, but I can activate scenes via the OCTAN Remote. I use the remote to control, for instance, one click executes scene a, double click scene b, and so on.

I go to domoticz scenes, set up my scene, then click on Activation Devices - add decives and i get a differente device base on the combination of button clicks (up to 16)

What is exactly then a Central Scene?

Very interesting.. I do not know about the Octan remote but if it is a zwave device then it means we should be able to do same with the Fibaro Button... not consistent with what has generally been posted about the topic but this is to be investigated for sure. I am relatively new to Domoticz so expert advise is welcome

Hi, i have ordered a fibaro button... maybe you could try to add a domoticz scene and then click activation devices and then try a fibaro button combination.

The octan remote is a zwave device and i ensure i am launching different domoticz scenes.

Please try and let us know


Enviado desde mi iPhone utilizando Tapatalk Pro

further information.

from nodon octan user guide: http://www.vesternet.com/downloads/dl/f ... _guide.pdf

We strongly advise you to use « CENTRAL SCENE », which is more user friendly.
However, some home automation gateways don’t support « CENTRAL SCENE »
yet, then you can still use the previous standard « SCENE ACTIVATION ».
The user interface of your gateway will then allow you to set-up scenes

Parameter 3 in domoticz device config file:

<Value type="list" index="3" genre="config" label="Scene Type" min="0" max="1" size="1" value="0">
<Help>This parameter configures the type of command sent when the product is in "Gateway Centric Mode", with buttons profile configuration set in "Scene Behavior".</Help>
<Item label="Central Scene" value="0"/>
<Item label="Scene Activation" value="1"/>
</Value>

Still confused what Scene Activation is compared to Central Scene (i guess in Central Scene you manage scenes different in the gateway UI).

Could the fibaro button work on scene activation mode???

Regards,

nim

As far as I know there will be needed a new OZW release - or a patch.

Central Scene Command Class was/is not full supported by OZW, that's why there are problems with some devices.

https://github.com/OpenZWave/open-zwave/issues/367
https://github.com/OpenZWave/open-zwave/pull/993

Michael

Well...i have a "dirty" workarround to use the button until OZW 1.6 is released...

You can run a script that is listening

sudo tail -f /home/pi/domoticz/Config/OZW_Log.txt | grep Node065- add here your expressions

for the number of times you push the button, where

0x80 is one time
0x83 is twice
0x84 is three times
0x85 is four times

I have checked it several times and the number is consistentin every test (others are not)

2017-01-17 20:11:29.248 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4d, 0x80, 0x01, 0x20
2017-01-17 20:11:29.250 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7680 seconds. Sending event notification.
2017-01-17 20:11:29.250 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:31.798 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4e, 0x83, 0x01, 0x20
2017-01-17 20:11:31.799 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7860 seconds. Sending event notification.
2017-01-17 20:11:31.800 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:33.778 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4f, 0x84, 0x01, 0x26
2017-01-17 20:11:33.780 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7920 seconds. Sending event notification.
2017-01-17 20:11:33.781 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:36.028 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x50, 0x85, 0x01, 0x38
2017-01-17 20:11:36.029 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7980 seconds. Sending event notification.
2017-01-17 20:11:36.030 Warning, Node065, No ValueID created for Scene 1

You can use even monit and then execute an action based on the number of clicks and run a http command to turn on / of a scene.

I know, it is not a nice way but it works:)

Regards,

Nim

nizaga wrote:Well...i have a "dirty" workarround to use the button until OZW 1.6 is released...

You can run a script that is listening

sudo tail -f /home/pi/domoticz/Config/OZW_Log.txt | grep Node065- add here your expressions

for the number of times you push the button, where

0x80 is one time
0x83 is twice
0x84 is three times
0x85 is four times

I have checked it several times and the number is consistentin every test (others are not)

2017-01-17 20:11:29.248 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4d, 0x80, 0x01, 0x20
2017-01-17 20:11:29.250 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7680 seconds. Sending event notification.
2017-01-17 20:11:29.250 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:31.798 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4e, 0x83, 0x01, 0x20
2017-01-17 20:11:31.799 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7860 seconds. Sending event notification.
2017-01-17 20:11:31.800 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:33.778 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x4f, 0x84, 0x01, 0x26
2017-01-17 20:11:33.780 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7920 seconds. Sending event notification.
2017-01-17 20:11:33.781 Warning, Node065, No ValueID created for Scene 1

2017-01-17 20:11:36.028 Detail, Node065, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x41, 0x05, 0x5b, 0x03, 0x50, 0x85, 0x01, 0x38
2017-01-17 20:11:36.029 Info, Node065, Received Central Scene set from node 65: scene id=1 in 7980 seconds. Sending event notification.
2017-01-17 20:11:36.030 Warning, Node065, No ValueID created for Scene 1

You can use even monit and then execute an action based on the number of clicks and run a http command to turn on / of a scene.

I know, it is not a nice way but it works:)

Regards,

Nim

thanks!!

A practical example, please.

to understand better.

thanks for your time

Point to your OZW_Log.txt file (you need to enable debug, normaly the file is under /home/pi/domoticz/Config, mine is under /var/tmp (in memory, but this is not relevant now)

and then run a script, like this: in my case, the button is Node065 (change the node number to yours), i call the script with different paramenters, $1 is the number of the button clicks (0x80, 0x83..), $2 is the idx of the switch, $3 is the command (on /of... ) etc...

call the script (command line) like _(samble) myscript.sh 0x80 120 on >/dev/null &

this will execute ON in the device IDX 120 in domoticz whenever you click one in the button (0x80)

tail -fn0 /var/tmp/OZW_Log.txt | \
while read line ; do
echo "$line" | grep Node065.*"$1"
if [ $? = 0 ]
then
sudo curl -s -i -H "Accept: application/json" "http://127.0.0.1:8080/json.htm?type=com ... &passcode="
fi
done

enjoy!

First of all thanks!

I do not understand English well.

first step:
second step:
third step:

I create a file that I call "myscript.sh" (for example), with the code:
fourth step:
fifth step:

I call the script from a scene with:


Would it be all correct? Or I misunderstood it.

thanks for your time.

PD: I have installed domoticz in a synology

PD2: File path synology:

you need to run the script in background, so you don't need a scene. Just copy the script on your folder under for instance /home/pi/scripts, assign the right permissions using chmod and then execute "sudo bash myscript.sh 0x80 120 on> /dev/null &

Remember: my script is pointing to /var/tmp/OZW_Log.txt ... probably your OZW_Log.txt is running in another location.

regards,

thanks!! working!!!

Any update on this issue since last post?

/Jacob

I installed jeedom in another rpi, added a USB zwave stick and the button is recognized. I have not migrated to jeedom, I just use a virtual switch in jeedom to call a domoticz url switch and it works great


Enviado desde mi iPhone utilizando Tapatalk Pro