Amazing. Thank you!!
@EricM_Inovelli Great to hear itās now being worked on! Are you working on it for both multiple taps and press and hold?
I believe it will apply to both scenarios.
Thank you.
I still have 5 more Reds to update.
So that Iām clearā¦
1.48 otz T0 pairs with
1.41 bin T1?
1.48 OTZ to T0; 1.47.bin to T1.
Butā¦
1.47 bin SAYS it is 1.41 bin once installed.
Thatās the source of my original question.
Ahhh got it. Yes, I believe @EricM_Inovelli did confirm that. Maybe the next .bin file will reflect the filename version.
I purchased a refurbished dimmer late December and it came with 1.35ā¦ Am I correct in assuming the only way for me to get 1.48 and Smart Bulb Mode (what I bought it for) is to purchase a USB zwave dongle or a hubitat?
Unless your hub has OTA update abilities youād either need a Z-Wave stick to do it from a computer or if your hub uses a Z-Wave stick rather than the Z-Wave radio integrated inside the hub you can most likely shutdown your hub and pull that stick to use it to update, although if you have a lot of devices connected to the stick it will likely be challenging to identify the device you want to update.
You can still accomplish, āsmart bulb modeā with 1.35. We just made it, āeasierā with 1.48 in that itās just a toggle now (and we tweaked the output setting).
Can you let me know what bulb youāre trying to accomplish this with?
In regards to the refurbished products, we donāt flash them with the latest firmware as that would take forever (thereās only 7 of us, with Courtney being the sole person who checks in refurbs) ā itās about a 5 min procedure (minimum) and there are a ton of refurbs that come in. Itās something we can look at doing in the future.
I understand the work involved with flashing all of the refurbished products and that it would be an arduous task. However, I keep noticing issues with firmware on these switches as if the previous owners caused problems and returned them. For example, the latest one I installed says itās 1.48 but the white LED option displays as red, suggesting the bin wasnāt flashed correctly. Regardless on this, I will probably be picking up a hubitat soon to fix all of this.
To answer your question though in the meantime, theyāre hue bulbs. However, I donāt want to derail the thread topic with my issues.
Which hub are you using and what method are you using to change the LED to white? There was a bug at some point where the driver or device handler was not changing the LED to white. If it isnāt that then it probably didnāt have target 1 flashed with the .bin file during the firmware update.
Iām using Smartthings and Iām using smartthings settings to change it to white. I have other dimmers that this works on, but not on a couple of the refurbished ones I recently purchased. I have a hubitat coming and plan on flashing the new firmware.
Make sure you have the latest device handler. Dated 11/13/20
@EricM_Inovelli Do you have any information on the new firmware file (1.52)? Perhaps a solution for the dimmer level when using smart bulbs?
Ahhhh! I just flashed 1.48 to all of my dimmers tonight!
Edit: Also why is the bin 1.52_1.43
@EricM_Inovelli, so, i am getting this error with the bin file for target 1
2021-01-24 12:20:12.582 am errorjava.net.SocketTimeoutException: Read timed out on line 395 (firmwareStore)
Any idea why I might be getting this. Hubitat C-5
Man, do you have a notification set up when we post something to the firmware site? Lol
It should have the smart bulb fix as well as several other things. I am interested everything yet so that is why I havenāt created a knowledge base article for it.
Hey, not sure. I havenāt tested flashing with hubitat yet. I flashed with PC controller last night.
Thatās classified
Just to confirm, smart bulb mode with this release eliminates the need to disable the bypass? Just configure association and done?
Iām guessing you mean you are still testing. If thatās the case Iāll wait for the KB before testing things.