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
Iâm very new to Homey Pro so forgive me if I am teaching anyone to âsuck eggsâ but I wanted to use my Gen 2 LW switches to trigger a Flow in Homey, and this works:
How to use a Lightwave Gen 2 multi-click to trigger a Homey Pro Flow
Launch Lightwave (Gen 2) App (Green Background with White Wave)
Click +
Click âLink Connect Series Deviceâ
Click Lighting
Click Dimmer
Name Device âLW Virtual Switchâ
Click Link
Wait until app says âyour device is now linkedâŚâ
Click back arrow, until reach âDoneâ
Click âDoneâ
Device has been created in âdefault roomâ
In Homey Pro
Click +
Choose New Device
Click Lightwave
Click Dimmer
Click Connect
Click Login on API Connection Details
Choose Virtual switch
In LW App
Choose Light Switch
Settings
Multi-press
Add Automation
Button Press
Multi-press (3 or whatever number presses you want)
Action
Set Virtual switch On or Off
Done
1 Like
Welcome and thanks for the tip 
I have just published an new test version that allows the device class for the energy meter to be changed between Sensor, Socket and EV Charger. This allows the device to be clamped around the EV charger feed cable and open the garage door in the new Homey Energy tab.
Is anyone else having to use polling to get updates of dim-level from Lightwave dimmer into Homey flow? The problem started for me a couple of days ago.
I must confess that I only use the On/Off triggers, so I havenât seen an issue.
Do you see any clues in the Log tab of the app settings page?
Try, with the Log Enabled, controlling a dimmer and see what comes up. You could also temporarily enable the Log Webhook option and see if you are getting message.
I have been using your app very successfully for about a year, to integrate my Lightwave switches into my Homey Pro. I only use one Lightwave Virtual device as the interface for the whole house. I have 9 rooms with a Lightwave Dimmer switch in each. Within the Lightwave app, for each room, I have used the multi-press setting to set a particular dim level of the Virtual switch, with 5 up presses and 4 down presses and one long press. So for example in my lounge, which is room 3, pressing and holding the lounge switch will set the dim level of the Virtual Switch to 30%, One UP press to 31%, TWO up presses to 32%, 1 DOWN press to 36%, 4 DOWN presses to 39% and so one for the Kitchen which is room 4 and therefore 1 UP press is 41%
I then use your âThe Dim Level Changedâ card to trigger a Flow uses a simple HomeyScript to parse the 99 Dim Levels into 9 Variables, named after each room which each can have values ranging from U1 to U5 and D1 to D4.
For instance, 3 UP presses of the lounge LW switch, will make Lounge$ = U3 and 4 DOWN presses of my Kitchen LW switch will make Kitchen$ = D4
But in the last two days the âWhen dim level changesâ card has stopped firing my flow. I can see the Virtual Switch level change to 32% when I UP click the lounge switch twice, but the Flow is not triggered. What should happen is that the Dim Level of the VS is reset to 100% three seconds after the Flow is triggered, but the level of the VS remains at 32% because the Flow is not triggering.
Without polling turned on your app has stopped working and with polling on it crashes after a short time. I do hope you can help as this has made all the light switches in my home stop working.
This is the code: a2076a33-6ec4-417a-b135-f06ec32f71b8
