@Janus as you can see I have already done the association
It was already set the slide function
and at last I have enabled the report type
The only think I have not done is mess around with the cfg file
Is this really needed?
I have changed the cfg file with no result.
See below the log file during test
2019-02-27 21:39:39.427 Detail, Node006, Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x06, 0x08, 0x70, 0x06, 0x0a, 0x04, 0x01, 0x00, 0x15, 0x3b, 0xac
2019-02-27 21:39:39.427 Detail,
2019-02-27 21:39:39.428 Detail, Node006, Refreshed Value: old value=16779577, new value=16782651, type=int
2019-02-27 21:39:39.428 Detail, Node006, Changes to this value are not verified
2019-02-27 21:39:39.428 Info, Node006, Received Configuration report: Parameter=10, Value=16782651
2019-02-27 21:39:39.428 Detail, Node006, Notification: ValueChanged
2019-02-27 21:39:39.706 Detail, Node006, Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x06, 0x08, 0x70, 0x06, 0x09, 0x04, 0x01, 0x00, 0x65, 0x3c, 0xd8
2019-02-27 21:39:39.706 Detail,
2019-02-27 21:39:39.706 Detail, Node006, Refreshed Value: old value=16812602, new value=16803132, type=int
2019-02-27 21:39:39.706 Detail, Node006, Changes to this value are not verified
2019-02-27 21:39:39.706 Info, Node006, Received Configuration report: Parameter=9, Value=16803132
2019-02-27 21:39:39.707 Detail, Node006, Notification: ValueChanged
2019-02-27 21:39:40.878 Detail, Node006, Received: 0x01, 0x0e, 0x00, 0x04, 0x00, 0x06, 0x08, 0x70, 0x06, 0x0a, 0x04, 0x01, 0x00, 0x21, 0x3d, 0x9e
2019-02-27 21:39:40.878 Detail,
2019-02-27 21:39:40.878 Detail, Node006, Refreshed Value: old value=16782651, new value=16785725, type=int
2019-02-27 21:39:40.878 Detail, Node006, Changes to this value are not verified
2019-02-27 21:39:40.878 Info, Node006, Received Configuration report: Parameter=10, Value=16785725
2019-02-27 21:39:40.879 Detail, Node006, Notification: ValueChanged
hmm then I really don’t know why the slide function to dim your zwave light bulbs doesn’t work. I have no experience with this so cannot help you further. If messing around with the cfg file is not what you like then I suggest you not do it. Btw, the slide function is not a central command scene but a multi-level switch, which means modifying the cfg file will not make any difference.
I suggest you contact Aeotec for further assistance or ask here in the forum for a similar issue.
Thanks Janus for your help. But so fat I have not found anything else related with the dim function.
Did you add your wallmote as secured device? I don’t know if that matters…
No I did not since I do not have any other secure devices. But I do not think this matter.
In the documentation it states the slide function works with a dimmer device though… so probably it doesn’t work directly with a light bulb.
Mi light bulb is an aeotec light bulb. What do you mean by dimmer device?
e.g. Aeotec nano dimmer?
I think I am going to contact Aeotec.
Okay I am curious about what they have to say.
@janus How did you test/debug if the API call from the Pyhthon script to home assistant is working? I’m not sure if that part is working and I like to test it?
In the script above, DEBUG is set to True. You should be able to see the return code of resp variable. That is the last output of my script.
Has anyone able to get the Slide/Swipe working?
Would be interested to know the answer to this as well.
I’m trying to disable the sound but the option has no effect.
logs when I do it :
2019-11-01 20:51:08.634 Info, Node007, Value::Set - COMMAND_CLASS_CONFIGURATION - Touch sound - 1 - 1 - Disable
2019-11-01 20:51:08.634 Info, Node007, Configuration::Set - Parameter=1, Value=0 Size=1
2019-11-01 20:51:08.634 Detail,
2019-11-01 20:51:08.635 Detail, Node007, Queuing (WakeUp) ConfigurationCmd_Set (Node=7): 0x01, 0x0c, 0x00, 0x13, 0x07, 0x05, 0x70, 0x04, 0x01, 0x01, 0x00, 0x25, 0x49, 0xfa
2019-11-01 20:51:08.635 Detail,
2019-11-01 20:51:08.635 Detail, Node007, Queuing (WakeUp) ConfigurationCmd_Get (Node=7): 0x01, 0x0a, 0x00, 0x13, 0x07, 0x03, 0x70, 0x05, 0x01, 0x25, 0x4a, 0xf9
Is it a bug ? Is there another way to change parameters ?
Thanks
From the docs:
Battery powered devices need to be awake before you can use the Z-Wave control panel to update their settings. How to wake your device is device specific, and some devices will stay awake for only a couple of seconds. Please refer to the manual of your device for more details.
Basically, you either need to manually wake up your remote, or wait for it to wake up by itself. Once it wakes up, the config setting will be changed. That’s why the log says “Queuing (WakeUp)”, it is queuing the configuration change message and will send it when the device wakes up.
1 Like
I got a wallmote on saturday and I can make it work with my lights but not my lock or garage door.
I asked for help and the reply was I need to enable CENTRAL_SCENE and then any device should work.
The docs here: https://www.home-assistant.io/docs/z-wave/device-specific/#aeotec-wallmote
say to look for the section with id=“91” in your zwcfg_*.xml file and then replace with with the code they list.
The problem I am having is I can’t find any section with id=“91” in that file. I can’t find any mention of wallmote in that file. I can find the aretec stick itself (ZW090 Z-Stick Gen5 US) but that is it. I did find it listed in zwave_device_config.yaml but not the zwcfg_*.xml config file
Where are you guys finding this id=“91”?
Thanks.
If the zwcfg_*.xml only shows the Z-Stick, then you might not yet have included the wallmote into your Z-Wave network?
Head over to the Settings > Z Wave Menu and add the wallmote as a new node
To provide Central Scene support you need to shutdown Home Assistant and modify your
zwcfg_*.xmlfile according to the following guides.
Did you do the part in bold?