Thank you let me know if you want me to try anything or send any more logs
One thing which is a very small chance, if you had polling switched on with a large number of devices, it might have been blocking your account due to too many requests.
With polling switched off it will register a Webhook for each capability so you get push notifications. The app restricts the rate at which it registers the Webhooks so it doesnât exceed any rate limits so it can take several minutes to start up, but once itâs running there is very little traffic and itâs response to events is very quick.
Iâve turned off the polling after you asked me to, it is normally off though, only turned it on to see if it would make any difference
1 Like
I have tried the app on my dev Homey and it worked fine. Now gone back to my normal Homey and that is still working as well. So I have no idea why yours is not working. Everything points to it being a bad refresh or access token.
Thank you for looking into it, itâs really strange just gone into the config again and it doesnât have the refresh token displayed so got a new one, put that in went out to test a light, it turned on but didnât register as on, so went back in the token was the old one, so updated it and tested by turning off the same light which worked but again it didnât register it as off, having looked at it again itâs now registered it as off. Make me wonder if there is something with my actual homey
With the number of devices you have, it could take several minutes to register all the Webhooks when you enter a new token. If you monitor the log you will see it registering them, providing it has managed to connect.
Hi Ady, hopefully this support page is still active. Iâm got a problem whereby there is an increasing delay in lights turning on. It doesnât always happen, sometimes they turn on immediately, but the frequency of the problem is getting worse.
Iâm using 3.1.9 of the app and looking at the log there are lots of âConnection Failed: Error: {âmessageâ:âRequest timed outâ}â entries, followed by âRequest retryâ entries. Eventually a connection is made and the command executes as expected. Have tried restarting the app and the LW hub, but made no difference. Doesnât feel like itâs an app problem but any ideas?
Thanks
The app communicates with the Lightwave servers via the internet. The only thing I can think of is an issue with either tour connection or the LW servers. I do occasionally get a 2 to 5 second delay with my extra kitchen lights coming on, but I have never bothered to investigate. I use the notification from the LW dimmer to turn on the other lights.
Ok, thanks Ady
Ady, would it be possible for the app to communicate directly with the Link hub rather than go via servers on the internet?
Not as far as I know. I did ask about that a few years ago, but was told it would be unlikely then.
I had a quick look at the home assistant hub version and it seems at first glance like you give it the ip address of the hub. So may be now possible. Would be a huge improvement not to rely on internet⌠
That looks like the old version that works with the original lw devices.
The HA component that works with the Hub plus also connects via the Internet API.
Ok Ady, thanks anyway
