[Beta] Wink Relay - LAN Integration

community_app
community_driver

#63

I haven't used my Wink Relays in quite a while, but when I was using them I just had a browser loaded with my preferred dashboard running.

One thing to note is that these are already pretty resource starved devices, so if STWinkRelay app in running in the background and the dashboard starts taking up too many resources, the Android OS might kill the STWinkRelay app.

I ended up switching over to a wall mounted tablet running my SharpTools.io dashboard:

image


#64

Wow, that’s fancy! I would consider doing that but I love the simplicity of the Relay, a small screen I can show some soft buttons and maybe weather m, and two physical buttons I can link to any rule.

At some point, I may have to lose the Relays (4 of them) though. Hopefully they remain stable in this configuration. I have one that might be “losing its connection” despite being on WiFi, it at times seems to not be able to communicate to Hubitat requiring a reset.

The other 3 are blazingly responsive!


#66

Hi again. I'm loving this integration. I'm noticing in the logs a search every 5 minutes for the relays. Maybe to update their status or IPs or whatever. Is it necessary? I see the system logs and because I have 4 relays, it checks 4 times simultaneously. The system events is purely this "urn:sharptools-io:device:WinkRelay:1" x4 every five minutes or so.


#67

Yes, the SSDP discovery occurs every 5 minutes to keep the device information in sync (starting at
this line it checks to see if you already have the device in your list and if it's already setup as a child device and the data doesn't match, it synchronizes it).

If it's just console logging you don't like, you could comment out the log.debug statements as you see fit.

If it's the actual SSDP discovery you don't like and you have fixed IP addresses on all your Wink Relays, you could always comment out the line that schedules the ssdpDiscovery.


#68

Thank you! I was able to comment out the scheduling of the discovery. I have all my relays on static IPs.


#69

Sorry, it's me again. I am noticing, and haven't figured out why, that the Relays will sometimes freeze up and become unresponsive requiring a reset. I'm wondering if it's because I'm not doing the discovery step anymore. Is there anything I can uninstall from the rooting process that might be contributing to this?

Regarding the SSDP discovery, is it supposed to run once for each relay I have? I would think it would just run once regardless of how many I have but it does it 4 times simultaneously.

Thanks for all you've done!


#70

As noted above, make sure to stop at step 32. No need to install the package disabler, custom patched Wink Relay app, or any of that. The link to the Wiki article was just intended a reference on how to root.

The Wink Relays are not the most powerful device, so it's not too surprising to me. Out of the box, they are stripped down and locked to just running the Wink Relay app and they seem to do a decent job of it.

Not doing the discovery shouldn't cause any performance issues on the Wink Relay itself. That discovery just sends an SSDP packet that the custom STWinkRelay responds to for discovery/setup purposes.

Not sure if you are running dashboards or anything else on them at the same time, but anything else that's loaded on them beyond the core rooting and STWinkRelay app puts additional load on them.


#71

Thanks. I restored them to factory. Followed the rooting steps to 32. Then installed the STWinkRelay app. Nothing else is running on them. I do load the STWinkRelay app after it loads up though just so there’s something on the screen.

I thought maybe a periodic ping from the hub would keep it alive or something. I can’t tell what happened after it freezes up, ie the screen won’t come on unless I reset it.

Any reason to delete KingRoot after it’s rooted?

Thanks again!