Aeotec ZWA019 Water Sensor 7 Pro

[no1warr1or]

I'm blanket asking for help on this. I'm having issues with the above mentioned sensor. The water detection portion works perfectly however the temperature and humidity do not update ever and only display the readings it had when first paired to the zwave network. I have tried removing then adding it back, checking the configuration and resetting the device. I’ve submitted a ticket with aeotec and opened a thread in the Home Assistant Community, but wanted to see if anyone had similar issues with this device

[AlCalzone]

Are the parameters for automatic reporting configured properly?

[no1warr1or]

So an update, the other sensors are reporting properly i just didnt give it enough time. It's still just the above mentioned water sensor not reporting. The guy I'm working with at aeotec said he's gonna continue testing units he has with the same application version and forward everything to the firmware engineering team, which to me indicates it could be a firmware issue?

[AlCalzone]

which to me indicates it could be a firmware issue?

Could be. Let's see what they find out.

[no1warr1or]

I was just provided a firmware update to test out. Wish me luck 😂

[no1warr1or]

Firmware did the job. I'll continue to monitor and update this with a link to the firmware/instructions when they officially post it up on their website.

[no1warr1or]

https://help.aeotec.com/support/solutions/articles/6000255849--zwa019-update-water-sensor-7-pro

[no1warr1or]

https://help.aeotec.com/support/solutions/articles/6000255849--zwa019-update-water-sensor-7-pro

[thecobra666]

I'm updating my 2 sensors. But one is stuck on fw update 99%. It did a new interview but it still says firmware v2.0 and it stays at 99%. The other stays at 100 procent. How did the update go for you?

[no1warr1or]

I've had a lot of issues updating some aeotec battery devices. If I remember correctly, I had to keep activating the action button. Not sure if it was going to sleep or what.

[thecobra666]

I've had a lot of issues updating some aeotec battery devices. If I remember correctly, I had to keep activating the action button. Not sure if it was going to sleep or what.

Thanks for the reply. I refreshed the page in zwavejs2mqtt and it changed to the firmware version 😅. Update successful :)

[garyjlo]

I have two of these devices (ZWA019), both with firmware version 2.1
When I attempt to do an OTA update to v2.3 [stable], I'm getting an error of "Error_InvalidHardwareVersion". The log is below.

I have also tried doing a firmware update from the advanced actions menu after manually downloading the US, EU and AU versions of the v2.3 firmware from Aoetec's site but they are all giving me the same error.

2024-12-15T03:16:51.015Z CNTRLR   [Node 066] OTA firmware update started, downloading 1 updates...
2024-12-15T03:16:51.016Z CNTRLR   [Node 066] Downloading firmware update 0 of 1...
2024-12-15T03:16:51.411Z CNTRLR   [Node 066] All updates downloaded, validating device IDs...
2024-12-15T03:17:09.187Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 28
                                    │ security class:  S2_Authenticated
                                    └─[WakeUpCCWakeUpNotification]
2024-12-15T03:17:09.187Z CNTRLR « [Node 066] received wakeup notification
2024-12-14 22:17:09.189 INFO STORE: [Node 066] Is now awake
2024-12-15T03:17:09.190Z CNTRLR   [Node 066] The node is now awake.
2024-12-15T03:17:09.198Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      11
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 55
                                    └─[ManufacturerSpecificCCGet]
2024-12-15T03:17:09.246Z CNTRLR   [Node 066] [~] [Manufacturer Specific] productId: 19 => 19        [Endpoint 0]
2024-12-14 22:17:09.247 INFO STORE: [Node 066] Value updated: 114-0-productId 19 => 19
2024-12-15T03:17:09.248Z CNTRLR   [Node 066] [~] [Manufacturer Specific] productType: 258 => 258    [Endpoint 0]
2024-12-14 22:17:09.249 INFO STORE: [Node 066] Value updated: 114-0-productType 258 => 258
2024-12-15T03:17:09.250Z CNTRLR   [Node 066] [~] [Manufacturer Specific] manufacturerId: 881 => 881 [Endpoint 0]
2024-12-14 22:17:09.251 INFO STORE: [Node 066] Value updated: 114-0-manufacturerId 881 => 881
2024-12-15T03:17:09.252Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 29
                                    │ security class:  S2_Authenticated
                                    └─[ManufacturerSpecificCCReport]
                                        manufacturer id: 0x0371
                                        product type:    0x0102
                                        product id:      0x13
2024-12-15T03:17:09.258Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      12
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 56
                                    └─[VersionCCGet]
2024-12-15T03:17:09.307Z CNTRLR   [Node 066] [~] [Version] hardwareVersion: 1 => 1                  [Endpoint 0]
2024-12-14 22:17:09.308 INFO STORE: [Node 066] Value updated: 134-0-hardwareVersion 1 => 1
2024-12-15T03:17:09.311Z CNTRLR   [Node 066] [~] [Version] firmwareVersions: 2.1 => 2.1             [Endpoint 0]
2024-12-14 22:17:09.311 INFO STORE: [Node 066] Value updated: 134-0-firmwareVersions 2.1 => 2.1
2024-12-15T03:17:09.312Z CNTRLR   [Node 066] [~] [Version] protocolVersion: "7.15" => "7.15"        [Endpoint 0]
2024-12-14 22:17:09.313 INFO STORE: [Node 066] Value updated: 134-0-protocolVersion 7.15 => 7.15
2024-12-15T03:17:09.314Z CNTRLR   [Node 066] [~] [Version] libraryType: 3 => 3                      [Endpoint 0]
2024-12-14 22:17:09.314 INFO STORE: [Node 066] Value updated: 134-0-libraryType 3 => 3
2024-12-15T03:17:09.315Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 30
                                    │ security class:  S2_Authenticated
                                    └─[VersionCCReport]
                                        library type:      Enhanced Slave
                                        protocol version:  7.15
                                        firmware versions: 2.1
                                        hardware version:  1
2024-12-15T03:17:09.320Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      13
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 57
                                    └─[VersionCCZWaveSoftwareGet]
2024-12-15T03:17:09.372Z CNTRLR   [Node 066] [~] [Version] applicationBuildNumber: 0 => 0           [Endpoint 0]
2024-12-14 22:17:09.373 INFO STORE: [Node 066] Value updated: 134-0-applicationBuildNumber 0 => 0
2024-12-15T03:17:09.374Z CNTRLR   [Node 066] [~] [Version] applicationVersion: "2.1.0" => "2.1.0"   [Endpoint 0]
2024-12-14 22:17:09.375 INFO STORE: [Node 066] Value updated: 134-0-applicationVersion 2.1.0 => 2.1.0
2024-12-15T03:17:09.376Z CNTRLR   [Node 066] [~] [Version] zWaveProtocolBuildNumber: 256 => 256     [Endpoint 0]
2024-12-14 22:17:09.377 INFO STORE: [Node 066] Value updated: 134-0-zWaveProtocolBuildNumber 256 => 256
2024-12-15T03:17:09.378Z CNTRLR   [Node 066] [~] [Version] zWaveProtocolVersion: "7.15.4" => "7.15. [Endpoint 0]
                                  4"
2024-12-14 22:17:09.379 INFO STORE: [Node 066] Value updated: 134-0-zWaveProtocolVersion 7.15.4 => 7.15.4
2024-12-15T03:17:09.380Z CNTRLR   [Node 066] [~] [Version] hostInterfaceBuildNumber: 0 => 0         [Endpoint 0]
2024-12-14 22:17:09.380 INFO STORE: [Node 066] Value updated: 134-0-hostInterfaceBuildNumber 0 => 0
2024-12-15T03:17:09.381Z CNTRLR   [Node 066] [~] [Version] hostInterfaceVersion: "unused" => "unuse [Endpoint 0]
                                  d"
2024-12-14 22:17:09.382 INFO STORE: [Node 066] Value updated: 134-0-hostInterfaceVersion unused => unused
2024-12-15T03:17:09.382Z CNTRLR   [Node 066] [~] [Version] applicationFrameworkBuildNumber: 256 =>  [Endpoint 0]
                                  256
2024-12-14 22:17:09.383 INFO STORE: [Node 066] Value updated: 134-0-applicationFrameworkBuildNumber 256 => 256
2024-12-15T03:17:09.384Z CNTRLR   [Node 066] [~] [Version] applicationFrameworkAPIVersion: "10.15.4 [Endpoint 0]
                                  " => "10.15.4"
2024-12-14 22:17:09.384 INFO STORE: [Node 066] Value updated: 134-0-applicationFrameworkAPIVersion 10.15.4 => 10.15.4
2024-12-15T03:17:09.385Z CNTRLR   [Node 066] [~] [Version] sdkVersion: "7.15.4" => "7.15.4"         [Endpoint 0]
2024-12-14 22:17:09.386 INFO STORE: [Node 066] Value updated: 134-0-sdkVersion 7.15.4 => 7.15.4
2024-12-15T03:17:09.387Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 31
                                    │ security class:  S2_Authenticated
                                    └─[VersionCCZWaveSoftwareReport]
                                        SDK version:                  7.15.4
                                        appl. framework API version:  10.15.4
                                        appl. framework build number: 256
                                        host interface version:       unused
                                        Z-Wave protocol version:      7.15.4
                                        Z-Wave protocol build number: 256
                                        application version:          2.1.0
                                        application build number:     0
2024-12-15T03:17:09.388Z CNTRLR   [Node 066] Device IDs match, installing firmware updates...
2024-12-15T03:17:09.393Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      14
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 58
                                    └─[FirmwareUpdateMetaDataCCMetaDataGet]
2024-12-15T03:17:09.443Z CNTRLR   [Node 066] [~] [Firmware Update Meta Data] additionalF [Endpoint 0] [internal]
                                  irmwareIDs:  => 
2024-12-15T03:17:09.443Z CNTRLR   [Node 066] [~] [Firmware Update Meta Data] firmwareUpg [Endpoint 0] [internal]
                                  radable: true => true
2024-12-15T03:17:09.444Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 32
                                    │ security class:  S2_Authenticated
                                    └─[FirmwareUpdateMetaDataCCMetaDataReport]
                                        manufacturer id:     881
                                        firmware id:         531
                                        checksum:            0
                                        firmware upgradable: true
                                        max fragment size:   28
                                        hardware version:    1
2024-12-15T03:17:09.466Z CNTRLR   [Node 066] Updating firmware (part 1 / 1)...
2024-12-15T03:17:09.466Z CNTRLR » [Node 066] Starting firmware update...
2024-12-15T03:17:09.473Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      15
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 59
                                    └─[FirmwareUpdateMetaDataCCRequestGet]
                                        manufacturer id:     0x0371
                                        firmware id:         0x0213
                                        checksum:            0x113a
                                        firmware target:     0
                                        fragment size:       28
                                        activation:          false
                                        resume:              false
                                        non-secure transfer: false
2024-12-15T03:17:09.523Z DRIVER « [Node 066] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 33
                                    │ security class:  S2_Authenticated
                                    └─[FirmwareUpdateMetaDataCCRequestReport]
                                        status: Error_InvalidHardwareVersion
2024-12-15T03:17:09.777Z CNTRLR » [Node 066] Sending node back to sleep...
2024-12-15T03:17:09.783Z DRIVER » [Node 066] [REQ] [SendData]
                                  │ transmit options: 0x24
                                  │ callback id:      0
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 60
                                    └─[WakeUpCCNoMoreInformation]
2024-12-14 22:17:09.797 INFO STORE: [Node 066] Is now asleep
2024-12-15T03:17:09.798Z CNTRLR   [Node 066] The node is now asleep.

[AlCalzone]

Update Z-Wave JS (UI)