In your case I think the command would be
adb push C:\adb\wink_manager /sdcard
What should be happening on the Hass.io front end if this is done correctly? I think I have the relay setup correctly but I don’t see any change on my frontend.
You won’t see anything automatically on the frontend. You need to set up mqtt switches.
I don’t recall the topics they send on, but the best way to figure it would would be to subscribe to all topics and start pressing buttons.
How would you go about subscribing to all topics?
Also, should I be seeing anything on the relay to indicate it is connected via mqtt?
Nope, no feedback given on the relay either (maybe in some sort of logs but I never looked)
In the HA frontend go to YOUR_IP/developer-tools/mqtt and subscribe to # that should listen to all channels.
You can tell it’s programmed right by the clicking of the relay when you push the top button (assuming you programmed the ini file that way). Through the wink software I had both buttons programmed as smart buttons so I know the mod worked.
Here’s how I programmed the relay after root.
Download wink_manager and wink_manager.ini (in zip file) from GitHub
Edit wink manager.ini with ip:port address of homeassistant pi
Place wink_manager and wink_manager.ini on C:
adb connect 192.168.1.67
adb push C:\wink_manager /sdcard/
adb push C:\wink_manager.ini /sdcard/
adb shell
su
mount -o remount,rw /system
rm /system/bin/edisonwink
cp /sdcard/wink_manager /system/bin/edisonwink
chmod 755 /system/bin/edisonwink
adb reboot
Would you mind sharing your ini file with us and your switch code from configuration.yaml?
Unfortunately I don’t have any relays anymore so I don’t have a config or an INI anymore.
Hey folks,
So one of my relays stopped working, and now Chrome wont load ‘error parsing’ issue 
Anyone more experienced with Android know what could have happened?
replying to my own question as solved it. I needed Chrome v56 arm apk
That still runs 
I flashed also a relay bought recently.
Everything works great!
I am trying to figure out how to play with the buttons in order to make them work like smart buttons.
When i press the button i get the Button to change from OFF to ON but than stays ON for ever.
Any idea how to automatically revert the state of the Button (it’s a sensor) back to OFF after is turned to ON.
I think you would want to set the flag to 2 for the switch.
It will just send a pressed event via mqtt. You could then use that to trigger whatever automation you wanted.
I set the flag to 2 for the switch.
I use the trigger but it won’t revert to 0 (OFF) so the next time the button is pressed to give again a OFF > ON trigger.
Just the first time is OFF > ON, after the first trigger is always ON.
When you say the button stays on do you mean you have a binary sensor or some sort of switch in HA that is staying on?
Yes I have this sensor:
- platform: mqtt
state_topic: “Andrew_Bedroom_Relay/buttons/0/click/1”
name: “Andrew Bedroom UP Button Click 1”
And when I press the physical button from “unknown” state goes to ON.
If I manually change it to OFF, through Developers/states goes to OFF, otherwise stayes ON for ever.
I made an automation with this sensor and on the end of the automation I send a payload OFF and it’s working but I think it’s not the ideal solution.
Yeah I don’t think you are going to want to use a sensor here.
You should just be able to use the MQTT trigger in an automation.
Then any time that topic has something published you can trigger your automation. Then you can use whatever conditions you need.
Of course what you are doing now sounds like its working, but probably adding an unnecessary entity.
Also the latest chrome version working is V62.
Total Launcher has better icon size for the desktop App shortcuts.
I flashed 12 of them for my home and they are working as a charm!
I haven’t thought it like this, I will have it a try! Thank you!
1 Like
I don’t own any anymore, I am surprised that they are still pushing down the update from their server when you upgrade from the stock image. I expect that will start to fail eventually.