The Fibaro presets are a little more advanced than what this device can provide. I would like to do the lightning program, but there seems to be a variable time between colors. Maybe I’ll add a Christmas (Red & Green) program since that holiday is coming up.
2 Likes
Sounds good! We just missed Halloween 
I’ve started playing around with the virtual switch sync last night, I had to create a separate room to dump all the virtual switches in as I have 25 extra devices now
But! I’ve done some preliminary tests and I’m getting closer to what I always wanted to do with my outdoor bulbs! Though did you find if there was any way to run one of the presets at a specific dimmer level?
I’ve got ten H801’s waiting to deploy your code as well, can’t wait to tie it all together!
Good news, I updated to firmware 1.05 and it allows you to choose a brightness level for programs. The bad news is that Aeon totally changed around the config parameters and how they work. I am almost done with a handler upgrade to support the new firmware version.
Regarding cold white, I’ll be adding that in the same update. It appears that adjusting the color temperature level just dims or brightens the bulb. I think that having two level adjustments is confusing so I will just make it possible to switch between warm white and cold white and then you can use the main level slider to adjust the temperature to what you want.
1 Like
I have updated the handler to work with firmware 1.05. It now supports changing the brightness when configuring a custom program. There are also a few other options I have added that are on the first post. I no longer have a 1.04 bulb to test with, so hopefully I didn’t mess things up there.
As of right now, there is a cold white / warm white slider. The first 50% of the slider sets it to cold and the second sets it to warm. You can then use the level slider to adjust it further.
I can always test when I get home because unless ST implemented OTA Z-Wave updates, mine will still be on whatever version I got them with. How did you update yours? Different Z-Wave controller?
I have an Aeon Z-Stick as a secondary controller on my network. The UZB Z-Wave PLUS USB stick by Z-Wave.Me also works for OTA firmware upgrade purposes.
1 Like
Interesting, I’m not seeing any firmware updates available on their site?
1 Like
Oh wow! That’s a great site! Thank you!
Okay, so just tried the new version, it’s really not happy with 1.04 firmware, none of the extra switches work at all and the sync and firmware version listed is very confused so I rolled back. Not sure if you want to separate out the DTH’s to pre 1.04 and post 1.05 as people might get confused with it not working and not many people will have the means to update.
With that being said… I saw that you updated the first post with the new features you added and they look… amazing. So, which USB Z-Wave stick would you recommend 
I was looking at this but I see you mentioned another:
https://www.amazon.com/Aeon-Labs-Aeotec-Z-Wave-Z-Stick/dp/B00X0AWA6E/
Bummer, I’ll have to flash my bulb back to 1.04 to see what the problem is. The handler should work with both versions.
That is the Z-Stick that should work. This will also work, but it is unavailable on Amazon. Perhaps you can find it somewhere else.
Alright, I flashed back to 1.04 and figured out the issue (pretty sure). Firmware should be reporting as 1.04 in the SmartThings App. If it has a random number let me know what it is.
I can give it another go if you’d like but basically the main on/off worked but like the ‘police’ switch just did nothing, the firmware reported as a very high number and it said ‘Pending’ so I went into the settings, changed a colour and saved it. It switched to ‘Synced’ but it still didn’t do anything.
Since the Aeon Z-Wave stick is within $10 of that one, I think I’ll just get that one, especially since you’ve already used it.
Lol, same time post. Okay, just a tick, I’ll switch it now and report back.
Sorry, if you go into preferences on the bulb and then hit done, the firmware version should update.
Gave that a go, still the same, tried again and changed one of the colour settings, hit done, still the same and didn’t change to ‘Pending’.
This is me turning on/off the 1st switch (Fade):
dbcb1f40-141e-4840-bda4-d6eeb59872a2 10:14:47 PM: debug 'BasicReport(value: 10)' parsed to [[name:switch, value:on, descriptionText:Back Door Colour Lantern was turned on, isStateChange:false, displayed:false, linkText:Back Door Colour Lantern], [name:level, value:10, unit:%, isStateChange:false, displayed:false, linkText:Back Door Colour Lantern, descriptionText:Back Door Colour Lantern level is 10%]]
dbcb1f40-141e-4840-bda4-d6eeb59872a2 10:14:47 PM: debug offCmd()
dbcb1f40-141e-4840-bda4-d6eeb59872a2 10:14:23 PM: debug 'BasicReport(value: 10)' parsed to [[name:switch, value:on, descriptionText:Back Door Colour Lantern was turned on, isStateChange:false, displayed:false, linkText:Back Door Colour Lantern], [name:level, value:10, unit:%, isStateChange:false, displayed:false, linkText:Back Door Colour Lantern, descriptionText:Back Door Colour Lantern level is 10%]]
dbcb1f40-141e-4840-bda4-d6eeb59872a2 10:14:21 PM: debug on1()
Can you make sure that you have updated the handler to the latest version? There isn’t anything that would be stopping the firmware from changing to 1.04 unless an error is thrown during the process. Also, I have changed the handler behavior to assume the firmware is 1.04 if it doesn’t know what it is so it should work regardless. Seems like maybe it didn’t get updated.
1 Like
Whoops! My bad, I was silly and hadn’t realised you had updated the DTH on GitHub (I don’t have this in particular synced), just updated it and BOOM! It’s showing 1.04, will have to test tonight though as I am at work.
This needs to be said again, I sincerely appreciate all the work you’ve put into this Eric, you’ve changed this bulb for me from being an nice experiment as an alternative to Philips Hue to, I wouldn’t buy any other RGB bulb.
This bulb has started to randomly turn on by itself for each of the last 4/5 mornings, nobody else? Should I try excluding and re-pairing the device? And rebuilding all the automations?
It could of been since the hub update.