FIB FGWDSEU-221 Walli Switch, Smart Switch, Z-wave 2nd way/channel: How to trigger a spec. scene[Solved], update Status in time[open]?

Other Devices & Integrations Lighting & Load Control
#1

The controller is a Vera plus Gateway with the latest beta Firmware
2 way switch : FIB FGWDSEU-221 Walli Switch, Smart Switch, Z-Wave

Include into the Gateway was also not a problem with the latest release SW (as general Z Wave device nor in the latest beta FW, which know the device.

The Associated Group reflects only channel 1 (First channel) and so Vera switch the main device (Group 1) in depent of the status from Ch1. Ch1 is only updated after timeout and poll the device.

I’m a new user with Vera, maybe I missed something…
I’ve try to associate the group 2&3 (Switch and dimm of Ch 1) and also group 4&5 (Switch and Dimm of Ch2) to the devices zwave and -_scene controller (with and without a zero in the textfield).

I’ve try to send a scene command (with different values (parameter 159 and 161) incl. change the parameter, so that the switch should send a scene ID for Ch 1&2 to the associated partner. But in the log I didn’t found/see anything :frowning:

I’ve try to add a startup, luascript with different settings like:

– Walli Switch (VeraID 47)
local YourDeviceID = 47

luup.variable_watch(“SceneActivation”,“urn:micasaverde-com:serviceId:SceneController1”,“LastSceneTime”,YourDeviceID)

function SceneActivation()
local lastSceneID= luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”, “LastSceneID”,YourDeviceID)

– ?? 98 Wert aus Parameter 158 (2&3 Assoziationsgruppe)für Doppelklick
if (lastSceneID== “1”) then
– 15 > VeraID der auszufuehrenden Scene
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”,“RunScene”,{ SceneNum=“15” },0)

– ?? Wert aus Parameter 161 (4&5 Assoziationsgruppe) für Doppelklick
elseif (lastSceneID== “2”) then
– 15 > VeraID der auszufuehrenden Scene
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”,“RunScene”,{ SceneNum=“15” },0)
end
end

How should /could I program the switch /Gateway, that the Walli switch reported a double click to the Vera Gateway and the GW can interact with the message?

It’s necessary to know the current status of Ch2 or control reproducibile, to implement some working scene; e. g. hold the state for Lamp1 or 2, switch off automatically, maybe remember the last lamp in combination withe a motion control

#2

I’ve try different things, but nothing is working.
The ID of the parent-Switch is 47, 2 Test-Scenes has the ID 15 and 16.
Firmware on Vera is the latest Beta,
Firmware on the Fibaro Walli Switch is VersinInfo “3,6,2,5,2”

The log shows me only

01 12/07/21 7:28:08.941 JobHandler_LuaUPnP::REQ_VariableGet variable not found <0x70761520>
06 12/07/21 7:28:09.812 Device_Variable::m_szValue_set device: 47 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0.0 now: 0.0 #hooks: 0 upnp: 0 skip: 0 v:0x109ba58/NONE duplicate:1 <0x77161520>
06 12/07/21 7:28:09.813 Device_Variable::m_szValue_set device: 47 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0x109bac0/NONE duplicate:1 <0x77161520>
06 12/07/21 7:28:18.056 Device_Variable::m_szValue_set device: 47 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_CentralScene was: 1 now: 2 #hooks: 0 upnp: 0 skip: 0 v:0x104d1a8/NONE duplicate:0 <0x77161520>
01 12/07/21 7:28:18.128 JobHandler_LuaUPnP::REQ_VariableGet variable not found <0x70561520>
02 12/07/21 7:28:18.248 ZWaveNode::HandlePollUpdate_Basic_Set node 12 device 47 unhandled <0x77161520>
02 12/07/21 7:28:18.408 ZWaveNode::HandlePollUpdate_Basic_Set node 12 device 47 unhandled <0x77161520>

The startupscript looks following now:
ocal YourDeviceID = 47

luup.variable_watch(“SceneActivation”,“urn:micasaverde-com:serviceId:SceneController1”,“LastSceneTime”,YourDeviceID)

function SceneActivation()
local lastSceneID= luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”, “LastSceneID”,YourDeviceID)
if (lastSceneID== “1”) then
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”,“RunScene”,{ SceneNum=“15” },0)
elseif (lastSceneID== “2”) then
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1”,“RunScene”,{ SceneNum=“16” },0)
end
end

#3

Trigger a scene is resolved.
Currently unsolved is the Status of Channel 2 in time (only available after polling)
A change of the name from one variable In the startup-Script was neccessary: Uncomfortable the timeout of the switch is to long (to catch maybe a following key-press and transmit the message to the Gateway)
Here is the working script:

local YourDeviceID_ = 47

luup.variable_watch("SceneActivation","urn:micasaverde-com:serviceId:SceneController1","sl_CentralScene",YourDeviceID_)

function SceneActivation()
	local lastSceneID_= luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "sl_CentralScene",YourDeviceID_)
	if (lastSceneID_== "1") then
-- 16 is the Vera-ID from scene to execute
		luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",{ SceneNum="16" },0)
	elseif (lastSceneID_== "2") then
-- 15 is the Vera-ID from scene to execute
		luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",{ SceneNum="15" },0)
	end
end