zooz normally sends the file as an attachment and doesn't host the file on a web server..
3 Likes
I was having difficulty creating a Google Drive downloadable link for Inovelli firmware. Came across this service that does it from a shareable link. Google Drive Direct Link Generator
4 Likes
I noticed Eric started including a link in his firmware posts. I just use that.
Not sure if he did it for all though. That’s the dimmer. Maybe he can update the missing links in their posts.
4 Likes
Thanks for this tool. I've done one Inovelli Red SN dimmer and a Black dimmer. Both updates to completion without issue. I did the Red from Inovelli's link and the Black from my Google Drive using the Google Drive Link Generator reference in a preceding post.
1 Like
don’t forget to like the first post if you haven’t already
7 Likes
@bcopeland:
I hit abort process during fragment uploading (because I wanted to turn off debug logging), and got the following:
The errors kept coming until i pulled the airgap on the dimmer (Inovelli Red series).
Everything is fine after the power cycle.
1 Like
Yep.. Abort is quite a destructive process.. You could have disabled debug logging without hitting abort..
The errors you were seeing is because the device was still requesting fragments that the driver no longer had in memory
1 Like
I figured as much, but wanted to report it just in case.
That is good to know about being able to update the logging during the process.
I guess you could add an if (abort) there to ignore the request and avoid the error message, but the device has to be power cycled anyways it looks like, so it is likely a moot point.
Thanks for this tool!
1 Like
There are so many helpful people in this community and the overlapping Inovelli community I have many to thank! There has been progress…
@aaiyar, @bertabcd1234, @bcopeland my driver issues have been resolved. The problem was caused by the addition of "capability ColorControl" in the driver update that Inovelli pushed on 2020-05-05. Removing that solved all issues and I have been able to move forward. Thankfully no form of reset was required! See these for more if anyone else is experiencing this issue:
@jercloud I had the same experience you did regarding an Inovelli LZW30-SN. Performing part of the procedure you outlined way back in this thread successfully got me through the firmware update. It took two tries to "catch" the update at the correct moment for step #5 but on that second try all was smooth.
Another general thing I have noticed (and now I have firmware updated over 20 devices using this excellent driver) is that the driver switchover from the real device handler to the firmware update driver is most successful immediately after a hub reboot. Nearly every time I attempted a firmware update using this driver when my hub had been running for a few hours/days I would get all sorts of confused messages in the logs indicating that my hub thought the old driver was still present. A reboot always cured it and It did not matter whether I switched drivers before or after the reboot.
3 Likes
You must have hit the magic number by now.
4 Likes
He did. I was 101. 
5 Likes
We did it!!!OK time to close this down. Ultimate goal achieved. 
3 Likes
1 Like
I just stopped tracking this thread. My job here is done.
3 Likes
OK - so who won the $25 shopping extravaganza at Breaux Mart? 
2 Likes
Congrats! According to the badges page there is only 1 topic that hit the 100 likes... They need a badge now for 200... then 500... then 1000 at the rate Bryan will be going.
3 Likes
Welcome to Louisiana. We got crawfish boils, Parish beer, and @bcopeland.
4 Likes
