@aaiyar You go to this website and at the bottom click the link to request the firmware update.. It will bring you to their ticket system to create a ticket..
And the firmware updates are pretty safe.. There are crc checksums everywhere..
Whole image crc, compressed area crc, firmware descriptor crc, some other crc in the firmware descriptor, and crc checks on each of the 2,500+ zwave packets... They went a little overboard with the CRCs...
No, there isn't. I've talked to Jasco numerous times about this and each time the response is always the same... It is along the lines that if you find an issue with your device and there is a new firmware they will replace it if it is under warranty. Otherwise, no updates. In fact, I've tried to pull firmware to make my own images from my switches/dimmers in case I could push them to my lower version switches and dimmers and that doesn't seem to work either. I've never been able to pull anything from them.
A long while back I found a web page that outlined the process of soldering wires onto the hardware to get an image but I haven't tried that and I'm not sure where/if I saved the page.
It's one of the reasons I have started buying from companies that release firmware images.
@bcopeland Pretty neat POC you have going on here.
BTW.. To anyone who still thinks HE is under-powered.. This code should prove otherwise..
It downloads a firmware image off the internet in hex format..
Parses it into binary
Runs CRC16 on the whole image
Reads header information
Decompresses the firmware image
Reads the firmware descriptors
Selects the correct firmware update target based on the descriptor and meta data
And then processes 2,500+ requests for individual parts of the firmware and computes a crc16 checksum on each of these packets..
On my production hub... while it's doing other automatons... In fact you can see a stall in the firmware transfer as motion lighting turned off all the lights in the room that I was transferring the image to... The stall is not a slow down.. The spec is designed to pause firmware fragment requests when there is increased activity on the mesh..
There is more than one Mike in these Communities.
I had thought about putting your tag in there and putting a smiley after it but thought perhaps if you were actually rewriting the drives and couldn't spare the time.
Wow man! I can't believe you're working on this! Thanks a ton!
I'm real new here, just got my HE last week, but I am loving it. I've been known to write some code, but haven't done so with my home automation stuff (aside from basic manipulations to ST drivers).
I would not like to get into the Middle of this, but, the Hub is able to be a 'well powered' Home Automation Hub. I think it would be underpowered for tasks like gravity mapping, heat flow analysis etc. It is IO bound, but a lot of THAT is due to the 9.6k half duplex nature of some ZWave devices. The CPU on the other hand, would be doing nothing, really fast. Which, if you can have it be doing something instead, would be done, really fast. If the CPU is 'churning' on a DB retry loop or garbage collection, or any of the other potential problem areas of Java, then that speed/performance is wasted on what looks just like "nothing, really fast".
It's a cool thing to write!
