All my wink relays have died a slow death. They started out good, then they would intermittently go into bootloop (either infinite wink boot animation or no animation at all). After some time, the screen’s backlight wouldn’t even turn on after powering the device. Out of 5 or 6 wink relays, only 1 has survived. Curiously, this is the only wink relay where I performed no modifications (custom apps, etc.). I followed the standard procedure for installing this integration, and I am using a standard setup that many people here have succeeded with. My wink relays were older than 3 years at the point of failure, with about a year of the custom integration. I do not believe that this app caused the issue, but a combination of all the load combined (especially kingroot - my pi hole detected and blocked queries to QQ almost every 5 seconds) - killed the relay thermally or with a storage failure. Interestingly, I can’t even access the recovery “BIOS” menu. I am curious if any others have a similar issue.
Therefore, due to the unreliability of the wink relays, I have changed all but one out with tasmotized smart switches. I am thankful for all the work the community and josh have put into this integration, but I guess it’s time for me to leave it.
sorry to resurrect an old thread, but I’m just now installing relays & came across your post, @Abhijeet_Ghosh
on my first root attempt I upgraded the relay from wink before starting the rooting process. the relay was acting wonky within a few hours after completion, and while poking around in terminal emulator I noticed something was creating lots of garbage files throughout the entire filesystem - I was sure that this could eventually cripple the relay (most filenames appeared to be portions of shell commands - but many looked just kinda random).
the first time I tried the factory reset using the relay buttons I couldn’t get into the recovery screen - but after a few tries of pulling the panel off & restarting, I finally got it to load.
so I did a factory reset and rooted again without upgrading, and the relay seems to be running normally now.
you can check out my readme if you want to see my process, at bit.ly/pjhread - relay.zip at bit.ly/pjhpackage contains adb tools package, mrw tools, kingroot, edisonwink from jimpastos, newest stwinkrelay from joshua, nova, dpi changer, chrome, a modified build.prop to restore buttons, & a hosts file to block wink servers.
after blocking the wink servers on both my router and in the relay’s hosts file, I’m having much less corruption - but I’ve still had to wipe chrome’s data nearly every day (I’m now testing some automated reboot/restore routines)
fwiw, I’m using the relays to run actiontiles via chrome
@pathensley Thanks for the tip … I guess this is why all of mine failed. Unfortunately, I’ve tried over and over again reseating the wink relays, and it doesn’t work. I’ve also tried waitin months before reseating them, but it still doesn’t work. I guess they are so crippled that even the power supply is dead…
I had this same issue because I tried to run the smart app in the Simulator on account.smartthings.com. This obviously did not work as the smart app needs to be ran inside the SmartThings App. Since SmartThings classic isn’t working, it needs to run in the new SmartThings App. After some Googling I learned that the new ST app has a developer mode and after enabled you can go under Automations/Add a routine and then you should be able to find the hidden Wink Smart App!
I have rooted wink relay successfully. sTWinkRelay 1.1 is installed and given root permission. SmartApp and both device handlers saved and published. No discovery. Relay and mobile device are on SmartThings Wi-Fi mesh. I uploaded logs and device ID is 9980d168fe5c9841. Any help is appreciated.
Hi Joshua, I’m interested in continuing your project in the new platform.
I am a programmer with experience in web applications and have been interested in automation programming for a while. I have 2 orphan Wink Relays since I moved to SmartThings a couple of years ago and would love to use them as guinea pigs to learn automation programming in the new ST Edge platform. Can you give me some directions on where to start from? Thank you!
Damian
All of the Wink Relay groovy code is open source and available for reference.
For building drivers, you’ll need to ask the broader developer community if you have questions about Edge drivers since the existing DTH code is built on Groovy of course.
The LAN Driver Tutorial is likely a good starting point:
The value of the Wink relay was that it could integrate its own 2 on/off relays with ST (via a Groovy based DTH) and provide a front end for other devices controlled by ST (via a Groovy based SmartApp).
The Edge environment is a replacement for the former - it can provide an interface similar to a DTH for a single (or parent/child) external device. What it can’t do is the SmartApp portion - Edge devices are sandboxed such that they can’t access other devices (such as Zigbee/Zwave/LAN/C2C) that aren’t under a given driver’s control. The Groovy SmartApp arena is being sunset as part of the Edge transition.
So creating an Edge driver for the relays/dimmers in the Wink Relay is possible, but integrating it as a dashboard/portal for the rest of your ST devices isn’t something Edge can do. For that, you’ll need to write an external application using the environment/language of your choice that interacts with the new SmartThings API.
If anyone does get some Edge going for these that’d be awesome. I have 2 that Im hoping to not lose. I only use the switching part of them, so that’d be plenty for me.
Looks like my Wink Relay stopped working about 2-3 weeks ago had this working for a couple years. most likely due to shutting down Groovy IDE? My Wink relay shows connected on the smartthings dashboard but when I tap on either relay the indicate on and off but no response from the device.
