I"m not sure what to post to help with diagnosing this, so any insight would be great. If i try to upgrade this outlet, it takes about 15-20 minutes, but never seems to finish. Then it will appear to need an upgrade again and is still on the old firmware.
Using the outlet works fine, just can’t upgrade it
Found the log file while it upgrading. It seems to have a few times where it goes to sleep, but it does wake up and continue on. It then finishes the upgrade and reboots, but is still on the old firmware.
2022-09-15T15:38:01.077Z CNTRLR » [Node 033] Sending firmware fragment 82 / 2239
2022-09-15T15:38:02.770Z CNTRLR [Node 033] Firmware fragment 82 already queued
2022-09-15T15:38:02.946Z CNTRLR [Node 033] Firmware fragment 82 already queued
2022-09-15T15:38:03.301Z CNTRLR [Node 033] Firmware fragment 82 already queued
2022-09-15T15:38:03.931Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:03.967Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:04.070Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:04.247Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:04.496Z CNTRLR [Node 033] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:05.026Z CNTRLR [Node 033] The node did not respond after 3 attempts, it is presumed dead
2022-09-15T15:38:05.027Z CNTRLR [Node 033] The node is now dead.
2022-09-15T15:38:05.033Z CNTRLR [Node 033] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status Fail) (ZW0202)
2022-09-15T15:38:05.415Z CNTRLR [Node 033] The node is now alive.
2022-09-15T15:38:05.417Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:05.453Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:05.591Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:05.909Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:05.981Z CNTRLR [Node 033] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:06.531Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:06.542Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2022-09-15T15:38:06.674Z CNTRLR [Node 033] The node did not respond after 3 attempts, it is presumed dead
2022-09-15T15:38:06.684Z CNTRLR [Node 033] The node is now dead.
2022-09-15T15:38:06.698Z CNTRLR [Node 033] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status Fail) (ZW0202)
2022-09-15T15:38:06.700Z CNTRLR [Node 033] The node is now alive.
2022-09-15T15:38:06.701Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:06.725Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:06.909Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:07.251Z CNTRLR [Node 033] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:07.734Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:07.779Z CNTRLR [Node 033] The node did not respond after 3 attempts, it is presumed dead
2022-09-15T15:38:07.780Z CNTRLR [Node 033] The node is now dead.
2022-09-15T15:38:07.786Z CNTRLR [Node 033] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status Fail) (ZW0202)
2022-09-15T15:38:07.839Z CNTRLR [Node 033] The node is now alive.
2022-09-15T15:38:07.841Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:07.877Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:08.086Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:08.403Z CNTRLR [Node 033] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:08.661Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:08.767Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:08.931Z CNTRLR [Node 033] The node did not respond after 3 attempts, it is presumed dead
2022-09-15T15:38:08.932Z CNTRLR [Node 033] The node is now dead.
2022-09-15T15:38:08.938Z CNTRLR [Node 033] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status Fail) (ZW0202)
2022-09-15T15:38:09.084Z CNTRLR [Node 033] The node is now alive.
2022-09-15T15:38:09.087Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:09.132Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:09.662Z CNTRLR [Node 033] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:10.158Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:10.192Z CNTRLR [Node 033] The node did not respond after 3 attempts, it is presumed dead
2022-09-15T15:38:10.193Z CNTRLR [Node 033] The node is now dead.
2022-09-15T15:38:10.198Z CNTRLR [Node 033] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status Fail) (ZW0202)
2022-09-15T15:38:10.236Z CNTRLR [Node 033] The node is now alive.
2022-09-15T15:38:10.238Z CNTRLR » [Node 033] Sending firmware fragment 83 / 2239
2022-09-15T15:38:10.273Z CNTRLR [Node 033] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2022-09-15T15:38:10.350Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:10.427Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:10.555Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T15:38:10.564Z CNTRLR [Node 033] Firmware fragment 83 already queued
2022-09-15T16:00:54.384Z CNTRLR » [Node 033] Sending firmware fragment 1701 / 2239
2022-09-15T16:00:54.733Z CNTRLR « [Node 019] received CentralScene notification {
"nodeId": 19,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0xed8201"
}
2022-09-15T16:00:54.765Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:54.811Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.035Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.108Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.164Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.202Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.231Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:55.998Z CNTRLR » [Node 033] Sending firmware fragment 1702 / 2239
2022-09-15T16:00:56.177Z CNTRLR [Node 033] Firmware fragment 1702 already queued
2022-09-15T16:00:56.611Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:56.644Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:56.665Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:56.759Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:56.785Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:57.634Z CNTRLR » [Node 033] Sending firmware fragment 1703 / 2239
2022-09-15T16:00:57.741Z CNTRLR [Node 033] Firmware fragment 1703 already queued
2022-09-15T16:00:57.864Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:57.919Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:57.970Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:58.184Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:58.563Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:58.680Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:58.781Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:58.802Z CNTRLR « [Node 019] received CentralScene notification {
"nodeId": 19,
"ccId": "Central Scene",
"ccCommand": "0x03",
"payload": "0xee8101"
}
2022-09-15T16:00:58.862Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:59.247Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:59.716Z CNTRLR » [Node 033] Sending firmware fragment 1704 / 2239
2022-09-15T16:00:59.793Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:59.837Z DRIVER Dropping message with invalid payload
2022-09-15T16:00:59.864Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:00.277Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:00.404Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:00.523Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:00.632Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:00.765Z DRIVER Dropping message with invalid payload
2022-09-15T16:01:01.617Z CNTRLR [Node 033] Firmware fragment 1704 already queued
2022-09-15T16:01:01.759Z CNTRLR [Node 033] Firmware fragment 1704 already queued
2022-09-15T16:01:02.157Z CNTRLR [Node 033] Firmware fragment 1704 already queued
2022-09-15T16:01:13.444Z CNTRLR » [Node 033] Sending firmware fragment 1705 / 2239
2022-09-15T16:01:13.700Z CNTRLR » [Node 033] Sending firmware fragment 1706 / 2239
2022-09-15T16:01:13.958Z CNTRLR » [Node 033] Sending firmware fragment 1707 / 2239
rebooting with old firmware"
2022-09-15T16:05:07.739Z CNTRLR » [Node 033] Sending firmware fragment 2239 / 2239
2022-09-15T16:05:16.419Z CNTRLR « [Node 033] Firmware update completed with status OK_RestartPending
2022-09-15T16:05:16.422Z CNTRLR [Node 033] Firmware updated, scheduling interview in 5 seconds...
2022-09-15T16:05:21.445Z CNTRLR [Node 033] Beginning interview - last completed stage: None
2022-09-15T16:05:21.447Z CNTRLR [Node 033] new node, doing a full interview...
2022-09-15T16:05:21.449Z CNTRLR » [Node 033] querying protocol info...
2022-09-15T16:05:21.483Z CNTRLR « [Node 033] received response for protocol info:
basic device class: Routing Slave
generic device class: Binary Switch
specific device class: Binary Power Switch
node type: End Node
is always listening: true
is frequent listening: false
can route messages: true
supports security: false
supports beaming: true
maximum data rate: 100000 kbps
protocol version: 3
2022-09-15T16:05:21.485Z CNTRLR [Node 033] Interview stage completed: ProtocolInfo
2022-09-15T16:05:21.486Z CNTRLR » [Node 033] querying node info...
2022-09-15T16:05:21.895Z CNTRLR « [Node 033] node info received
supported CCs:
· Z-Wave Plus Info
· CRC-16 Encapsulation
· Version
· Manufacturer Specific
· Device Reset Locally
· Association
· Association Group Information
· Powerlevel
· Binary Switch
· All Switch
· Configuration
· Scene Actuator Configuration
· Scene Activation
· Firmware Update Meta Data
2022-09-15T16:05:21.901Z CNTRLR [Node 033] Interview stage completed: NodeInfo
2022-09-15T16:05:21.914Z CNTRLR [Node 033] Interviewing Manufacturer Specific...
2022-09-15T16:05:21.915Z CNTRLR » [Node 033] querying manufacturer information...
2022-09-15T16:05:22.652Z CNTRLR « [Node 033] received response for manufacturer information:
manufacturer: GE/Jasco (0x63)
product type: 0x4952
product id: 0x3233
2022-09-15T16:05:22.657Z CNTRLR [Node 033] Interviewing Version...
2022-09-15T16:05:22.659Z CNTRLR » [Node 033] querying the CC version for Version...
2022-09-15T16:05:23.386Z CNTRLR [Node 033] supports CC Version (0x86) in version 2
2022-09-15T16:05:23.387Z CNTRLR » [Node 033] querying node versions...
2022-09-15T16:05:24.024Z CNTRLR « [Node 033] received response for node versions:
library type: Enhanced Slave (0x03)
protocol version: 4.38
firmware versions: 5.26
Do a heal on the node first, THEN do the fw upgrade.
I’ve done a heal as well as re-interview…neither seem to help
trying a new outlet right now to rule out a hardware issue
This indicates the fw was uploaded successfully and the node restarted.
Check the logs to see if it’s grabbing the 5.51 file from the web.
Odd, i have a new outlet and it also does the same thing.
where do i chekc the log on where its getting the firmware from?
It should say just before it starts sending the fragments.
looks like it is from the web:
Subscribed to Z-Wave JS Log Messages…
2022-09-15T15:36:37.251Z CNTRLR [Node 033] Downloading firmware update from https://raw.githubusercontent.com/
jascoproducts/firmware/9b5520f5056f7d3fce3fa6adc28bdaf27f8d0a68/zwave/Enbright
en-GE/ZW1002/14297%20-%20In-Wall%20Smart%20Outlet%2C%20Tamper%20Resistant%2C%2
0Lt%20Almd%2C%20500S/5.51/ZW1002_Enbrighten-GE_14297_5.51.otz...
2022-09-15T15:36:37.747Z CNTRLR [Node 033] Firmware update https://raw.githubusercontent.com/jascoproducts/fir
mware/9b5520f5056f7d3fce3fa6adc28bdaf27f8d0a68/zwave/Enbrighten-GE/ZW1002/1429
7%20-%20In-Wall%20Smart%20Outlet%2C%20Tamper%20Resistant%2C%20Lt%20Almd%2C%205
00S/5.51/ZW1002_Enbrighten-GE_14297_5.51.otz downloaded, installing...
2022-09-15T15:36:38.118Z CNTRLR » [Node 033] Starting firmware update...
2022-09-15T15:36:39.096Z CNTRLR » [Node 033] Sending firmware fragment 1 / 2239
2022-09-15T15:36:39.747Z CNTRLR » [Node 033] Sending firmware fragment 2 / 2239
2022-09-15T15:36:41.764Z CNTRLR » [Node 033] Sending firmware fragment 1 / 2239
Looks like it should be the correct file, but maybe the actual firmware isn’t 5.51.
fuuny thing is that it works on my white outlet but not on 2 almond ones
I am seeing the same issue with my almond enlighten receptacles. I have 4, and the logs for each one of them looks exactly what was posted above. Everything appears to work, but after reboot, the version is unchanged.
do you have any white ones? those work for me
I have the same issue. I have just reported the issue in their github page. Let see if it could help. [Bug Report]: Enbrighten-GE - ZW1002 - 14297 - FW VERSION 5.51 · Issue #99 · jascoproducts/firmware · GitHub