Open a command prompt as Administrator on your PC and navigate to the C:\ADB folder.
Type adb connect ipaddressofwinkrelay and hit Enter. If this fails to connect, reboot the Wink Relay using the small button at the very bottom and try again once it comes back up.
Once you are connected, type: adb push wink-projectone-release.apk /data/local/tmp
When it completes, open an ADB shell by typing: adb shell
Type SU to elevate your permissions: su Note: You'll need to Allow su to run as root by tapping Allow on the Wink Relay screen after typing this command.
Change your working folder: cd /data/local/tmp
Mount the file system as read and write: mount -o rw,remount /system (Note the space)
Copy the old Wink app to tmp folder and rename it: cp /system/app/wink-projectone-release.apk /data/local/tmp/wink-projectone-release-orig.apk
Remove the old Wink app: rm /system/app/wink-projectone-release.apk
Copy the new Wink app into place of the old one. cp ./wink-projectone-release.apk /system/app/wink-projectone-release.apk
Set permissions on the new Wink app to allow it to work: chmod 644 /system/app/wink-projectone-release.apk
Clean the Dalvik Cache to remove all traces of old app: rm -rf /data/dalvik-cache/*
Exit ADB shell by typing: exit (Note: You may need to type this twice, pressing Enter after each one to get back to the C:\adb prompt)
These steps aren't necessary. When rooting the device, you can stop at step 32.
We end up installing a custom app that replaces the Wink Relay built in app, so the steps you quoted aren't necessary.
Did you see the STWinkRelay app installed in the app drawer of the Wink Relay? If you installed Nova Launcher per step 16 of the linked guide, you should be able to open the app drawer and see the installed app.
The ADB installation approach is also more of an advanced approach. Any reason you didn't just want to install the app from a web browser installed on the Wink Relay (also should have been installed in step 16 of the linked guide)?
Thanks for trying to help.
I completely missed these steps because I could not find "Root Package Disabler (VuDanThanh)"
"33. Open APKPure again and search for Root Package Disabler (VuDanThanh) and install it.
Open Package Disabler, and swipe left to the System category. Scroll down to find the WinkUpgrade (com.wink.winkupgrade) service and check the box. You'll also want to disable the Uber Widget (com.wink.widget.uber) and the Fitbit Widget (com.wink.widget.fitbit)."
I found and downloaded an app called "Disable Application" but when I started it it didn't find the services mentioned in the description (com.wink.winkupgrade etc).
I did all the following steps after.
At "42. Type SU to elevate your permissions: su Note: You'll need to Allow su to run as root by tapping Allow on the Wink Relay screen after typing this command." there was no message on the Relay screen so I couldn't "Allow" anything.
When i reboot the Relay the old Wink app starts automatically.
Just to reiterate, you should stop at step 32. There is no need to install and package disabler, custom patched Wink Relay app, or anything.
All you need is to get the device rooted and then install the custom STWinkRelay app from this thread. The custom STWinkRelay app will handle disabling the built in Wink Relay app and then takes over all the functions.
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.
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.
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.
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.
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.
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.
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?
Another update: Thanks so much for this as it encouraged me to switch from Wink Hub 2 to Hubitat. Although it's not a perfect solution, I now have a system that is almost there. So much so that I've resigned to ditch the relays for Lutron Picos using the button controller. In the future, I will probably implement a SharpTools-based solution for in-depth, visual wall controls.
