Ok did this (deleted switch; changed ‘true’ to ‘false’ and saved/published in handler; re-installed) and i see all 3 now but the switches appear to have no functionality - they only show a cloud with a line through it…
@mikeyut3 In that case, you might want to change it back to true, delete and re-add the devices, and use the smart lighting smartapp to link it to virtual switches. The smart lighting smartapp shows the individual switches, even when the main app and automations tab do not.
But i only want to use the smartthings as it has all my other items!
Is there no fix or solution for this in the smartthings app or with the code?
We’re so close to give up now!
Thx for all this help!
-
After doing this, you will get separate switches in smartthings. Its just that the automations that allow those switches to run don’t use the SmartThings cloud automations
-
The smart lighting smartapp can be found under the smart apps section of the smartthings app. There, you can create an automation linking a virtual switch to a single switch of the wink relay. Then, you can use normal automations and the SmartThings dashboard to control that virtual switch. When the virtual switch is toggled, it instantaneously triggers the smart lighting automation, which then turns off the wink relay.
-
All you have to do is to create two virtual switches, create 2 automations in smart lighting, and bam, it will work just like it would if you set isComponent to false, except the weird no cloud errors will not be there
2 Likes
super helpful…got it!
1 Like
One last one from me (I hope). Everything now seems to be working flawlessly other than the actual physical bottom bottom. When pressed, the screen says the bottom button pressed (with words) but it does not do anything nor does it flip the lcd button to on or off. The top physical button works just fine. And the lcd buttons work just fine.
Thx!!
@mikeyut3 On the wink relay’s screen, open the STWinkRelay app and go to settings in the app. You should see a menu called button mapping. Make sure button 1 is mapped to switch 1 and button 2 is mapped to switch 2
1 Like
Amazing! Perfect. Thanks for helping those of us out that are way less technologically sophisticated!
2 Likes
@mikeyut3 your welcome!
Anyone else have their relay display a much higher temp than reality? Mine is displaying 76+ which is a 0% chance of accurate (given its been 30-35 degrees outside here and I set my thermostats to 70-72). I have put temp readers nearby the relay to check and they consistently read 69-70 which makes sense. Also my honeywell thermostats throughout the house read 68-71.
So its pretty clear the relay is displaying (or reading) inaccurately…
can anyone get this to work now? or provide APKS to get it to loads, i can’t find any of the older apps to load anything, any help would be great.
That is amazing…I have spent hours reading all of these threads and have no luck. Wish I could just send them to you to set up 
@Abhijeet_Ghosh DUDE. I spent hours today bashing my head against a wall trying to get KingRoot to work. Countless versions, wiped the device, everything I could think of and I totally wasn’t thinking about my PiHole blocking it! THANKS!!!
@Toasty If you notice on your pi hole console you get tons of denied requests to qq.com? It seems a bit fishy and I think it is a good idea to keep pi hole blocking on as long as you are not actively rooting the device. Once it has downloaded the root strategy, it should not (and from my experience, it does not) need to ping servers after that.
1 Like
good to know, but I am also attempting to replace kingroot with SuperSu for this very reason. Abhijeet_Ghosh I have successfully removed KingRoot for SuperSu… shouldn’t have any rogue network activity any longer!
2 Likes
at @Abhijeet_Ghosh’s warning about odd traffic on the network after installing KingRoot, I went about replacing KingRoot with SuperSu (Typically seen as the defacto standard Root Manager app, no weird network traffic there) - I found this web page: How to Replace Kingroot With SuperSU in Android | TechinReview I used option 2, after number 1 did not. I did have to tweak it just a bit, here’s my steps:
1 Go to APKPure site, search Terminal Emulator in search bar. I picked the first result, install this app on your Android Device.
2 Now Download Replace Kingroot with SuperSU Zip file and than extract it with the help of any extractor app. and than extract it with the help of any extractor app. (I use Explorer app, from APKPure, but any zip extractor app will do.
3 Next, -here’s where I had to change a bit. After extracting the downloaded zip (it should extract to it’s own separate sub-folder “mrw”) - That folder needs to be moved to /sdcard folder (off of the root /) - easily done with any file manager app, like Explorer.
4 Open the Terminal Emulator and enter SU command in it.
It will ask for root permission from you. Allow it. After that you will have to enter second command “sh /sdcard/mrw/root.sh”.
An error will be displayed on the screen, just ignore it and move further. Wait for some time to let it run some processes. (including more errors) It will automatically open the SuperSU App. If it does not open SuperSU App, run it manually from your device. (I did not have to do this)
Tap Continue to update binaries and select Normal Mode.
5 At Last, reboot your android device to finish this process.
KingRoot should be gone, replaced by SuperSu. I also then, downloaded the newest SuperSu APK from ApkPure, launched it and updated binaries again, and rebooted the Relay.
Alright. Maybe I was to tired to figure out what I wasn’t doing right last night after fixing SuperSu root. But I have the Relay visible in ST app, and set up the smart lighting automations, so tapping the buttons on the Relay screen or the virtual switches in ST work to control the load relays inside the Relay… But I can’t find anything in ST that would let me assign the physical buttons on the Relay to an action, and yes I do have them both set to do nothing (event only). What am I missing? @joshua_lyon
Edit: alright, so WebCore does let me choose the Top button or Bottom button state to monitor for changes, but it doesn’t seem to have any capabilities to actually compare against. No “pushed” or “on” “off” etc. So the only comparison I can seem to do is watch for state change and then toggle something on/off. Should there be other available switch states available ?
1 Like
First thanks to Joshua for all the work on this, I am a late Wink cast off, with pretty limited abilities. I got as far as discovery and when I try to save I get an error.
Make sure to save the SmartApp under SmartApps and the device handler under Device Handlers.
Hello Joshua! I am very glad to have found this thread and also I am planning to support you by getting a tablet and getting the other interface you have develop! Amazing work. As I have a Wink Relay, I want to confirm that all of the current instructions and installers are updated and summarized in the very first thread? As I been reading these posts, I can see the evolution that has happen and also the series of enhancements. I want to ensure if I need to go thru the complete 698 replies to ensure I am not missing anything important in this process. Thanks in advance for the confirmation if all latest installers and instructions are in the first message (Subject) of this discussion. Thanks!