I am trying to update a config parameter shown below, but it is not being pushed to device. Once I re-enter the config screen option is being disabled.
Device is DSC18 by AEON Labs, Connected via Z‐Stick Gen5 USB Controller
Is it for a battery operated device? That’ll have to be woken up to retrieve pending commands.
no it’s connected to the mains supply.
It looks like it needs to send a 4 byte parameter from the zwave controller, but it is sending a boolean (or something like that). You might want to submit a bug report for this. I’m not sure what controller you are using though.
https://manual.zwave.eu/backend/make.php?lang=en&sku=AEO_MES&cert=ZC08-13030007
1 Like
my controller is Z‐Stick Gen5 USB Controller
I think you are correct, I am not able to see the command that need to be sent in the datasheet, i.e. the option to enable voltage does not exist. Not sure if it makes a difference but I have the Gen2 module.
---------
PARAMETER
101
BITMASK
1
Automatic Report: Group 1 - Voltage
---------
2024-03-19T08:51:18.322Z DRIVER all queues busy
2024-03-19T08:51:18.329Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 5
└─[ConfigurationCCSet]
parameter #: 101
reset to default: false
value size: 4
value format: UnsignedInteger
value: 13
2024-03-19T08:51:18.337Z DRIVER « [RES] [SendData]
was sent: true
2024-03-19T08:51:18.355Z DRIVER « [REQ] [SendData]
callback id: 5
transmit status: OK
2024-03-19T08:51:18.364Z DRIVER all queues idle
2024-03-19T08:51:19.364Z DRIVER all queues busy
2024-03-19T08:51:19.368Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 6
└─[ConfigurationCCGet]
parameter #: 101
2024-03-19T08:51:19.376Z DRIVER « [RES] [SendData]
was sent: true
2024-03-19T08:51:19.393Z DRIVER « [REQ] [SendData]
callback id: 6
transmit status: OK
2024-03-19T08:51:19.410Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[ConfigurationCCReport]
parameter #: 101
value size: 4
value: 12
2024-03-19T08:51:19.415Z DRIVER all queues idle
2024-03-19T08:51:21.945Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: kWh
rate type: Consumed
value: 1226.902
time delta: 30 seconds
prev. value: 1226.902
2024-03-19T08:51:22.030Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 0
time delta: 0 seconds
When changing the following it is working fine (in the logs i changed from 5% to 1%)
It is also referenced in the datasheet:
------------------
PARAMETER
92
Minimum Power Percentage Change to Trigger Event
------------------
2024-03-19T08:55:19.515Z DRIVER all queues idle
2024-03-19T08:55:20.518Z DRIVER all queues busy
2024-03-19T08:55:20.525Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 8
└─[ConfigurationCCGet]
parameter #: 92
2024-03-19T08:55:20.534Z DRIVER « [RES] [SendData]
was sent: true
2024-03-19T08:55:20.551Z DRIVER « [REQ] [SendData]
callback id: 8
transmit status: OK
2024-03-19T08:55:20.565Z DRIVER « [Node 009] [REQ] [ApplicationCommand]
└─[ConfigurationCCReport]
parameter #: 92
value size: 1
value: 1
2024-03-19T08:55:20.566Z DRIVER all queues idle
Try going to Developer Tools > Services > and using the Z-Wave: Set device configuration parameter service. you can manually specify all the settings for the parameter.
1 Like
thanks! I was not aware of this function in HA!
The problem I have that in the module docs, there is no reference how to change this parameter… i.e what values are should use.
as a workaround yesterday I managed to take voltage reading using this automation running every minute and it is working fine. not sure if this is the proper way to do it though.
That frequency may be ok for 1 piece of data, but zwave is not a fast protocol and having too much data flowing is a common cause for zwave network failures. What’s the use case for needing voltage every minute?
The reason is to track the fluctuations in the voltage. I dont think that will be an issue since I am already have a power meter sending power readings every 20secs for 2 circuits.
Power readings every 20 seconds is pretty ambitious for zwave. It may work ok for now, as you add more stuff it’ll breakdown and it’ll start reporting dead nodes and timeouts.
I have been using it for 5 years now, never had any issues. I have the power meter, water heater switch, door switch and 3 multi sensors.
1 Like