Update: Look like for me 0.20.32 broke it… 0.20.26 still OK and after upgrade to 0.20.32, I got the Status Configuring Devices … any click give Device not Ready
Update: The oldest version work as I am rolling back to oldest version I have now is version 0.20.12… I will continue to go slowly up to the latest see what will be the last one that still work.
I have a Vera3 and Wink Connect has been running solid until yesterday. The Wink Connect device is totally broken. Show as “Can’t Find Device” and Wink Status as Configuring Devices. I can’t do anything with it. Everywhere I click, i got Device Not Ready message (can’t go to debug mode to get log either). The only thing changed last week was UI7 latest firmware upgrade to 1.7.760…
I have try
Roll back Vera firmware to 730
Uninstall, reinstall Wink connect
Upgrade/Downgrade to multiple version of Wink Connect…
Nothing work … and Wink Connect keep saying Configuring devices … and Vera give a red “Can’t Find devices”
I did try v0.20.42 and 0.21rc1 and rc3 and all gave me “Can’t Detect Device” and anywhere I click give me “Error Device Not Ready”. It was working a week ago and nothing change in my system accept for adding a Caseta in wall dimmer, a Caseta remote and upgrade UI7 to 760. I can’t go to DEBUG to pull the log either. Any other way to get the log for you? Thanks
[quote=“cybrmage, post:684, topic:185289”]Debug mode is not required.
Please post the standard LuaUPnP.log from the beginning of a reload… (see previous discussions in the thread for info on obtaining logs)[/quote]
Thank you cybrmage… here is the luaUPnP.log in dropbox … I started the new log from the last working version 0.26… Reload lua … upgrade to rc3 … once upgrade completed I reload lua again then refresh browser … I am running UI7 760 on Vera 3
Ok… The plugin is crashing while processing the device list provided by the Wink API… Which means that you have a device that has unexpected data… The device is reporting that it belongs to a hub (Wink Hub, Wink Relay or GE Link Hub), but the Wink API has not provided any data for that hub…
Do you have any devices on your Wink Account that are “shared”?? That is the only situation that I can think of where this could happen… (I have not tested or used shared devices)
I have made some “fail-safe” changes to the code… The attached test file should get the plugin running… and it will provide more information for further debugging.
Do NOT downgrade the plugin… just unzip and upload the attached file (make sure “reload” is checked), wait for the LuaUPnP engine to reload (multiple restarts may occur - this is normal), then capture and post the new LuaUPnP.log.
Thank you cybrmage for looking into this. As soon as you said crash due to device that has unexpected data and a hub causes this crash
I knew exactly which device cause the problem.
It was the Connected by TCP hub. I don’t know how the hub was added to the wink but when visit Wink@Home I can see the dead TCP hub.
once I cleared the dead TCP hub, the plugin came up READY and controllable again.
I’m hoping that someone has some insight on an issue I am having with the Wink Hub Plugin and using Ring with Vera. I’m not sure what I am doing to do is even supposed to be working as designed. I apologize if this has been mentioned before. But I looked at the front page and through this thread and not seeing anything.
To give a brief background on the issue, I have the Wink account only. Only two components connected are the Ring Doorbell and Egg Minder. What I’m trying to accomplish is running scenes on the Vera, dependent on whether there is motion or if someone presses the button to the doorbell. I can already see the devices in Vera once I uploaded v0.20.42 and reloaded luup followed by reloading the browser. I do know the devices match because I called the called the device in Vera Ring DB Button. And that name updated in Wink. I also know that I am looking at the correct devices by looking at the deviceID and what is under the Summary tab.
While I can see the devices in Vera, I just can’t get a simple function to work. I’m trying to run a scene when the doorbell button is being pressed. The scene simply blinks some lights 3 times. I press the doorbell button and get alerts for both the Wink and Ring doorbell app. However, nothing happens in Vera. My lights do not blink. Initially I tried setting this up under Select Scene for Device Buttons. I then tried creating another scene and making the trigger the ring DB button and then run the luup code that has worked for me in the past to blink the lights.
Can the scenes be triggered in Vera based upon what I’m trying to accomplish?
Yes… you should be able to trigger a scene using the Ring Video Doorbell as a trigger.
There are three possible reasons that it doesn’t work…
The data returned by the Wink API has changed.
The plugin is not triggering the scene controller device correctly.
The scene controller device is not configured correctly.
From your description, it sounds like you have tried both ways of configuring the scene controller… so, since I do not have one of these devices, you will need to post your LuaUPnP log so we can see exactly what is happening.
Make sure you turn on DEBUG mode in the plugin, and then reload the LuaUPnP engine… Once the LuaUPNP device has finished reloading and Wink Connect device indicates “Ready”, trigger the doorbell button, then post the LuaUPnP log (make sure you get everything from the plugin startup through to the end of the log)
Thank you for taking a look. Attached is the LuaUPnP log. I reloaded LuaUPnp at 2:45 PM. Pushing the doorbell button occurred at approximately 2:47 PM. Device # is 89.
Edit: Just realized I took out the action for the scene button yesterday. I was trying to troubleshoot to see if that and the triggering scene were conflicting. I placed that back in and LuaUPnp was reloaded around 3:09 PM. Attached as ring_db_test2
Figured it might help to have both case scenarios.
Yes… you should be able to trigger a scene using the Ring Video Doorbell as a trigger.
There are three possible reasons that it doesn’t work…
The data returned by the Wink API has changed.
The plugin is not triggering the scene controller device correctly.
The scene controller device is not configured correctly.
From your description, it sounds like you have tried both ways of configuring the scene controller… so, since I do not have one of these devices, you will need to post your LuaUPnP log so we can see exactly what is happening.
Make sure you turn on DEBUG mode in the plugin, and then reload the LuaUPnP engine… Once the LuaUPNP device has finished reloading and Wink Connect device indicates “Ready”, trigger the doorbell button, then post the LuaUPnP log (make sure you get everything from the plugin startup through to the end of the log)[/quote]
And… I was wrong… There are not 3 possible reasons for it not working… there are 4:
4) The plugin does not subscribe to notifications when there are no hub devices associated to the Wink Account…
Attached is a fix… v0.21rc4
This should fix the subscription problem and get the doorbell button working…
Thanks again for your help.
I uploaded all those files and restarted Luup. After doing so, I’m getting a Startup Lua Failed error. Attaching LuaUPNP.log
Definitely making progress here. But I noticed an issue. If there is motion being detected followed by pressing the button, the scene does not work. The only way I got the scene to work is being really close to the doorbell and press the button. If motion isn’t detected prior to pressing the Ring button, the scene executes. This will end up always being an issue as the Ring Doorbell will always detect motion as the person walks to the doorbell and then presses the button.
If I look at the push notifications in Wink, I see both the motion and the call button press action. In the Vera, I set up a notification for the motion rule and a scene to blink some lights if the button is pressed. This leads me to believe that it isn’t Wink interpreting Ring’s API incorrectly. And when the logic get’s passed to the Plugin, it ignores the button press if motion just happened.
If I’m thinking this through correctly, here are the expected and actual results:
Expected Results: 1) Trigger Scenes based upon motion (if applicable.) 2) Trigger Button Press Scene
Actual Results: 1) Motion works 2) Button scene does not work if there is previous motion
Attached is the LuaPnP.log. I tried the first scenario of having motion followed by the doorbell button at 23:47. And between 23:47 and 23:48 , I executed the doorbell button press with just the button and without motion. Please note that you will see a duplicate event of the first scenario. That’s because the doorbell detection the motion first again. So I had to try again.
[quote=“Rmervine, post:694, topic:185289”]If there is motion being detected followed by pressing the button, the scene does not work. The only way I got the scene to work is being really close to the doorbell and press the button. If motion isn’t detected prior to pressing the Ring button, the scene executes. This will end up always being an issue as the Ring Doorbell will always detect motion as the person walks to the doorbell and then presses the button.
If I look at the push notifications in Wink, I see both the motion and the call button press action. In the Vera, I set up a notification for the motion rule and a scene to blink some lights if the button is pressed. This leads me to believe that it isn’t Wink interpreting Ring’s API incorrectly. And when the logic get’s passed to the Plugin, it ignores the button press if motion just happened.
If I’m thinking this through correctly, here are the expected and actual results:
Expected Results: 1) Trigger Scenes based upon motion (if applicable.) 2) Trigger Button Press Scene
Actual Results: 1) Motion works 2) Button scene does not work if there is previous motion
Attached is the LuaPnP.log. I tried the first scenario of having motion followed by the doorbell button at 23:47. And between 23:47 and 23:48 , I executed the doorbell button press with just the button and without motion. Please note that you will see a duplicate event of the first scenario. That’s because the doorbell detection the motion first again. So I had to try again.[/quote]
This would happen if the notification for motion and button press are combined into a single notification…
I should be able to remedy this… but I may need further logs…
I’ll post an update once I finish going through the log…
And then it determines that the request is for button #1 (needed because the scene code is shared with Pico Remotes) and triggers the scene for button #1.
And the LuaUPnP engine runs the scene named “Test_Blinking”
At this point, the scene is running, and the Wink Connect Plugin has done exactly what it is supposed to do… Trigger a Vera Scene based on the Ring Video Doorbell button press…
And the Wink Connect Plugin finishes it’s processing of the button press portion of the notification data. (irrelevant log data truncated to save space)
50 02/02/16 23:48:15.986 luup_log:86: (Wink_Connect::HUB_DEVICES::findVirtualDeviceByTypeName): Searching for device of type [vDoorbellMotion] with Parent Wink ID [1606]. <0x2da10680>
50 02/02/16 23:48:15.987 luup_log:86: (Wink_Connect::HUB_DEVICES::findVirtualDeviceByTypeName): found device [2]. <0x2da10680>
02 02/02/16 23:48:15.988 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [motion] aVal [TRUE] aTime [1454474866.7375] dVal [] dTime []. <0x2da10680>
02 02/02/16 23:48:15.988 luup_log:86: (Wink_Connect::getLatestUpdatedValue): varName [motion] actual value does exists - Returning actual value [TRUE]. <0x2da10680>
50 02/02/16 23:48:15.989 luup_log:86: (Wink_Connect::setChildVariable) Device [88] SID [urn:micasaverde-com:serviceId:HaDevice1] variable [BatteryLevel] current [100] new [100]. <0x2da10680>
50 02/02/16 23:48:15.990 luup_log:86: (Wink_Connect::setChildVariable) Device [88] SID [urn:micasaverde-com:serviceId:SecuritySensor1] variable [Tripped] current [1] new [1]. <0x2da10680>
50 02/02/16 23:48:15.991 luup_log:86: (Wink_Connect::processDeviceState): deviceProcessed [TRUE]. <0x2da10680>
And here the motion event is detected and the motion sensor device is updated.
From this point on, until the next notification is received, is the LuaUPnP engine doeing processing of the scene…
I agree. I think I overloaded the Vera initially during my testing with having both the scene button and a triggered scene. I done some testing this morning and it seems to be working without an issue. As another note, I tested from my door initially. A more accurate test would be walking up to the door and then pressing the doorbell. There is a greater delay between the motion and the doorbell button. Hence that test works perfectly.It’s safe to say that the fixes resolve the issue with the Ring Doorbell. Thanks again for your help on this.
v0.21.rc6 - February 7, 2016 (manual update only)
– added - updates for Wink API Changes for hub firmware 02.49
– added - Support for LOCAL CONTROL implemented in Wink Hub Firmware 02.49
Do I have to do anything on Vera End or Wink end to enable LOCAL CONTROL? I upgraded my Wink Firmware to 02.49
Wink Connect plug-in Showed WinkHub (REMOTE - AAU) with my local IP
how do I tell if Wink or Wink Connect operate locally?
I have read in Wink FB page from Wink Social Media person that Local Control will be enabled for everyone after deployment of 2.49, so just getting 2.49 does not provide local control for lights.
Does having local lighting control now allow use of Caseta remotes for scenes in Vera, same as if the Hub were rooted with local API?