How to load older FW version

Discussions about Z-Way software and Z-Wave technology in general
Pmant
Posts: 4
Joined: 12 May 2017 14:58

Re: How to load older FW version

Post by Pmant » 12 May 2017 15:01

Willem_K wrote:After upgrade of my UZB to firmware 5.07 it is not working anymore, the stick is recognised but adding nodes is not possible, it causes a crash and I have to a restart it. What can I do to 'revive' it?
Same here, Stick seems to crash and reboot everytime I want to add a node or do something else with it. It also crashes randomly when doing nothing. Tested on windows pc and Raspberry PI.

Pmant
Posts: 4
Joined: 12 May 2017 14:58

Re: How to load older FW version

Post by Pmant » 15 May 2017 03:03

Now I can't update the firmware at all, the request to your update server gives this response:

Code: Select all

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') AND (type != 'bootloader' OR targetBootloaderCRC != ) AND enabled = 'enabled' ' at line 1
https://service.z-wave.me/expertui/uzb/ ... ionMinor=7

User avatar
Z-Wave Support
Posts: 230
Joined: 21 Oct 2016 15:49

Re: How to load older FW version

Post by Z-Wave Support » 15 May 2017 10:10

Hello,

The problem is under investigation.

Z-Wave Support

User avatar
PoltoS
Posts: 3732
Joined: 26 Jan 2011 19:36

Re: How to load older FW version

Post by PoltoS » 15 May 2017 11:48

The problem with update server was fixed. Thanks for pointing to it

User avatar
PoltoS
Posts: 3732
Joined: 26 Jan 2011 19:36

Re: How to load older FW version

Post by PoltoS » 15 May 2017 11:51

Could yu give us more info. log, controller info page screenshot, detailed description what do you mean by dongle crash

Pmant
Posts: 4
Joined: 12 May 2017 14:58

Re: How to load older FW version

Post by Pmant » 15 May 2017 15:21

Answering the Support Mail: I had to switch back to EU frequency after the Update to "Update firmware to 2 channels (EU/RU/US/ANZ/MY/IL/..) on 05.07". I think it was on "JP" which seems to be the other firmware option.
Also I noticed when upgrading to "Update firmware to 2 channels (EU/RU/US/ANZ/MY/IL/..) on 05.07" both upgrade buttons started the upgrade animation. And the Server returns the same fileURL for both options (2 and 3 Channel):

Code: Select all

{
   "data":[
      {
         "id":"98",
         "baseid":"",
         "enabled":"enabled",
         "type":"bootloader",
         "file":"bin",
         "vendorID":"277",
         "bootloaderCRC":null,
         "appVersionMajor":"5",
         "appVersionMinor":"7",
         "targetBootloaderCRC":"29304",
         "targetAppVersionMajor":null,
         "targetAppVersionMinor":null,
         "fileURL":"bootloader_UZB_from_05_07_to_7278_2MB.bin",
         "released":"2017-05-12",
         "comment":"Update bootloader to 7278",
         "position":"72",
         "version":"5.7"
      },
      {
         "id":"88",
         "baseid":"",
         "enabled":"enabled",
         "type":"firmware",
         "file":"bin",
         "vendorID":"277",
         "bootloaderCRC":null,
         "appVersionMajor":"5",
         "appVersionMinor":"7",
         "targetBootloaderCRC":null,
         "targetAppVersionMajor":"5",
         "targetAppVersionMinor":"7",
         "fileURL":"UPD_FIRMWARE_UZB500_X_from05_07_to_UZB500_3CH_05_07.bin",
         "released":"2017-04-18",
         "comment":"Update firmware to 3 channels (JP\/TW\/KR\/SG) on 5.07",
         "position":"57",
         "version":"5.7"
      },
      {
         "id":"89",
         "baseid":"",
         "enabled":"enabled",
         "type":"firmware",
         "file":"bin",
         "vendorID":"277",
         "bootloaderCRC":null,
         "appVersionMajor":"5",
         "appVersionMinor":"7",
         "targetBootloaderCRC":null,
         "targetAppVersionMajor":"5",
         "targetAppVersionMinor":"7",
         "fileURL":"UPD_FIRMWARE_UZB500_X_from05_07_to_UZB500_3CH_05_07.bin",
         "released":"2017-04-18",
         "comment":"Update firmware to 2 channels (EU\/RU\/US\/ANZ\/MY\/IL\/..) on 05.07",
         "position":"58",
         "version":"5.7"
      }
   ]
}
On Raspberry PI:
Dongle is recognized and initialized correctly with both Z-Way and OpenZWave (dev/ttyACM0). As soon as I want to include or exclude a node the dongle gets disconnected and reconnected to ttyACM1. Next time ttyACM2 and so on.

On Windows:
I can hear the USB-Disconnect/Connect Sounds whenever I want to include or exclude a node. COM-Port stays the same but I need to restart the Software.

Log:

Code: Select all

[2017-05-15 14:19:35.656] [I] [zway] Adding job: Remove node from network
[2017-05-15 14:19:35.670] [I] [zway] Job 0x4b (Remove node from network): Ready to remove - push button on the device to be removed
[2017-05-15 14:19:38.367] [C] [i/o] Device I/O error: Das Gerät erkennt den Befehl nicht.


[2017-05-15 14:19:38.367] [E] [zway] Device processing interrupted
[2017-05-15 14:19:38.375] [I] [core] Terminating Z-Wave binding
[2017-05-15 14:19:38.375] [I] [zway] Saving configuration data to config/zddx/c8217646-DevicesData.xml
[2017-05-15 14:19:48.376] [I] [core] Restarting Z-Wave binding
[2017-05-15 14:19:48.395] [I] [zway] Adding job: Get controller info and supported function classes
[2017-05-15 14:19:48.417] [I] [zway] Adding job: Get or set Z-Wave.Me firmware capabilities
[2017-05-15 14:19:48.417] [I] [zway] Adding job: Set Serial API timeouts
[2017-05-15 14:19:48.417] [I] [zway] Adding job: Set RF power level
[2017-05-15 14:19:48.417] [I] [zway] Adding job: WatchDog Start
[2017-05-15 14:19:48.417] [I] [zway] Adding job: Change/Get Z-Wave.Me firmware frequency
[2017-05-15 14:19:48.417] [I] [zway] Adding job: Get home id and controller node id
[2017-05-15 14:19:48.417] [I] [zway] Removing job: Get controller info and supported function classes
[2017-05-15 14:19:48.427] [W] [zway] Received SOF, while awaiting ACK
[2017-05-15 14:19:48.428] [W] [zway] No job of class 0x0a is waiting for callback 0x03
[2017-05-15 14:19:48.428] [I] [zway] Unhandled callback for function 0x00
[2017-05-15 14:19:48.428] [I] [zway] Removing job: Unknown function class
[2017-05-15 14:19:48.458] [I] [zway] Job 0xf5 (Get or set Z-Wave.Me firmware capabilities): In progress
[2017-05-15 14:19:48.469] [I] [zway] Job 0xf5 (Get or set Z-Wave.Me firmware capabilities): Done
[2017-05-15 14:19:48.469] [I] [zway] Removing job: Get or set Z-Wave.Me firmware capabilities
[2017-05-15 14:19:48.480] [I] [zway] Job 0x06 (Set Serial API timeouts): Old timeouts are: ACK timeout 1500 ms and Byte timeout 150 ms
[2017-05-15 14:19:48.480] [I] [zway] Removing job: Set Serial API timeouts
[2017-05-15 14:19:48.491] [I] [zway] Job 0x17 (Set RF power level): Done
[2017-05-15 14:19:48.491] [I] [zway] Removing job: Set RF power level
[2017-05-15 14:19:48.502] [I] [zway] Removing job: WatchDog Start
[2017-05-15 14:19:48.524] [I] [zway] Job 0xf2 (Change/Get Z-Wave.Me firmware frequency): Done
[2017-05-15 14:19:48.524] [I] [zway] Removing job: Change/Get Z-Wave.Me firmware frequency
[2017-05-15 14:19:48.535] [I] [zway] Job 0x20 (Get home id and controller node id): Home id: 0xc8217646, controller node id: 1
[2017-05-15 14:19:48.535] [I] [zway] Adding job: Get controller capabilities
[2017-05-15 14:19:48.535] [I] [zway] Adding job: Get controller version
[2017-05-15 14:19:48.535] [I] [zway] Adding job: Get SUC node id
[2017-05-15 14:19:48.535] [I] [zway] Adding job: Get initial data about network devices
[2017-05-15 14:19:48.535] [I] [zway] Adding job: Read bytes from extended EEPROM
[2017-05-15 14:19:48.535] [I] [zway] Removing job: Get home id and controller node id
[2017-05-15 14:19:48.546] [I] [zway] Removing job: Get controller capabilities
[2017-05-15 14:19:48.558] [I] [zway] Removing job: Get controller version
[2017-05-15 14:19:48.569] [I] [zway] Job 0x56 (Get SUC node id): SUC node is 1
[2017-05-15 14:19:48.569] [I] [zway] Removing job: Get SUC node id
[2017-05-15 14:19:48.665] [I] [zway] Adding job: Get node protocol information
[2017-05-15 14:19:48.665] [I] [zway] Adding job: Get routing table line
[2017-05-15 14:19:48.665] [I] [zway] Loading configuration data from config/zddx/c8217646-DevicesData.xml
[2017-05-15 14:19:48.670] [W] [zway] CC "MultiCmd" is not implemented
[2017-05-15 14:19:48.670] [W] [zway] CC "Security" is not implemented
[2017-05-15 14:19:48.670] [W] [zway] CC "CRC16" is not implemented
[2017-05-15 14:19:48.670] [I] [zway] Adding job: Set controller node information frame
[2017-05-15 14:19:48.670] [I] [zway] Loading Command Classes for device 1
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC Basic
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC ApplicationStatus
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC SwitchBinary
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC SwitchMultilevel
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC SceneActivation
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC ClimateControlSchedule
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC AssociationGroupInformation
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC DeviceResetLocally
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC CentralScene
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC ZWavePlusInfo
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC MultiChannel
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC ManufacturerSpecific
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC PowerLevel
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC NodeNaming
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC Clock
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC Association
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC Version
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC Time
[2017-05-15 14:19:48.670] [I] [zway] Node 1:0 supports CC MultiChannelAssociation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:1 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:2 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:3 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:4 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:5 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:6 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:7 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:8 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:9 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:10 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:11 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:12 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:13 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:14 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:15 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:16 supports CC Basic
[2017-05-15 14:19:48.671] [I] [zway] Node 1:1 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:2 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:3 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:4 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:5 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:6 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:7 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:8 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:9 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:10 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:11 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:12 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:13 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:14 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:15 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:16 supports CC SwitchBinary
[2017-05-15 14:19:48.671] [I] [zway] Node 1:1 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:2 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:3 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:4 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:5 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:6 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:7 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:8 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:9 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:10 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:11 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:12 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:13 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:14 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:15 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:16 supports CC SwitchMultilevel
[2017-05-15 14:19:48.671] [I] [zway] Node 1:1 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:2 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:3 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:4 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:5 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:6 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:7 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:8 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:9 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:10 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:11 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:12 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:13 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:14 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:15 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:16 supports CC SceneActivation
[2017-05-15 14:19:48.671] [I] [zway] Node 1:1 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:2 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:3 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:4 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:5 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:6 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:7 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:8 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:9 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:10 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:11 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:12 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:13 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:14 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:15 supports CC CentralScene
[2017-05-15 14:19:48.671] [I] [zway] Node 1:16 supports CC CentralScene
[2017-05-15 14:19:48.672] [I] [zway] Adding job: Get controller capabilities
[2017-05-15 14:19:48.672] [I] [zway] Removing job: Get initial data about network devices
[2017-05-15 14:19:48.688] [I] [zway] Removing job: Read bytes from extended EEPROM
[2017-05-15 14:19:48.699] [I] [zway] Removing job: Get node protocol information
[2017-05-15 14:19:48.710] [I] [zway] Job 0x80 (Get routing table line): List of neighbours for node 1: [ ]
[2017-05-15 14:19:48.710] [I] [zway] Removing job: Get routing table line
[2017-05-15 14:19:48.721] [I] [zway] Removing job: Set controller node information frame
[2017-05-15 14:19:48.743] [I] [zway] Removing job: Get controller capabilities

Pmant
Posts: 4
Joined: 12 May 2017 14:58

Re: How to load older FW version

Post by Pmant » 15 May 2017 22:59

UPDATE:
After switching to JP frequency it does not crash anymore, so how can I switch back to the EU firmware/frequency?

Willem_K
Posts: 5
Joined: 09 May 2017 11:07

Re: How to load older FW version

Post by Willem_K » 17 May 2017 16:23

I have the same.
I had an e-mail discussion with support and they said my stick is broken...but it cannot be a coincidence that we have the same issues. This should be solved one way or another.

herm
Posts: 1
Joined: 18 May 2017 23:37

Re: How to load older FW version

Post by herm » 18 May 2017 23:42

hi,

have exactly the same problem on my stick ... after upgrade to EU 2 channel 5.07 frequency changed to JP and was not usable anymore.... would be great if there exists some kind of downgrade/reflash procedure ...

herm

Willem_K
Posts: 5
Joined: 09 May 2017 11:07

Re: How to load older FW version

Post by Willem_K » 19 May 2017 13:30

So now there are already 3 people having the same issue with the stick after the upgrade, this is not good.
No solotion proposed yet by z-wave support. I hope they will soon.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 5 guests