Wink state #3767
Comments
|
Does it then return to the correct status? My setup does the same thing. I turn on a light via the HA front end. The front end switch flips on then off then back on. I read it was because HA must poll the light to get the status change and then updates the front end. |
|
@jsnoop315 Do you have any update on this? Sounds like this may be related to some of the other issues we are having with Wink push updates this is probably happening after HA has been running for awhile? I assume a restart fixes it? |
|
The problem continues on a reboot. I think the problem is related to the iHome smart plug API. Those are the only switches that show the incorrect state. On Wed, Nov 2, 2016 at 8:21 AM -0500, "William Scanlon" notifications@github.com wrote: @jsnoop315 Do you have any update on this? Sounds like this may be related to some of the other issues we are having with Wink push updates this is probably happening after HA has been running for awhile? I assume a restart fixes it? — |
|
Ahhh good to know, probably a bug I don't have any of those and haven't ever seen an API response for one. Any chance you can get a dump of the API json for that device? If so follow the instruction below. copy the contents of this link into a python file and run it http://hastebin.com/ehuduhudap.py it will prompt for your token (the one you are using in your config) and then spit out a data.json file in the same directory as the script. That file will have all of your devices in it. Paste that into https://jsonformatter.curiousconcept.com/ to format it and clean our any personal info, you will want to obfuscate all of the following. lat_lng Then after all of that, post that json here and we can see whats going on hopefully. Indicate the current state of the outlet too. |
|
I'll try and get that to you as soon as I get back. On Wed, Nov 2, 2016 at 9:09 AM -0500, "William Scanlon" notifications@github.com wrote: Ahhh good to know, probably a bug I don't have any of those and haven't ever seen an API response for one. Any chance you can get a dump of the API json for that device? If so follow the instruction below. copy the contents of this link into a python file and run it http://hastebin.com/ehuduhudap.py it will prompt for your token (the one you are using in your config) and then spit out a data.json file in the same directory as the script. That file will have all of your devices in it. Paste that into https://jsonformatter.curiousconcept.com/ to format it and clean our any personal info, you will want to obfuscate all of the following. lat_lng subscribe_key channel Then after all of that, post that json here and we can see whats going on hopefully. Indicate the current state of the outlet too. — |
|
{ ], ]
|
|
@jsnoop315 Thanks for the json, not seeing anything that stands out looks how I would expect any of the binary_switches to look. Do you always see this issue? or just on some state changes? Do you see the state change in HA if you update the state via the official Wink app? Also are you seeing any errors in your log? |
|
Sometimes it does work. I don't receive any error messages. On Wed, Nov 2, 2016 at 5:44 PM -0500, "William Scanlon" notifications@github.com wrote: @jsnoop315 Thanks for the json, not seeing anything that stands out looks how I would expect any of the binary_switches to look. Do you always see this issue? or just on some state changes? Do you see the state change in HA if you update the state via the official Wink app? Also are you seeing any errors in your log? — |
|
Interesting, good to know sounds like there isn't anything we can do about this unfortunately. I ran through the setup for one of those, and it looks like they are connecting it via an iHome account? So it sounds like Wink is accessing some API of theirs did a quick search and didn't see any public API for it. If you continue to have problems and Wink isn't able to resolve this we may be able to come up with some sort of polling only on those specific devices, that way if they don't update properly the state would get corrected on the next polling. |
|
Wink does need my iHome account to add them to my account. The API is not public from what I have seen. Maybe iHome will allow that one day. iHome has branched out and is now working with Alexa and smart things. On Wed, Nov 2, 2016 at 5:59 PM -0500, "William Scanlon" notifications@github.com wrote: Interesting, good to know sounds like there isn't anything we can do about this unfortunately. I ran through the setup for one of those, and it looks like they are connecting it via an iHome account? So it sounds like Wink is accessing some API of theirs did a quick search and didn't see any public API for it. If you continue to have problems and Wink isn't able to resolve this we may be able to come up with some sort of polling only on those specific devices, that way if they don't update properly the state would get corrected on the next polling. — |
|
Are you making a curl command directly to the switch? Or are you using curl On Nov 2, 2016 7:26 PM, "jsnoop315" notifications@github.com wrote:
|
|
The switch is wifi. On Wed, Nov 2, 2016 at 6:34 PM -0500, "William Scanlon" notifications@github.com wrote: Are you making a curl command directly to the switch? Or are you using curl to hit the wink api? Is the switch WiFi? On Nov 2, 2016 7:26 PM, "jsnoop315" notifications@github.com wrote:
— |
|
This is off the original topic but I would like to ask. On Wed, Nov 2, 2016 at 6:34 PM -0500, "William Scanlon" notifications@github.com wrote: Are you making a curl command directly to the switch? Or are you using curl to hit the wink api? Is the switch WiFi? On Nov 2, 2016 7:26 PM, "jsnoop315" notifications@github.com wrote:
— |
|
@jsnoop315 Yeah, off topic. If you have a feature request/question like this you should ask it on the forum. Did a quick search, and it looks like some people are talking about it, for example https://community.home-assistant.io/t/how-to-make-use-of-generic-433mhz-sensors/1215 |
|
@jsnoop315 are you still having trouble with these switches after updating to 0.34.0? If so I think I might be able to implement something that could help. |
|
Yes I am still having trouble with current state.
On Sun, Dec 4, 2016 at 9:38 AM -0600, "William Scanlon" <notifications@github.com> wrote:
@jsnoop315 are you still having trouble with these switches after updating to 0.34.0? If so I think I might be able to implement something that could help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
In 0.34.0 there was a new Wink service added. The next time you see this issue, can you call the |
|
Thanks. I will give that a try and let you know.
On Mon, Dec 5, 2016 at 6:57 AM -0600, "William Scanlon" <notifications@github.com> wrote:
In 0.34.0 there was a new Wink service added. The next time you see this issue, can you call the refresh_state_from_wink service and see if your switch state gets corrected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
The wink switch status had been working since 34.0. However, today it has stopped again. This is normal. So I called the refresh_from_wink_server service but that didn't help. Even if you go to the winkathome website the status is wrong.
On Mon, Dec 5, 2016 at 7:17 AM -0600, "Jody Boudreaux" <jsnoop315@gmail.com> wrote:
Thanks. I will give that a try and let you know.
On Mon, Dec 5, 2016 at 6:57 AM -0600, "William Scanlon" <notifications@github.com> wrote:
In 0.34.0 there was a new Wink service added. The next time you see this issue, can you call the refresh_state_from_wink service and see if your switch state gets corrected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@jsnoop315 that is unfortunate. That really means we are dependent on Wink to correct the issue. Going to go ahead and close this since it isn't any issue we can resolve. Hopefully Wink gets the issue figured out. |
When I turn on a wink switch the switch comes on but the status returns to off
The text was updated successfully, but these errors were encountered: