@Bry I much prefer the Classic App the Replace isn’t Available in the new app. The actual process is via PC Controller and the V3 ST Hub, I am using the latest version of PC Controller it has nothing to do with either apps.
Basically the second controller is sending the firmware, the ST hub, primary controller, is just the middle man allowing everybody to get along.
Technically I guess its not “ST OTA” but is an OTA solution that I found works. If you read the docs on PC Controller it is quite a powerful tool and you get a better understanding of what is going on in the Z wave network and how to utilize the tools available. ** Use with caution it can also mess with the network if not set right **
1 Like
Well, I have been considering buying a hubitat… but…
FYI - i tried homeseer’s Z-Flash software - which until this point has been a waste of money - and it is still a waste of money - it will not accept the gbl file. Hopefully work still is in progress to get us a .hex file. 
Thanks!
It was working great throughout fri/sat, but yesterday I could not get it to connect. Reset the breaker, fan light was flashing, so I did the pair to module. One flash green on switch, but the fan light continued to pulse, with no control after it stopped. Module is no more than 12-15ft away from switch.
Are you seeing the same problem on the new firmware?, or is what you’re describing different than before?
I have been trying to do the upgrade through @bcopeland’s upgrade driver on Hubitat, but without success. It gets an error at line 461 every time.
[error] java.lang.NullPointerException: Cannot invoke method and() on null object on line 461 (firmwareStore)
Tried multiple times, eventually moved the hub to less than 1ft away from the switch. Did a Z-Wave repair to make sure it was not bouncing everywhere… Still the same error.
Any recommendations? Trying to move the discussion from Hubitat’s forum over to here…
That error is because you are using the old version …
You are going to have to get the new binary compatible version:
The section of code referenced in the error doesn’t exist in the binary compatible version
2 Likes
With the correct Firmware Updater, it works like a charm. Thank you, @bcopeland. @Snell, this solves our problem.
Bryan, fwiw, it looks like there’s a version control ambiguity in the thread you referenced. I’m guessing you were focused on getting the solution out there and not packaging, so no judgment!
Yup, I tried it this morning and it is updating just fine now. Have to give @bcopeland a little grief for not changing his version number in the driver…
1 Like
just got this error
Current States
currentFirmwareVersion : 1.31
manufacturerId : null
firmwareUpdateProgress : FAILED: The device was unable to receive the requested firmware data
firmwareUploadPercent : 15%
firmwareTarget : 0
lockedBy : None
firmwareFragmentSize : 40
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:49:25.894 am [debug](http://10.0.0.203/device/edit/1314)Got request for fragment #:679 packing report and sending
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:49:13.686 am [error](http://10.0.0.203/device/edit/1314)groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Integer#multiply. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] on line 151 (parse)
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:49:13.666 am [debug](http://10.0.0.203/device/edit/1314)Got request for fragment #:679 packing report and sending
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:49:01.460 am [error](http://10.0.0.203/device/edit/1314)groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Integer#multiply. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] on line 151 (parse)
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:49:01.419 am [debug](http://10.0.0.203/device/edit/1314)Got request for fragment #:679 packing report and sending
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:48:49.291 am [debug](http://10.0.0.203/device/edit/1314)locked by:
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:48:49.284 am [warn](http://10.0.0.203/device/edit/1314)ERROR. Device expected an authentication event to enable firmware update
[dev:1314](http://10.0.0.203/logs#dev1314)2020-07-21 11:48:48.585 am [debug](http://10.0.0.203/device/edit/1314)Got request for fragment #:678 packing report and sendingJust installed my fan and had this issue. Everything worked fine until I paired my switch with SmartThings (~30 minutes after install & successful test of functionality from switch). I had to remove the metal dome on the fan and re-set the RF antenna to get it to work. Everything else has been fine so far.
Make/Model: Hunter Exeter 54"
Remote operated
Power to switch
10 foot distance from switch to fan
76F at switch, ~82F at fan
Wireless Router, SmartThings hub both ~8’ from switch, ~10’ from fan
2 Adults in house, average # of devices (2 phones, 2 laptops, 2 tablets, 8 Nest branded products)
Now that everything works, I love it!
1 Like
Can someone that has installed the new beta firmware please provide a status update? @DTrident’s last post indicated there may have still been some type of issues, but that was never clarified or echo’d by anyone else.
@Eric_Inovelli, at this point, is the beta firmware on-track to be released as the official?, or is there another revision in the works?
Seems like there might be another firmware somewhere on the horizon with the same “Disable Physical On/Off Delay” & “Smart Bulb Mode” settings as all the other switches. (But just guessing!)
Just tried the switch 20min ago and it’s still disconnected. Going to remove it from the zwave network and factory reset the switch. Probably will pull down the fan and move where the antenna is.
So you ARE still having disconnect issues with the new firmware?
I have had this software on the three switches running for 6 days without a single disconnection. Previously I would have lost connection ~1-2 per day…
2 Likes
I am in the same boat as lockout. I have not had any disconnects to the canopy for multiple days. I upgraded all 3 switches’ firmware and all have been solid. My finicky one usually disconnects in 1/2 a day and it has now been connected for 5 days without an issue. I’ll report back if I have a disconnect. However this looks to have solved my issue!
3 Likes
Zwave is showing the correct firmware. That’s why I want to start from scratch.
Does an air gap at the switch restore communication, or do you have to pull the breaker to get everything working again?
I still believe that there is a second, less frequent problem with some canopy modules. If an air gap restores the canopy connection, then this firmware (or disabling power monitoring) appears to fix it. If you need to pull the breaker, the problem probably isn’t in the switch…
The switch and the canopy will never reconnect unless you take some sort of action … are you just waiting for it to recover?