So I got a reply from Homeseer. I did look at their downloads page on my phone and didn't see the opportunity to download firmware. However, on my MacBook Pro I can see the firmware downloads available here (Smart Home Automation Software Downloads | HomeSeer). They are GBL files... I'm assuming that works with a C-7 hub? I have a new C-7 I plan on using to replace my C-5, but I hadn't gotten around to doing it yet. I guess now I have some motivation...
1 Like
Unfortunately, as @bertabcd1234 indicated, and their website states (see below), these are encrypted files that can be applied using their Z-Flash software .....
Just got a reply from Homeseer again with my question about using Hubitat... here's what they say:
"Matt Cave commented:
Most automation systems do not allow for firmware updates which is why there is a message regarding using HS4 or Z-Flash. If your system supports GBL files, you will be able to use the GBL file for your WX300. Note that if you run into any questions or issues with that process, you will want to reach out to Hubitat for assistance as I have not performed a firmware update for a device in that system."
1 Like
That's good news.
I think this should also work on the C-5 with the binary z-wave firmware updater from @bcopeland.
Perfect! I missed that and was thinking GBL files were only for the C-7. I'll get on that and let you all know how it goes.
1 Like
From the original thread for @bcopeland's firmware updater tool:
Here's the GitHub link to the binary updater:
1 Like
Well, I'll be. The update is a standard .GBL file, which I was able to apply using Hubitat, and it's available for download in their website (above). I'm not sure how HomeSeer's "smart bulb mode" is supposed to work, but I'll look that up later. I'm just in shock that they finally listened. 
(And that the updates aren't encrypted!)
3 Likes
So I was able to run the update using my C-5 hub, but the status seems to be stuck on " Complete device is flashing". Any suggestions on how to get it off of that?
With the driver-based updater, I think that just means it's done.
1 Like
I also think that means it is done. I cannot recall if it has a cleanup button? But you should be able to switch back to the normal driver and see if the device responds, may need to press configure.
If there is any leftover states or junk from the firmware driver you can switch to type "Device" and it has some clean up button to delete junk.
1 Like
Hmm… I switched to the Homeseer driver, and it still showed the status. I also tried hitting configure with no luck. I finally decided to restart the hub, and that status disappeared, but it still says I’m on firmware 1.13 instead of 1.13.6 (I believe).
I’ll try your suggestion here when I get home tonight. The device works, responds, and even flashed on and off during the update process last night.
The cleanup on the "Device" driver wont fix the firmware version, but POSSIBLY if you press "Get Info" with that driver it might check the version, I cannot recall if it does or not.
What is probably happening, is the firmware is updated but the driver you are using is not requesting the version info from the device. If the driver has a Refresh or Initialize buttons that may force it to check the version.
Also, the new feature is probably a parameter setting, and the driver you use probably does not have support for it. So you may need to use something like the "Basic Z-Wave Tool" (custom example driver that Hubitat posted a while back) to manually set the parameter.
I was on 1.12 before, which is what mine came from the factory with when it was new. My current version reports as 1.13, which I believe is current. I don't think Z-Wave has the ability to report three sets of version numbers. HomeSeer's parameter documentation (they added a couple more in this update too, it seems) also only mention 1.12 and 1.13.
So...probably all good.
Duh good point, yes the ZWave firmware reports only have version and subversion, there is no third level. Knowing that they really should have just called it 1.14
I think this might be common practice internally; they could have tested 1.13.1, 13.1.2, and so on before releasing the final 1.13.6 for public use. This is how it's worked with a vendor I beta tested (private) firmware for recently. I know other vendors also just increase the subversion for all betas, too (presumably why their firmware version history isn't all sequential numbers). In either case, it's normally not confusing since by the time it goes public, there's only one version/subversion to worry about.
As far as I can tell, they've also only said "1.13" publicly (that's how it's listed on the download page and docs), so anything more is probably us just inferring things from filenames. 
That is super helpful!! I should have written down my firmware version ahead of time… I was just thinking to look for the “.6” at the end. Thank you all for your input with this.
One last question about the parameter to turn off the relay. Can I use the Basic Z-Wave Tool driver to set it to always on and then switch it back to the normal driver? Or do I need to keep it on the Basic Z-Wave Tool one? I’ve not used that one before but figure I can figure it out with some digging!
You can use the Basic Z-Wave Tool driver to set the parameter, then switch the driver back. You pretty much have to, since Basic Z-Wave Tool doesn't really allow regular use of the device (only its special commands). Some drivers might overwrite something you do with the Basic Z-Wave Tool, but that's not likely unless the driver knows about a parameter and needs it set a certain way to make the device work how the driver expects. I would still avoid hitting "Configure" after you switch back, despite the regular advice--no real reason to when all should be set already if you were using this driver previously.
I will also update my custom driver with the new parameters as soon as I get a chance to test things out.
This worked perfectly! Thank you so much for that suggestion!
Yes - I was able to look up the proper parameters from Homeseer's web site to get it working properly - the button doesn't cut power to the attached light.
I have your latest version up and running. I'll watch for you to update the driver when you have time.
Everyone: thank you so much for all of your help!! I am so glad to have this up and going.
Just released an update for my driver in the other thread if you're still interested in using that! Should support all new parameters for the switch and dimmer, except the "don't flash switch vs. dimmer mode on startup" option that was introduced (I can't imagine many people would disconnect power from their switches often enough to have a preference and might actually like to see it, the default, if it happens...but it can still manually be set via the Set Config Parameter command if really needed).
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
