Fair enough… But realize that doing this is actually forcing the state of the lights out of sync with the status stored by the wink hub… until the hub polls the devices for actual status (poll interval is not known… seems to average about 2 minutes)… the Wink API will not send proper notifications until after the devices are properly synced…
The android app will never show the correct icon (except for dimmers, switches, light bulbs and door locks), unless the android app is updated to specifically support the custom deviceTypes that are used to represent the devices attached to the Wink Account. The mobile apps will usually select an appropriate icon to use based on the UPnP services that the device provides.
If the icon, in a browser accessing the UI on the Vera, is incorrect, thats a plugin problem… If the icon in an android/IOS app is incorrect, that is that apps problem.
You will quickly learn that, in home automation with Vera, nothing is EVER unrelated… IE: you make a change to a scene, and then decide to turn a light on… but the light doesn’t turn on… so there is a problem with the light (since it won’t turn on)… But that would be wrong… Changing a scene cause a LuaUPnP reload, so none of your devices will operate until the reload has completed… (yes, a simplistic example, but you get the idea)
IP cameras displayed in the Vera UI are showing the image retrieved from the camera periodically… You also have an H264 stream configured… This stream is causing the error… which is causing excessive network activity… which can cause poor responsiveness… and could cause lost network packets (ie: a missed notification from the Wink API)… Check your camera configuration!!! Your modification to the “unrelated” network settings, may in fact be related.
log?? going back several (or 4 or 5) hours (with a brief description of what you did and when you did it), so we can see what is happening… The problem can’t be solved if we can’t see what is happening leading up to the need to force a LuaUPnP reload.
Of course, the wink hub usually catches up within a minute or so.
OK, so the wrong icon in the android-vera, in my case, is expected. Good to know…
I just meant that the network changes weren’t related to the sync issue since it’s happened both before and after.
It may have caused the camera issue, so I removed it and re-added it. I’m still having issues viewing the camera in some cases…I’ll get to that in a sec.
Sorry, I’ve been tweaking stuff trying to troubleshoot; I’ll get you a fresh log with debug on after the logs rollover tomorrow. (it’s not an emergency)
So, while trouble shooting, I’ve noticed different behavioral differences depending on browser/app:
1: Waterfox browser - After logging in via home.getvera.com I get redirected to .mios.com/www/1.7.1320-en/
Bad icons but vista700 cam works.
2: Chrome browser - After logging in (same) I get redirected to my internal IP 192.168* instead of mios.
Good icons but camera shows “flowplayer” link but never starts camera.
3: Android app (running on desktop emulator) -
Icons are wrong (expected now) and camera stays black and then freezes/crashes vera-app
That’s all I have so far but I have no idea why one browser redirects to mios.com and the other just connects locally…
“Waterfox” is not supported by the mios user interface…
“Chrome” is not supported by the mios user interface…
You are running a VeraEdge on firmware 1.7.1320…
From experience, and various discussions in the forums, Firefox, IE and Safari are the only browsers that actually work with any semblance of reliability.
The v1.7.1320 firmware is also an issue, as there are many reports of bugs and anomolies with this firmware release…
I will not be “upgrading” to this firmware in the near future… I just don’t have the time to deal with firmware problems on top of everything else
[quote=“cybrmage, post:543, topic:185289”]So… I only see three issues…
“Waterfox” is not supported by the mios user interface…
“Chrome” is not supported by the mios user interface…
You are running a VeraEdge on firmware 1.7.1320…
From experience, and various discussions in the forums, Firefox, IE and Safari are the only browsers that actually work with any semblance of reliability.
The v1.7.1320 firmware is also an issue, as there are many reports of bugs and anomolies with this firmware release…
I will not be “upgrading” to this firmware in the near future… I just don’t have the time to deal with firmware problems on top of everything else[/quote]
I had no idea this FW has been buggy, I guess I’ll wait for the next one and see if it’s better. I wouldn’t expect you to have to deal with those kind of fixes.
While waterfox is basically 64bit firefox I guess I’ll have to try the others and run one of those.
Thanks for help…
EDIT:
IE seems to fix the camera and icon issues…the sync thing we can look at tomorrow.
If I use combined mode, and control them by the group, would the group stop working if my internet/wink service goes down? or is the app smart enough to use them to associate the online group with the local devices to control them that way?
Good question. Cybrmage would be better to answer this one. But, from what I understand about Wink’s API…No. Since Wink does the grouping on their API it doesn’t correlate to anything on the plugin. Wink keeps saying that local control is on the way…so hopefully they have a good way of doing this.
Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?
(I’m thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)
[quote=“kenray536”]Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?
(I’m thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)[/quote]
No, but you can setup the Wink hub as a secondary zwave controller and control zwave devices that are connected to Vera through the Wink app.
Can control all Vera scenes and devices if the Wink hub is setup as a secondary controller? For example, I have 2 Wemo devices hooked up through the Wemo Plugin. Would the Wink be able to see them? Or what about my Sonos devices?
[quote=“dubbedout, post:551, topic:185289”][quote=“kenray536”]Are you able to control functions on the Vera through the Wink Hub? For example, would I be able to run a scene that only exists on my Vera on the Wink app?
(I’m thinking this app only works to control devices/scenes paired to the Wink Hub from the Vera, but just wanted to confirm.)[/quote]
No, but you can setup the Wink hub as a secondary zwave controller and control zwave devices that are connected to Vera through the Wink app.
Sent from my iPhone using Tapatalk[/quote]
I just picked up a Wink hub. How do I set it up as a secondary controller?
Or will installing this plugin make it automatically see all of my Vera devices?
I read that a Staples connect user was able to assign commands via a Lutron PICO remote to carry out other system commands. This would be great to set the center button to say a good night button.
Any thoughts in Vera / PLEG on how to get the pico remote buttons to appear as a device in vera? I can see the remote, but not control any of the PICO buttons.
I suspect because it goes through the WINK CONNECT, that is the reason I can noot seem to locate the PICO as a trigger, but I am so new to Wink and the Caseta products in Vera.
[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.
v0.18b99 - August 9, 2015 (manual update only)
– added - limited support for control/status display from mobile apps that use generic serviceid for unknown device support
– added - initial AAU support (upcoming wink native localcontrol interface)
– added - local device control of group devices if Wink API command fails (using Local_Api or AAU if available)
– changed - tweaks to load level calculation for dimmer devices
– added - configured wink device summary on device settings page
– changed - no longer suppress vera device creation for remote pico with no members
@cybrmage - Thought you would be the best person to ask…
[quote=“MrAutomate, post:554, topic:185289”]Wink plug in users:
I read that a Staples connect user was able to assign commands via a Lutron PICO remote to carry out other system commands. This would be great to set the center button to say a good night button.
Any thoughts in Vera / PLEG on how to get the pico remote buttons to appear as a device in vera? I can see the remote, but not control any of the PICO buttons.
I suspect because it goes through the WINK CONNECT, that is the reason I can noot seem to locate the PICO as a trigger, but I am so new to Wink and the Caseta products in Vera.
v0.18b100 - August 9, 2015 (manual update only)
– added - initial support for Wink Shortcuts
A custom scene controller device will be created for each Wink Shortcut. These devices will only allow activation of the Wink Shortcut. Shortcuts must be currently be added or modified via the Wink App.
Shortcut support must be explicitly enabled in the options section of the Wink Connect Device configuration page.
@ cybrmage - That update is definitely cool! , As a Wink Newbie, is there a trick to create a shortcut on the Wink for the center button to trigger a vera event ?
I seem to only be able to create a shortcut that turns a light on or off.
I want to be able to create a vera trigger event when the center button is pushed on the PICO remote. I attached a pdf, showing I was able to create a shortcut, but still not sure how to do what I want, which is when I press the center button on the PICO remote, trigger a vera scene.