A transition could be simulated with automation. Simulating a transition for a single light is simple - for a group may be possible. Essential the queue would need to become a priority queue with waits injected at appropriate points. I’ll give this some thought when I have a moment. Right now I want to focus on getting this published via a docker file.
1 Like
I’ve thought about that before, but I’ve realised it was pointless as I’ve moved to dimmable LED bulbs. Even the expensive ones don’t seem to have much ‘graduation’. They dim from around 20% to 35%, then nothing till about 50% to 60% then it’s pretty much 100%. I’ve tried a few now and yet to find one that works as well as the old style bulbs 
I like this quote:
Can I dim any LED bulb?
In a word, no. Dimmable LED bulbs and their non-dimmable counterparts use entirely different componentry, so putting a non-dimmable bulb on a dimmable circuit and expecting it to work is a bit like chucking a toaster into the sea and expecting it to swim – it’s only going to end in crushing disappointment and some seriously damaged electrics.
I agree that LED lights are problematic but the ones I have do work albeit not at the lower brightness settings.
Lightwave also provide a compatibility chart: https://support.lightwaverf.com/hc/en-us/articles/115001925031-LED-compatibility-charts.
This is part of the reason that I have moved over to Hue lights for where I don’t have LightWaveRF.
1 Like
Lol - I like that!
I purchased some cheap dimmable LED candle bulbs from amazon the other day. They were 2w bulbs (x5 in a chandelier) but they simply didn’t work. Not enough load. They also buzzed like crazy too (bulbs not the LWRF dimmer). so they are going back to Amazon.
In this situation, it’s really possible to put Hue bulbs in there as 1. They don’t look as good IMO, and 2. it’s just not as cost effective.
I also have several other lights that require a ‘feature’ too, where LWRF is a better fit.
This is great. Thank you. I have been using IFTTT to get my lightwave to work, but now I have this working, time to switch it all across.
Do you know if you can call Mood settings or the “Home” or “Away” events using this method?
Moods can be supported see (https://api.lightwaverf.com/lighting_power.html). Not sure how to get moods to be reflected back to Home Assistant as scenes.
Added a registration button. This can be used to register and de-register. You will need to update the configuration.yaml file the hide the button after registration.
This should make it easier for those who do not like accessing the shell.
Docker is left to do.
I’ve got this up and running now and firstly I just want to say thank you. It was fairly easy to get going and seems pretty solid from what I’ve used so far.
There’s just a couple of small things I’ve noticed:
1.My lights always seem to turn on at full power, would it be possible to have them remember their previous brightness value and turn on at that?
2. When I drag the brightness slider completely to the left, the light seems to go back to full power, not its lowest brightness value.
Cheers,
Tony
Hey Tony,
Retain last brightness should be trivial to do. I’ll take a look over the weekend.
Drag the brightness slider completely to the left sounds like a bug. I’ve never tested that and can see in the code how this could go wrong.
Cheers,
Geoff
Hey Tony,
Fixed the brightness slider and added the ability to retain the brightness.
Registration of the hub is now automatic. It should have been this first time round. When it tried to talk to the hub and gets a response “Not yet registered” it tries to registered automatically. This should make as you don’t need to modify the configuration file.
Cheers,
Geoff
2 Likes
That’s great, thanks Geoff!
Great work Geoff!
Am I imagining things, or are my lights now taking longer to switch off? My kitchen comprises of 5 switches and 2 dimmable lights. When I click the groups off toggle it takes about 11 seconds for everything to turn on / off.
I’m sure it was quicker before, but may be wrong?!?!?
Hi Martin,
Your observations are probably right. In refactoring for automatic hub registration I introduced an error. While it works it does cause a delay. Essential every request would never complete except with a timeout. The number of retries was set to 15 with a 0.25 second pause between retries.
You are requesting 5 + 2 request => 7 * 15 * 0.25 is 26 seconds so not sure why you are only seeing an 11 second delay?
The good news is I have updated the code. Please let me know if this has got things back on track.
I have also posted the code as a PR on the main HA dev branch, if accepted it will hopefully be incorporated into the main build.
You got a link to the new code? Can only see the one edited 4 days ago.
Sorry - I forgot to push the code to Github. Try again now and it should be there.
1 Like
Awesome - now takes 5 to 6 seconds to turn the kitchen lights on.
Thanks for the confirmation. Unfortunately, while working, I can’t test the times just the code.
The Docker version isn’t done/available yet, is that correct?
The docker version is not done and hopefully will not be required as I am in the process of getting it submitted to the main home-assistant build. Hopefully in the next few updates this will become a first class component like other switches and lights.
https://github.com/home-assistant/home-assistant/pull/18026
2 Likes
Ah, great. Thanks!