NEW VERSION RELEASED - IN APP MARKETPLACE
v0.19 has been uploaded to the first post in the thread AND the App Marketplace
@ cybrmage - Was that New release in response to my post about the center button, or a different function? Please let me know if the Center button can be used as a trigger. I installed today’s update (not sure what this update changed) , but I still see no way to use the center pico remote button to trigger a vera scend. Thank for any help .
Does anyone know how to use the center pico remote button on vera?
Try reading the ENTIRE first post… AND the link to details for the pico remote (in the update history - specifically for v0.18b90)
@cybrmage- Thanks, so from what I read , it is possible ;D, and (remembering I am just starting out with WINK) it appears I need a rooted WINK HUB, and set it up in local mode.
From what I have read, WINK fixed / patched their systems to prevent rooting. If this is not the most current information I found, can you offer a link to instructions to be able to root a current version of the WINK ?
My WINK software version is 1.10 per the WINK APP.
Appreciate the help!
Thanks
Thank you for all of the hard work that you have put in on this plugin. Great work!
Would it be possible to add the Quirky Nimbus? I’m looking for away to update a dial on the Nimbus when my garage opens and closes. I’m hoping to find a way to set the dial directly via LUA, but just realized that this something your plugin may be handle. Thanks
I do not have a Nimbus, so you would need to provide the LuaUPnP.log showing the complete plugin startup so I can see what can be done.
I just sent you my logs via PM. Please let me know if you would prefer me to deliver them a different way.
Thanks again for looking into supporting the Nimbus!
Nimbus cloud clock support
Since a Nimbus is a display device, with no sensors or controls, a Vera device is NOT created for a Nimbus that is associated with your Wink account.
The support for Nimbus devices is limited to using the Wink Connect device as a command proxy… allowing you to send a dial update to the Nimbus without the requirement of having to use one of the many workarounds (IFTTT channel, android app, etc)
How to use
To update a dial on a Nimbus cloud clock, you trigger a UPnP action on the Wink Connect device:
SID: urn:micasaverde-com:serviceId:Wink_Hub1
ACTION: UpdateNimbusDial
PARAMETERS:
clock_cloud_id = the Nimbus ID
dial_index = the dial to update
Label1 = the text for the first dial label
Label 2 = the text fot the second dial label
dial_rotation = direction of dial pointer rotation: “cw” or “ccw”
dial_scale_type = type of dial scale: “log” or “linear”
dial_min_value = minimum value for the dial pointer value
dial_max_value = maximum value for the dial pointer value
dial_min_position = maximum value for the dial pointer position
dial_max_position = maximum value for the dial pointer position
dial_num_ticks = number of tick on the dial
value = value to set for the dial pointer
position = position to set for the dial pointer
brightness = brightness of the dial backlight: 0 to 100
For convenience, the ID of all Nimbus devices associated with your Wink account are display in the device summary on the Wink Connect device.
To trigger the UPnP action, you can generate an action using lua code or using an http data request:
local Wink_Connect_Device_ID = 1234
local Nimbus_ID = 12345
local Dial_Index = 0 -- can be 0, 1, 2 or 3
local Action_Parameters = {
["cloud_clock_id"] = Nimbus_ID, -- this parameter is REQUIRED
["dial_index"] = Dial_Index, -- this parameter is REQUIRED
["Label1"] = "test1", -- this parameter is REQUIRED
["Label2"] = "test2", -- this parameter is OPTIONAL
["dial_rotation"] = "cw",
["dial_scale_type"] = "linear",
["dial_min_value"] = 0,
["dial_max_value"] = 100,
["dial_min_position"] = 0,
["dial_max_position"] = 360,
["dial_num_ticks"] = 12,
["value"] = 50, -- this parameter is OPTIONAL
["position"] = 180, -- this parameter is OPTIONAL
["brightness"] = 55 -- this parameter is OPTIONAL
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1","UpdateNimbusDial",Action_Parameters,Wink_Connect_Device_ID)http://<IP.OF.VERA>/port_3480/data_request?id=action&DeviceNum=<WINK_CONNECT_PLUGIN_VERA_DEVICE_NUMBER>&serviceId=urn:micasaverde-com:serviceId:Wink_Hub1&action=UpdateNimbusDial&cloud_clock_id=<NIMBUS_ID>&dial_index=<DIAL_INDEX>&Label1=<text for label 1>&Label2=<text for label 2>&dial_rotation=<cw|ccw>&dial_scale_type=<log|linear>&dial_min_value=<integer>&dial_max_value=<integer>&dial_min_position=<integer>&dial_max_position= <integer>&dial_num_ticks=<number of ticks>&value=<dial value>&position=<dial position value>&brightness=<backlight brightness>[ATTACHMENT MOVED TO FIRST POST IN THREAD]
I uploaded the updated files and have tested via LUA. Getting close but not working yet.
- Should the Wink ID be the Vera Device ID? (Mine is 142 for the Wink connect device).
- Also, it looks like the variable “Dial_ID” is never set. Does that need to be set?
Once again thanks for all of your hard work. The log is below from when I tried to run a Scene with LUA code to set the dial.
JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x31225680>
08 08/27/15 10:11:44.385 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x31225680>
08 08/27/15 10:11:44.385 Scene::RunScene running 146 Nimbus Test <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x31225680>
08 08/27/15 10:11:44.386 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x31225680>
01 08/27/15 10:11:44.387 LuaInterface::CallFunction_Job2 device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed (null) with return false <0x31225680>
02 08/27/15 10:11:45.103 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
02 08/27/15 10:11:47.234 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
06 08/27/15 10:11:47.383 Device_Variable::m_szValue_set device: 91 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 0 upnp: 0 v:0xd3b1f0/NONE duplicate:1 <0x2bff3680>
06 08/27/15 10:11:47.383 Device_Variable::m_szValue_set device: 91 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xd3cef0/NONE duplicate:1 <0x2bff3680>
02 08/27/15 10:11:49.386 ZW_Send_Data node 29 NO ROUTE (nil) <0x2c3f3680>
08 08/27/15 10:11:51.948 JobHandler_LuaUPnP::HandleActionRequest device: 138 service: urn:futzle-com:serviceId:WeMo1 action: notifyBinaryState <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=138 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:futzle-com:serviceId:WeMo1 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument action=notifyBinaryState <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument binaryState=0 <0x30825680>
08 08/27/15 10:11:51.949 JobHandler_LuaUPnP::HandleActionRequest argument sid=uuid:010fac0e-1dd2-11b2-9626-dae11ff4ee26 <0x30825680>
06 08/27/15 10:11:51.950 Device_Variable::m_szValue_set device: 138 service: urn:micasaverde-com:serviceId:SecuritySensor1 variable: Tripped was: 0 now: 0 #hooks: 0 upnp: 0 v:0xd3b190/NONE duplicate:0 <0x30825680>
08 08/27/15 10:12:07.700 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x31225680>
08 08/27/15 10:12:07.700 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x31225680>
08 08/27/15 10:12:07.701 Scene::RunScene running 146 Nimbus Test <0x31225680>
08 08/27/15 10:12:07.701 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x31225680>
08 08/27/15 10:12:07.702 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x31225680>
01 08/27/15 10:12:07.703 LuaInterface::CallFunction_Job2 device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed (null) with return false <0x31225680>
01 08/27/15 10:12:10.552 ZWJob_PollNode::ReceivedFrame job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 got FUNC_ID_APPLICATION_COMMAND_HANDLER node info expected 29 got 32 <0x2bff3680>
06 08/27/15 10:12:10.553 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 43.7100 now: 43.7100 #hooks: 0 upnp: 0 v:0xd3c260/NONE duplicate:1 <0x2bff3680>
06 08/27/15 10:12:10.553 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440695470 now: 1440695530 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2bff3680>
02 08/27/15 10:12:11.523 ZWaveSerial::GetFrame 0x2c3f2ef0 timed out now 0 m_listGetFramePending 0 <0x2c3f3680>
02 08/27/15 10:12:11.523 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2c3f3680>
02 08/27/15 10:12:11.524 ZWJob_PollNode::ReturnMessageNotReceived -end- job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 node 29 didn't reply iOK 0 iBadTx 0 iNoReply 1 Abort returned m_iFrameID 0 <0x2c3f3680>
02 08/27/15 10:12:11.524 ZWJob_PollNode::PollFailed job job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:5 node 29 battery 0 <0x2c3f3680>
06 08/27/15 10:12:11.524 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastError was: Poll failed now: Poll failed #hooks: 0 upnp: 0 v:0xf98608/NONE duplicate:1 <0x2c3f3680>
04 08/27/15 10:12:11.526 <0x2c3f3680>
02 08/27/15 10:12:11.526 JobHandler::PurgeCompletedJobs purge job#33 :pollnode #29 dev:91 (0x1238518) N:29 P:100 S:2 pollnode #29 3 cmds status 2 <0x2c3f3680>
08 08/27/15 10:12:11.914 JobHandler_LuaUPnP::HandleActionRequest device: 138 service: urn:futzle-com:serviceId:WeMo1 action: notifyBinaryState <0x30825680>
08 08/27/15 10:12:11.914 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=138 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:futzle-com:serviceId:WeMo1 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument action=notifyBinaryState <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument binaryState=0 <0x30825680>
08 08/27/15 10:12:11.915 JobHandler_LuaUPnP::HandleActionRequest argument sid=uuid:010fac0e-1dd2-11b2-9626-dae11ff4ee26 <0x30825680>Here is the LUA code that I’m using:
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 0 – can be 0, 1, 2 or 3
local Action_Parameters = {
[“cloud_clock_id”] = Nimbus_ID,
[“dial_index”] = Dial_ID,
[“Label1”] = “test1”,
[“Label2”] = “test2”
}
luup.call_action(“urn:micasaverde-com:serviceId:Wink_Hub1”,“UpdateNimbusDial”,Action_Parameters,Wink_Connect_Device_ID)
Yep… Typo… Dial_ID should be Dial_Index…
Yep… Typo… Dial_ID should be Dial_Index…[/quote]
Good news, everything is working great! Great job getting everything working on the first try. This makes the Nimbus a lot more useful as when using it with the Wink app it doesn’t work very well and often doesn’t refresh. With your updates I can now make it my Vera status station! Thanks again for all of the hard work and time spent.
I’m posting the code snippet here for reference for everyone. This changes the 3rd and 4th dials. I’m planning to have these dials show the status of my garage door and alarm. Going to make a scene for each dial and trigger it off of my garage or alarm.
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 2 -- can be 0, 1, 2 or 3
local Action_Parameters = {
["cloud_clock_id"] = Nimbus_ID,
["dial_index"] = Dial_Index,
["Label1"] = "G:OPEN A:OFF",
["Label2"] = "3rd Dial"
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)
Dial_Index = 3;
Action_Parameters = {
["cloud_clock_id"] = Nimbus_ID,
["dial_index"] = Dial_Index,
["Label1"] = "G=OK A=ON",
["Label2"] = "4th Dial"
}
luup.call_action("urn:micasaverde-com:serviceId:Wink_Hub1", "UpdateNimbusDial", Action_Parameters, Wink_Connect_Device_ID)[quote=“kenray536, post:555, topic:185289”][quote=“FOCGreeN, post:360, topic:185289”]I think someone has said this already but I’ll say it again. You can add your vera Z-wave devices to Wink. This includes the Schlage lock.
In vera add a generic device.
In Wink app go to your hub and get into your z-wave options. Select learning mode.
In vera you should see it add. Name it. It will be a scene controller.
Reload vera. After done force close wink app and re-open it.
Devices will slowly start to load in the right places. Next is trial and error because the device will not have names in the Wink App.
My Kwikset lock, lights, t-stats all appear in wink from my vera. They also duplicate in vera from the newly named Wink Connect plugin.[/quote]
Thanks for this post. I was able to add the Vera as a Secondary controller using these instructions. Now all of the lights switch, dimmers, appliance module, and lock Z-wave devices show up on my Wink account and the Wink App. My Alarm, Sonos, Wemo, Harmony and other non-wave devices didn’t show up in the Wink.
I’m enjoying using the wink app to make Scenes aka Robots and running them on the fly. One thing that I always wanted was a quick way to make a scene for my bedroom ceiling to shutoff in X (dynamic) amount of minutes without having to get to a web interface. I’ve also linked the Wink to my Echo. So now some of the devices that I was previously using the Echo-Vera bridge for are being controlled through the Wink. This helped out because I was right at the 28 device limit on the Echo bridge. (I have Harmony Hub, Sonos, lots of switches so the 28 slots fill up fast if you want to voice control everything).
I didn’t actually have to install the plugin to make this work, I was able to just follow the above directions and after a few restarts on the Vera, all devices ended up in my Wink account.[/quote]
I’ve added 3 new Z-wave devices after I already added the Hub. I’m hoping to make these 3 new devices show up in the Wink app but haven’t had any success with trying to repeat this process.
Anyone happen to have any ideas?
Can the same Z-Wave device be paired to more than one controller? I’m tempted to try to manually Pair the new switches with the Wink but I think that would make me lose them in the Vera.
If you add Z-Wave devices to your primary controller (the Vera), they will not automatically show up in the secondary controller (The WInk, or any other secondary controller).
In order to get them to show up on the secondary controller, you must re-add the secondary controller into the primary controller. DO NOT exclude the secondary controller… just re-add the secondary, it will then sync the devices.
TEST VERSION - basic Nimbus cloud clock support
v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness
UPDATED usage information is HERE
If you add Z-Wave devices to your primary controller (the Vera), they will not automatically show up in the secondary controller (The WInk, or any other secondary controller).
In order to get them to show up on the secondary controller, you must re-add the secondary controller into the primary controller. DO NOT exclude the secondary controller… just re-add the secondary, it will then sync the devices.[/quote]
I tried that multi times with no success unfortunately.
I ended up having to exclude it and re-include it. I had to re-setup all of my device names and icons, but luckily I haven’t made many robots or shortcuts so it wasn’t too bad.
Here’s a step by step for future reference.
Excluding the Wink Hub from the Vera (Warning - this will erase all devices, shortcuts, and robots that use the deleted devices)
- Open Wink app and click on Hub and click the “…” sign not he top left. Click on your Hub Name
- New page should pop up with settings. Scroll down and click “Z-Wave controls”.
- At the Vera page Go to Devices–>Add Devices Tab
4)Find Advanced Z-Wave Devices and click on “Add”
5)In top top section there is a button that says “Remove One”. Get the Wink hub and place touching the Vera - Go back to the Vera page and click on “GO”.
- Go back to the Wink app and click “Exclusion Mode”.
- The Vera will process remove the Wink Hub as a Secondary controller and Reload.
Adding the Wink Hub as a Secondary controller for the first time:
1)Go to Devices–>Add Devices Tab
2)Find Advanced Z-Wave Devices and click on “Add”
3) At the new Add Z-Wave Device page go to the bottom Include section.
4) Set “node(s) of type” to “controller”
5) Set “with” to “full power” and hold tight while we get the Wink ready
6) Place the wink controller directly next to the Vera 3 so that they are touching.
7) Open Wink app and click on Hub and click the “…” sign not he top left. Click on your Hub Name
8) New page should pop up with settings. Scroll down and click “Z-Wave controls”.
9) Go back to the Vera page and click on “GO”.
10) Go back to the Wink app and click “Learning Mode”.
11) The two hubs should talk to each other and exchange information.
12) Wait about 10-15 minutes. Forces close the Wink app and re-open it.
13) You should see your devices there. You’ll have to re-name them all. On/Off=Switch Dimmers=Bulb
Notes:
I’ve noticed that sometimes not all of my Vera Z-wave devices are showing up in the Wink app, so I’ve had to repeat this a couple of times.
I also sometimes get an error from the Wink Scene controller in the Vera that says “Failed to Setup Security”. This hasn’t caused any problems though as I can fully control all devices in the Wink app.
[quote=“cybrmage, post:574, topic:185289”]TEST VERSION - basic Nimbus cloud clock support
v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness
UPDATED usage information is HERE[/quote]
Awesome thanks for the update!!! 8)
I’ll test it out later today hopefully.
[quote=“kenray536, post:575, topic:185289”]I’ve noticed that sometimes not all of my Vera Z-wave devices are showing up in the Wink app, so I’ve had to repeat this a couple of times.
I also sometimes get an error from the Wink Scene controller in the Vera that says “Failed to Setup Security”.[/quote]
Some of your Z-Wave device, on the Wink Hub, show as “UNKNOWN DEVICE”… I’m not surprised that unknown, and therefore unsupported, devices don’t show up reliably in the Wink… (Just because the Vera recognizes and supports the device does not mean that the Wink Hub will… Wink Hub Z-Wave support = BAD).
There is no Wink Scene Controller when you are using the Wink API (REMOTE mode)… The only time a Scene Controller is created by the Wink Connect plugin is when you have a rooted Wink Hub AND have the “Support Pico Events” option under “Hub Tools” enabled AND you have Pico remotes paired with your Wink Hub AND you are using LOCAL or COMBINED API mode… Even then, there is NO security setup that the plugin does that can fail…
The “Failed to Setup Security” is a Vera Z-Wave device driver error… The Scene Controller is probably how the Vera Z-Wave driver sees the Wink Hub as a secondary controller… and a “Failed to Setup security” error means that it could not do all of the configuration that is required to properly set up the Wink Hub as a secondary controller… Possibly due to having a Z-Wave door lock device… To get the Wink Hub configured as a secondary controller, you may need to move the Wink Hub and the Vera closer to the door lock to allow the secure connection to be established…
[quote=“cybrmage, post:574, topic:185289”]TEST VERSION - basic Nimbus cloud clock support
v0.19dev11 - August 28, 2015 (Manual update only - EXPERIMENTAL)
- add control of dial pointer position and backlight brightness
UPDATED usage information is HERE[/quote]
Looks like a data type problem with one of the parameters. Here is the log from the latest version. Thanks cybrmage!
08/28/15 15:38:11.313 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x30e7d680>
08 08/28/15 15:38:11.313 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x30e7d680>
08 08/28/15 15:38:11.313 Scene::RunScene running 146 Nimbus Test <0x30e7d680>
08 08/28/15 15:38:11.314 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument value=50 <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument dial_index=3 <0x30e7d680>
08 08/28/15 15:38:11.315 JobHandler_LuaUPnP::HandleActionRequest argument position=180 <0x30e7d680>
08 08/28/15 15:38:11.320 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x30e7d680>
08 08/28/15 15:38:11.321 JobHandler_LuaUPnP::HandleActionRequest argument brightness=20 <0x30e7d680>
08 08/28/15 15:38:11.321 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x30e7d680>
08 08/28/15 15:38:11.322 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x30e7d680>
01 08/28/15 15:38:11.326 LuaInterface::CallFunction_Job device 142 function SWinkHub1_Wink_Hub1_UpdateNimbusDial_run failed [string "-- Wink_Connect 0.19dev11..."]:8875: bad argument #2 to 'tonumber' (integer expected, got boolean) <0x30e7d680>
Give this a try 8-}
[ATTACHMENT SUPERCEDED]
Give this a try 8-}[/quote]
Ran the code but doesn’t have an effect.
Here is the exact code from the LUA section:
local Wink_Connect_Device_ID = 142
local Nimbus_ID = 13997
local Dial_Index = 3 – can be 0, 1, 2 or 3
local Action_Parameters = {
[“cloud_clock_id”] = Nimbus_ID, – this parameter is REQUIRED
[“dial_index”] = Dial_Index, – this parameter is REQUIRED
[“Label1”] = “test1”, – this parameter is REQUIRED
[“Label2”] = “test2”, – this parameter is OPTIONAL
[“dial_config”] = { – this parameter/sub-parameters is OPTIONAL
[“rotation”] = “cw”,
[“scale_type”] = “linear”,
[“min_value”] = 0,
[“max_value”] = 100,
[“min_position”] = 0,
[“max_position”] = 360,
[“num_ticks”] = 12
},
[“value”] = 50, – this parameter is OPTIONAL
[“position”] = 180, – this parameter is OPTIONAL
[“brightness”] = 20 – this parameter is OPTIONAL
}
luup.call_action(“urn:micasaverde-com:serviceId:Wink_Hub1”,“UpdateNimbusDial”,Action_Parameters,Wink_Connect_Device_ID)
08 08/28/15 19:41:46.758 JobHandler_LuaUPnP::HandleActionRequest device: 0 service: urn:micasaverde-com:serviceId:HomeAutomationGateway1 action: RunScene <0x30a16680>
08 08/28/15 19:41:46.759 JobHandler_LuaUPnP::HandleActionRequest argument SceneNum=146 <0x30a16680>
08 08/28/15 19:41:46.759 Scene::RunScene running 146 Nimbus Test <0x30a16680>
08 08/28/15 19:41:46.760 JobHandler_LuaUPnP::HandleActionRequest device: 142 service: urn:micasaverde-com:serviceId:Wink_Hub1 action: UpdateNimbusDial <0x30a16680>
08 08/28/15 19:41:46.760 JobHandler_LuaUPnP::HandleActionRequest argument value=50 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument dial_index=3 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument position=180 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument Label1=test1 <0x30a16680>
08 08/28/15 19:41:46.761 JobHandler_LuaUPnP::HandleActionRequest argument brightness=20 <0x30a16680>
08 08/28/15 19:41:46.762 JobHandler_LuaUPnP::HandleActionRequest argument cloud_clock_id=13997 <0x30a16680>
08 08/28/15 19:41:46.762 JobHandler_LuaUPnP::HandleActionRequest argument Label2=test2 <0x30a16680>
06 08/28/15 19:41:59.152 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: Status was: 1 now: 1 #hooks: 0 upnp: 0 v:0x1055cf8/NONE duplicate:1 <0x2c3b3680>
06 08/28/15 19:41:59.153 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: StatusText was: Running now: Running #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2c3b3680>
06 08/28/15 19:41:59.155 Device_Variable::m_szValue_set device: 39 service: urn:futzle-com:serviceId:UPnPProxy1 variable: API was: 3 now: 3 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2c3b3680>
02 08/28/15 19:42:00.102 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
02 08/28/15 19:42:02.227 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:02.358 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 1 upnp: 0 v:0xff2480/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:02.358 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xff24c0/NONE duplicate:1 <0x2b9b3680>
02 08/28/15 19:42:04.360 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:04.496 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 44.5110 now: 44.5110 #hooks: 0 upnp: 0 v:0xff1e30/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:04.497 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440816082 now: 1440816124 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>
02 08/28/15 19:42:06.513 ZW_Send_Data node 32 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:06.646 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 0 now: 0 #hooks: 1 upnp: 0 v:0xff2480/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:06.646 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: ActualUsage was: 1 now: 1 #hooks: 0 upnp: 0 v:0xff24c0/NONE duplicate:1 <0x2b9b3680>
04 08/28/15 19:42:06.648 <0x2b9b3680>
01 08/28/15 19:42:22.101 lu_io_connected 0x1b746e8 args 0 0xfb90e8 <0x2f816680>
06 08/28/15 19:42:22.966 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWH was: 44.5110 now: 44.5110 #hooks: 0 upnp: 0 v:0xff1e30/NONE duplicate:1 <0x2b9b3680>
06 08/28/15 19:42:22.967 Device_Variable::m_szValue_set device: 129 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: KWHReading was: 1440816124 now: 1440816142 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>
02 08/28/15 19:42:30.103 ZW_Send_Data node 33 NO ROUTE (nil) <0x2bbb3680>
02 08/28/15 19:42:32.948 ZW_Send_Data node 33 NO ROUTE (nil) <0x2bbb3680>
06 08/28/15 19:42:33.086 Device_Variable::m_szValue_set device: 130 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 41 now: 42 #hooks: 0 upnp: 0 v:0xff2480/NONE duplicate:0 <0x2b9b3680>
06 08/28/15 19:42:33.087 Device_Variable::m_szValue_set device: 130 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 41,41,41,1440815400,1 now: 42,41,42,1440816153,754 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2b9b3680>