Wild guess, but most of the time you need a static DHCP address (also Address Reservation or similar) for devices like this. It is probably "forgetting" what the address is when rebooted.
2 Likes
Thanks for your quick response. I though about that but if this would be the case, why the I reboot the relay it does not lose the connection for on and off...... just for the automation ...... wired !!!!
I don't know if I can answer that. But LAN/Wifi devices are funny sometimes. Giving them a static DHCP is one of those things that gives the hub a fighting chance of keeping track of everything.
Oh, and another quick question, you did put your hub on a static DHCP too, right? That is always recommended to prevent issues.
I did not but I am going to try this and let you know .... thanks for the advise .... keep you informed
Believe it or not it was the other way around. I have some of my Wink Relays with Static IP Address and others with dynamic... The ones with static were causing the problem. Now that I removed the static addresses the rules works perfectly, even after rebooting the device...... wired but.....
Thanks a lot because you put me in the right direction.
1 Like
THIS IS A TRANSCRIPT OF A THREAD I STARTED IN THE MAIN GROUP. THE ADMINISTRATORS SUGGESTED MOVING THE DISCUSSION HERE.
Here the original thread
HI there
I have 14 Wink relays connected to Hubitat. They are all working super well.
I just discovered an issue when I setup a rule to disconnect lights after a certain period of time using RM4.0. The issue is that from time to time the Wink relay does not refresh the status and consequently, the rule does not work properly because the system does not realize that this particular switch has been activated. Once I manually refresh, the rule works again.
I have created a rule to refresh the Wink Relay and I have 2 questions:
1.) Taking in to consideration I do not know exactly when the refresh status stop working, can I setup a rule every 10m for instance? Does it affect the performance of the hub at all?
2.) if the above is not an issue, if I setup a rule to update my 14 wink relays every 10m.....is this going to affect the performance of the hub at all?
Many thanks for your help.
Could you post your rule (also not sure what is meant by "disconnect" lights)? I suspect the refresh issue might be fixable in your rule.
@aaiyar I think he is referring to the way a dashboard will not update (on some devices) if the state is changed outside of that dashboard. So if the light is turned off via RM it not display as off unless you manually refresh the dashboard.
@jcastrillo Your Wink Relays run a dashboard right?
Let me know if my assessment is true, and if so we may be able to "refresh" with less work on the hub. I stress the words MAY BE.
Thanks to all and yes @TechMedX you are absolutely right... my state is changed outside the dashboard because this is a manual trigger. I press the button and 20m later the light is off.
I can post the rule but I am not sure how to do it.... I assume you want the rule code and not the screenshot .... right?
Unfortunately I do not think that will change much on the Wink Relay. Try it out, I hope I'm wrong. If not let us know and I will continue the investigation mentioned below.
Pretty sure the problem is not with anything in HE, but the Wink Relay itself. Older devices (one of my iPads does this, and I know of few other members with the same issue) do not update automatically to pull in new "state" changes.
I am not aware of anyway to refresh a HE Dashboard via RM.
You can....
1 - Click the green arrow which will reload that page without going back to HE main Dashboard selection screen.
2 - You can create a "Refresh" button that is a url link back to that same page (just a bigger button)
What I do not know, but think would fix this issue if either were possible...
1 - Add CSS that will trigger a page refresh on the Wink Relay (doubtful)
2 - Edit the HTML Header to add a reload to the page (better chance if we can edit the header somehow)
I am still learning CSS and HTML, as it pertains to HE, so I will need to research and check with those smarter than I to see if we can make this happen. Since more and more Wink users are coming on and this is becoming a bigger issue. I think it warrants some investigation.
If anymore out there knows of a way to automate the refresh of an HE dashboard (not via Kiosk that's cheating!) please let me know.
EDIT: When your Wink Relay says the fan is off, what does the HE device page show, on or off?
The only way around this is to do a periodic refresh() as you initially proposed. There is a Wink Relay specific thread and I suggest you post there - other relay owners may have methods to get around this.
I agree that posting in the Wink Relay thread is a good place to get help with Wink Relay related issues. Other Wink Relay users are in that thread and might have suggestions for you (and as the original device author, I monitor that thread as well).
The refresh() command on the Wink Relay driver does a couple of things. It manually requests an update of each of the states, but it also sets up fresh event subscriptions in case things changed somewhere in the event pipeline.
Specifically, the most common thing this fixes is if your Hubitat hub's local IP address changes. You would really want to make sure your hub has a static IP address though.
How do you get that home screen? The app looks a lot different when I install it.
Share some pictures. What are you seeing?
So I had everything working with Hubitat at one point but then my screen started to act up and would flash every once in a while. So I thought a fresh install would help. But then i tried to factory reset this happened. Where it failed to verify whole-file signature and aborts the installation.
And now I just get a boot loop. is there any way to recover from this or is the device bricked?
I have a picture of the failure but i guess since this is my first post i can't include it.
it is telling me i cant put images in the post.
can i send them to an email or something?
I sent you a PM with my email address. If you want to send them to me, I can post them for you.
Attaching your photos in case anyone else runs into the same problem and needs help...
The first photo is of the update screen and shows that you are on version code 12 (pre 1.0) and shows that version code 14 is available (1.1.0).
If you were already running an older version of the software, you'll need to manually upgrade. The original 1.0 release had a warning in the release notes that show on the update screen. Perhaps I can add this message back, so it's more clear to those who haven't watched this thread closely.
Instructions are included in the bottom of the first post of this thread...
I can't remember if it was this thread or the SmartThings one, but I've seen some posts of people getting stuck in boot loops and getting out of the boot loop.
Here's one of the posts on the SmartThings community where they got their Relay out of a loop:
Thanks! That worked... Sent you one more email with a screenshot. Wondering how you got it to take up the whole screen?
also the full screen mode... maybe i missed an option?
Attaching your photo for others to reference as well...
Did you go through the Wink Relay updates? The updates change the screen density and remove the system bar at the top.
You can find more details on the screen density difference in the sister SmartThings topic (as there are ways to work around that):
ah... so i should just ahead and reload the factory image and sign in this time and do the updates? then root etc? i used you app and disabled the factory software. not sure if there is an easy way to get it back to do the updates now?
hmm... now i can't restore the factory edison.zip or kingroot overwrote it. any suggestions how to go back to factory so I can do the updates?
yeah there is no way i can get the app back to do the updates and the factory reset or factory image flash is not working. maybe add an option to re-enable the wink app after disabling it?
