forum

Posted: **14 Jan 2015 12:25**

I have a Fibaro Smoke Alarm. The configuration of this is very hairy, but it seems like more bugs in z-way-server...

Using "expert" commands, I can set the temperature sensor offset on parameter 73, and it's getting this value fine:

Code: Select all

[2015-01-14 09:56:29.705] [D] [zway] RECEIVED: ( 01 10 00 04 00 0D 0A 56 01 70 06 49 02 00 00 69 65 8A )
[2015-01-14 09:56:29.706] [D] [zway] SENT ACK
[2015-01-14 09:56:29.706] [D] [zway] SETDATA devices.13.data.lastReceived = 0 (0x00000000)
[2015-01-14 09:56:29.706] [D] [zway] SETDATA devices.13.instances.0.commandClasses.112.data.73.size = 2 (0x00000002)
[2015-01-14 09:56:29.706] [D] [zway] SETDATA devices.13.instances.0.commandClasses.112.data.73.val = 0 (0x00000000)
[2015-01-14 09:56:29.707] [D] [zway] SETDATA devices.13.instances.0.commandClasses.112.data.73 = Empty
[2015-01-14 09:56:29.707] [I] [zway] Node 13:0 CC Configuration: Parameter 0x49 = 0 (size = 2)

But in the "configuration" folder, it refuses to update the value (or the timestamp):

Nº 73 - Temperature measurement compensation
[64536]
updated: 13.01.2015 | Default value is: 0 |

The 64536 value I have no idea where it comes from. I set another parameter a yesterday, and it sent the 64536 to the device (the device had 0), and the device then reported a temperature of -76.1 degrees.
(I started a post about it before I discovered that this parameter was completely off...)

edit: 112.data.73 is 0 on the JSON API as well. Just not in the "configuration".

edit 2: configuration stays the same after restarts and upgrade to rc10 as well.

Posted: **19 Jan 2015 21:56**

page refresh does not help?

Posted: **25 Jan 2015 23:39**

No, not at all. I tried restarting the z-way-server as well as upgrading it.

I have managed to repeat this with a newly attached Aeon Labs Multisensor. The values in the configuration interface are not related at all to the values in the JSON interface (or z-way-server.log). Interestingly enough these values update on page reload.

I had to pick device description manually (I don't know why, interview did not fail). It might be related?

edit:
The smoke detector doesn't even fill in all the data, for instance
112.data.89 is 1
but

Nº 89 - Tamper alarm
( ) 0 – tamper alarm inactive
( ) 1 – tamper alarm active, with cancellation option available
( ) 2 – tamper alarm active, without cancellation option

has nothing marked as the current value.

forum

configuration not updating

configuration not updating

Re: configuration not updating

Re: configuration not updating