You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From time to time I get very wrong sensor values. Now I have recognized a case where the z-wave message is clearly wrong and could be filtered by the receiver.
Device: Aeotec Multisensor 6, ZW-100 Application Version 1.7
Z-Way log: [2019-04-25 15:32:54.712] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"5787.5 °C","location":16} [2019-04-25 15:32:55.489] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"22.6 °C","location":16} [2019-04-25 15:32:56.049] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"5787.5 °C","location":16} [2019-04-25 15:32:57.757] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"22.6 °C","location":16}
Please consider the temperatures above 5000°C.
These wrong values are caused by a wrong value size in the Z-Wave message: It is 3 Bytes, but should be 2 Bytes. 3 Bytes is obviously wrong, because it wouldn't fit with the message length.
The Z-Wave message:
[2019-04-25 15:32:54.446] xxxxxxxx06450818012000FB221D1900003105012300E2A0
xxxxxxxx: Home ID
06: Source 06=aaaaaaaa
4508: Frame Control
4=0100
0: routed=no
1: ACK required=yes
0: low power=no
0: speed modified=no
5: Frame Type=explorer frame (route lost)
0: Beam Control (Battery support option)=no beam
8: Sequence No=8
18: Total Length in Bytes=24
01: Destination 01=Z-Way
2000FB22: Explorer Header
20=00100000
0010: Version
0000: Cmd=SearchRequest
00=00000000
0: Source Routed
0: Direction
0: Stop
0: Stop Request
0000: Reserved
FB: SX SessionTxRandomInterval
2: ST Session Time To Live (4,3,2...)
2: Pointer Index (0,1,2,3,4), current sender
1D190000: Repeater
1D: Repeater_0 29=bbbbbbbb
19: Repeater_1 25=cccccccc
31: Command Class 49=Sensor Multilevel
05: Command 5=Multilevel Sensor Report
012300E2: Param(s)
01=temperature
23=00100011
001: Precision = 1
00: Scale = 0
011: Size = 3
00E2A0: Sensor Value = 5801.6°C
A0: Checksum
[2019-04-25 15:32:54.446] #8 ExplF=SearchRequest 06=aaaaaaaa ->0 29=bbbbbbbb ->1 25=cccccccc ?> 01=Z-Way : 49=Sensor Multilevel - 5=Multilevel Sensor Report - 0x012300E2
`
The text was updated successfully, but these errors were encountered:
From time to time I get very wrong sensor values. Now I have recognized a case where the z-wave message is clearly wrong and could be filtered by the receiver.
Device: Aeotec Multisensor 6, ZW-100 Application Version 1.7
Z-Way log:
[2019-04-25 15:32:54.712] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"5787.5 °C","location":16} [2019-04-25 15:32:55.489] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"22.6 °C","location":16} [2019-04-25 15:32:56.049] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"5787.5 °C","location":16} [2019-04-25 15:32:57.757] [I] [core] Notification: device-info (device-temperature): {"dev":"ON-WZ Temperatur","l":"22.6 °C","location":16}
Please consider the temperatures above 5000°C.
These wrong values are caused by a wrong value size in the Z-Wave message: It is 3 Bytes, but should be 2 Bytes. 3 Bytes is obviously wrong, because it wouldn't fit with the message length.
The Z-Wave message:
[2019-04-25 15:32:54.446] xxxxxxxx06450818012000FB221D1900003105012300E2A0
xxxxxxxx: Home ID
06: Source 06=aaaaaaaa
4508: Frame Control
4=0100
0: routed=no
1: ACK required=yes
0: low power=no
0: speed modified=no
5: Frame Type=explorer frame (route lost)
0: Beam Control (Battery support option)=no beam
8: Sequence No=8
18: Total Length in Bytes=24
01: Destination 01=Z-Way
2000FB22: Explorer Header
20=00100000
0010: Version
0000: Cmd=SearchRequest
00=00000000
0: Source Routed
0: Direction
0: Stop
0: Stop Request
0000: Reserved
FB: SX SessionTxRandomInterval
2: ST Session Time To Live (4,3,2...)
2: Pointer Index (0,1,2,3,4), current sender
1D190000: Repeater
1D: Repeater_0 29=bbbbbbbb
19: Repeater_1 25=cccccccc
31: Command Class 49=Sensor Multilevel
05: Command 5=Multilevel Sensor Report
012300E2: Param(s)
01=temperature
23=00100011
001: Precision = 1
00: Scale = 0
011: Size = 3
00E2A0: Sensor Value = 5801.6°C
A0: Checksum
[2019-04-25 15:32:54.446] #8 ExplF=SearchRequest 06=aaaaaaaa ->0 29=bbbbbbbb ->1 25=cccccccc ?> 01=Z-Way : 49=Sensor Multilevel - 5=Multilevel Sensor Report - 0x012300E2
`
The text was updated successfully, but these errors were encountered: