Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge
-
I have installed my UZB1 stick on my RP4 and want to megrate my device form my Vera to z-way. Now I want to use my Roller shutter 2 in z-way.mev as a scene controller. This is activated by 2x / 3x clicks on the switch. This works perfectly with vera (verabridge) in openluup and reactor using variable LastSceneID and LastScenetime.
Fibaro documentation:
When using z-way.me and z-way bridge it works differently. In reactor I see the variable below. I don't know how to use it. Maybe someone else can help me.
-
I have installed my UZB1 stick on my RP4 and want to megrate my device form my Vera to z-way. Now I want to use my Roller shutter 2 in z-way.mev as a scene controller. This is activated by 2x / 3x clicks on the switch. This works perfectly with vera (verabridge) in openluup and reactor using variable LastSceneID and LastScenetime.
Fibaro documentation:
When using z-way.me and z-way bridge it works differently. In reactor I see the variable below. I don't know how to use it. Maybe someone else can help me.
@edwin1972 I do not have the same device, but I have added logic to capture clicks/doubble-clicks etc from a Remotec ZRC-90. The logic has the same structure as your Vera screenshow, using "updates" and the pressed value.
For my ZRC-90 the values when pressing the buttons in Vera were not the same as in Z-way. Also the names of the variables could be different.
What you can do is to add the device and all variables to a condition in Reactor. You should then be able to find out how they change when pressing the buttons in various ways since the current value to each varible is shown to the right. Hopefully that helps, if not it could be that something needs to be added to the bridge to fully map the variables and them being updated for the Fibaro.Here is an old thread on the ZRC-90, it could perhaps be of some assistance.
-
A warning about any variables from the ZWay bridge which start with
zway_......they are only really there for development purposes, and they are special, in that they do not trigger a watch when their value is changed. For any recognised device, their values should get translated into more familiar serviceId/variable names which are able to be watched for changes.
-
I have installed my UZB1 stick on my RP4 and want to megrate my device form my Vera to z-way. Now I want to use my Roller shutter 2 in z-way.mev as a scene controller. This is activated by 2x / 3x clicks on the switch. This works perfectly with vera (verabridge) in openluup and reactor using variable LastSceneID and LastScenetime.
Fibaro documentation:
When using z-way.me and z-way bridge it works differently. In reactor I see the variable below. I don't know how to use it. Maybe someone else can help me.
I think it works the same, It is just that z-way bridge has not yet been set up to port these variables/command classes to openLuup. I may take a deeper look when I get some more time. It is a busy weekend for me this week.
-
Just looking quickly into it: From the documentation you shared, there are several operating modes to this switch which you need to setup using the user configuration parameter 14 and/or 10.
1.What configuration are you using for these 2 parameters? (maybe look at the expertUI into the expert command screen and look for the configurations)
2.Depending on the configuration used, the behavior should then be identical to the vera: It should report that the scene was activated using the LastSceneTime called LastUpdate in zway but associated with the specific scene number 12, 13, 14 or 16 (hold/release/2xclick/1xclick) which is where you should see the event. Oddly the z-way bridge, and therefore z-way, is posting scene codes 14, 16, 24, 25 and 26 but I have not read the full documentation. It would be interesting to see if you see any of these variables update in z-way when you activate each scene event from the scene controller. -
I have set the following parameters in Vera
I have set the following parameters in Z-wave.me
By scene activation, z-way.me created a number of buttons like this. When I press this button, the relevant scene is activated. In ReactorOpenLuup The variable zway_Remote_2-0-0-14-S_LastUpdate change but the variable zway_Remote_2-0-0-14-S stays ON. None of the variables change to the value of sceneID (14,16,24,25 or 26)
-
I have set the following parameters in Vera
I have set the following parameters in Z-wave.me
By scene activation, z-way.me created a number of buttons like this. When I press this button, the relevant scene is activated. In ReactorOpenLuup The variable zway_Remote_2-0-0-14-S_LastUpdate change but the variable zway_Remote_2-0-0-14-S stays ON. None of the variables change to the value of sceneID (14,16,24,25 or 26)
@edwin1972 said in Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge:
By scene activation, z-way.me created a number of buttons like this. When I press this button, the relevant scene is activated. In ReactorOpenLuup The variable zway_Remote_2-0-0-14-S_LastUpdate change but the variable zway_Remote_2-0-0-14-S stays ON. None of the variables change to the value of sceneID (14,16,24,25 or 26)
I am not using my scene controllers to trigger scenes but as direct association buttons to turn on and off groups of devices so forgive my ignorance. My understanding of how the scene controllers work is that when you physically toggle a scene, it will just send a command class to update the LastUpdate variable. The zway_remote_xxx is a virtual device attempting to represent the scene as a button. The fact that it stays on is expected (I think the vera used to do the same thing as you would have to trigger an off scene to turn the button off) as the fibaro doesn't have a corresponding off scene. There may be a plugin for this specific type of scene controller on z-way to make the virtual device turn off some time after it triggers.
Now, if like me you don't use the z-way smarthome interface and will be interracting with openLuup, then the variable zway_Remote_2-0-0-14-S_LastUpdate getting updated is the only thing which is needed to trigger your scene. You could just add a variable watch on this variable for the specific scene you want to trigger on openLuup and do the same for each specific variable. Am I missing something?
-
@edwin1972 said in Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge:
By scene activation, z-way.me created a number of buttons like this. When I press this button, the relevant scene is activated. In ReactorOpenLuup The variable zway_Remote_2-0-0-14-S_LastUpdate change but the variable zway_Remote_2-0-0-14-S stays ON. None of the variables change to the value of sceneID (14,16,24,25 or 26)
I am not using my scene controllers to trigger scenes but as direct association buttons to turn on and off groups of devices so forgive my ignorance. My understanding of how the scene controllers work is that when you physically toggle a scene, it will just send a command class to update the LastUpdate variable. The zway_remote_xxx is a virtual device attempting to represent the scene as a button. The fact that it stays on is expected (I think the vera used to do the same thing as you would have to trigger an off scene to turn the button off) as the fibaro doesn't have a corresponding off scene. There may be a plugin for this specific type of scene controller on z-way to make the virtual device turn off some time after it triggers.
Now, if like me you don't use the z-way smarthome interface and will be interracting with openLuup, then the variable zway_Remote_2-0-0-14-S_LastUpdate getting updated is the only thing which is needed to trigger your scene. You could just add a variable watch on this variable for the specific scene you want to trigger on openLuup and do the same for each specific variable. Am I missing something?
@rafale77 said in Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge:
the variable zway_Remote_2-0-0-14-S_LastUpdate getting updated is the only thing which is needed to trigger your scene. You could just add a variable watch on this variable for the specific scene you want to trigger on openLuup and do the same for each specific variable. Am I missing something?
see:
@akbooer said in Use Scenes (2x/ 3x click) from Fibaro Roller Shutter 2 in openluup with zway bridge:
A warning about any variables from the ZWay bridge which start with
zway_......they are only really there for development purposes, and they are special, in that they do not trigger a watch when their value is changed. For any recognised device, their values should get translated into more familiar serviceId/variable names which are able to be watched for changes.
-
Not owning the device or anything similar is making things a bit complicated. I am taking guesses here:
@akbooer, this device is reporting a command class 0 which should be recognized by the bridge correctly as a scene controller. However it needs to create multiple "sl_SceneActivated" and "LastSceneTime" variables corresponding to instance 0, then for each of the meta 14, 16, 24, 25 and 26 which correspond to "scene numbers".@Edwin1972, for a start, can you make sure the the bridged device on openLuup uses this device_file "D_SceneController1.xml" as its attribute? There is a possibility that this alone will get you very close to the finish line.
-
I am not familiar with this . I don't understand what you want to know. I would like to provide you with information, but I do not quite understand what you are asking. Can you give me some more detail how to give your requested information.
These are my settings:
-
Yes! This is very helpful. Now the only confusion I have is about how you intend on using this controller. Is it still intended to be a roller shutter switch + scene capability or are you intending for it to become a scene controller?
Edit: Try the file below which should enable at least the scene last update variable to get updated. Ideally it would be better to create a child device for the scene controller portion of it but for now it adds new variables to the windowcovering device. I also don't know how it handles multiple "scene" containers as it should be creating one variable for each but some additional changes may be required to make that happen.
-
Yes! This is very helpful. Now the only confusion I have is about how you intend on using this controller. Is it still intended to be a roller shutter switch + scene capability or are you intending for it to become a scene controller?
Edit: Try the file below which should enable at least the scene last update variable to get updated. Ideally it would be better to create a child device for the scene controller portion of it but for now it adds new variables to the windowcovering device. I also don't know how it handles multiple "scene" containers as it should be creating one variable for each but some additional changes may be required to make that happen.
-
Yes! This is very helpful. Now the only confusion I have is about how you intend on using this controller. Is it still intended to be a roller shutter switch + scene capability or are you intending for it to become a scene controller?
Edit: Try the file below which should enable at least the scene last update variable to get updated. Ideally it would be better to create a child device for the scene controller portion of it but for now it adds new variables to the windowcovering device. I also don't know how it handles multiple "scene" containers as it should be creating one variable for each but some additional changes may be required to make that happen.
-
Thanks for your comment. I do not understand what you mean. Maybe you know how to fix this.
You may have forgotten how to establish a login session:
You need to go under the openLuup console and use the action screen of the z-way bridge in the console.
This will log you in. Then to prevent your security token from expiring, you need to go make it permanent by going into the z-way smart home UI under options/my settings and click on the hour glass for the token you just established to make it an infinite loop:
. I was not going to change the generic behavior... just adding support to the command class.
