Aeotec DSA22 keyfob configuration in HA

Configuration Z-Wave
1

Hi, trying to configure this small Aeotec Keyfob.

image

Was able to include it in the network. Set parameter 250 to 1 to be in scene mode like I did for Minimote successfully. I’ve seen that there is a dsa22.xml file for openzwave.

Is there a way to integrate this in HA? Same way as Minimote? Does someone successfully did it? Thanks.

This is the code I tried to execute in automations:

- id: '100000010'
  alias: Minimote Button 1 Pressed
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      entity_id: zwave.zwave.aeondsa22_key_fob
      scene_id: 1
  action:
    service: cover.toggle
    entity_id: cover.fibfgrm222_chambreparents_storesud_level
2

I have no experience with that hardware but your entity_id is incorrect. Should be “zwave.aeondsa22_key_fob” instead of “zwave.zwave.aeondsa22_key_fob”.

3

thanks, sorry typo error, just changed this, no change.

4

Post the log messages from the OZW_Log.txt file when pressing buttons in the keyfob.

5

Thanks, here’s the log:

2019-10-27 09:01:06.947 Info, Node015, Received Scene Activation set from node 15: scene id=1 via configuration. Sending event notification.
2019-10-27 09:01:06.947 Detail, Node015, Notification: SceneEvent
2019-10-27 09:01:27.000 Detail, Node015,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x0f, 0x04, 0x2b, 0x01, 0x01, 0xff, 0x2e
2019-10-27 09:01:27.000 Detail,
2019-10-27 09:01:27.001 Info, Node015, Received Scene Activation set from node 15: scene id=1 via configuration. Sending event notification.
2019-10-27 09:01:27.001 Detail, Node015, Notification: SceneEvent

EDIT: In fact now the scene is working!! had some difficulties to set up correctly the remote and set it up to “scene” mode.

Now I’ve seen in the configuration device list that my remote DSA22 appears 3 times, is there a correct way to delete the other 2? Sure it’s my fault, I did include and exclude many times, but it appears that this has not been correctly exlcuded. In the z-wave device list it is correct, it appears only once.

DSA22HA
DSA22HA967×150 21.3 KB

Thanks a lot!

6

The only way to remove devices (well, Z-Wave at least) is to delete them from the .storage/core.device_registry file. Stop HA, make a backup, and delete the removed nodes from the file.

7

Ok, bad news, now the Aeotec Minimote is no more available! Still in the Configuration…Devices list but no more in the Z-Wave Devices list. Seems to me that the DSA22 Keyfob has taken his place, How’s that possible?? No way to use both remotes?
Try to add node again:

2019-10-27 18:04:19.958 Detail,
2019-10-27 18:04:19.959 Info, Node005, Sending (WakeUp) message (Callback ID=0x68, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x84, 0x08, 0x25, 0x68, 0x23
2019-10-27 18:04:19.966 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-10-27 18:04:19.966 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2019-10-27 18:04:19.983 Detail, Node005,   Received: 0x01, 0x07, 0x00, 0x13, 0x68, 0x00, 0x00, 0x03, 0x80
2019-10-27 18:04:19.983 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x68 received (expected 0x68)
2019-10-27 18:04:19.983 Info, Node005, Request RTT 24 Average Request RTT 24
2019-10-27 18:04:19.983 Info, Node005,   Node 5 has been marked as asleep
2019-10-27 18:04:19.984 Detail,   Expected callbackId was received
2019-10-27 18:04:19.984 Detail,   Expected reply was received
2019-10-27 18:04:19.984 Detail,   Message transaction complete
2019-10-27 18:04:19.984 Detail,
2019-10-27 18:04:19.984 Detail, Node005, Removing current message
2019-10-27 18:04:19.984 Detail, Node005, Notification: Notification - Node Asleep
2019-10-27 18:04:32.281 Info, Node005, Value::Set - COMMAND_CLASS_CONFIGURATION - Mode - 250 - 1 - Scene
2019-10-27 18:04:32.281 Info, Node005, Configuration::Set - Parameter=250, Value=1 Size=1
2019-10-27 18:04:32.281 Detail,
2019-10-27 18:04:32.281 Detail, Node005, Queuing (WakeUp) ConfigurationCmd_Set (Node=5): 0x01, 0x0c, 0x00, 0x13, 0x05, 0x05, 0x70, 0x04, 0xfa, 0x01, 0x01, 0x25, 0x69, 0x22
2019-10-27 18:04:32.282 Detail,
2019-10-27 18:04:32.282 Detail, Node005, Queuing (WakeUp) ConfigurationCmd_Get (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x70, 0x05, 0xfa, 0x25, 0x6a, 0x20

Now it works, but had to add Minimote again in z-wave, bug ?

8

What does it mean to be “in the Configuration”? What is the “Z-Wave Devices list”?

Seems to me that the DSA22 Keyfob has taken his place, How’s that possible?? No way to use both remotes?

No, that isn’t possible. Node IDs are never re-used.

2019-10-27 18:04:19.959 Info, Node005, Sending (WakeUp) message (Callback ID=0x68, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x84, 0x08, 0x25, 0x68, 0x23

What are you trying to show with this log sequence? It’s showing a configuration parameter being set on a Node 5 (the minimote?), it’s not showing any node being added. You cannot add a node again without removing it first. Your other logs showed Node 15, so obviously there are different nodes in question here.

9

I’m surprised by your response, I just want to help to find solutions. AND I cannot do print screen each time.

It’s clear to me: follow the path Configuration Menu (GEARING LOGO)

and then Devices list.

I just can tell you that the DEVICE Node 5 disapeared after adding the DSA22 node. I cannot tell you why, but it was true. As I told you, I cannot make printscreens each time.

It’s also very clear to me, in this sequence I’m trying to explain you, but it’s difficult… that I had to add the Minimote AGAIN.

YES, NOTE 015 is DSA22 and NODE 005 is Minimote, this is why I mention this, because it’s very strange! Now if you do not want me to report my (poor) experience in this forum, just tell me and I keep it for me, but I thought that the goal of that kind of discuss forum was the place to discuss…

10

Wonderful…

If you had to add the minimote it would not stay as Node 5, it would be higher in number. I’m not sure what you are experiencing, but it sounds you might be moving faster than the system can process.

Sorry you’re having a bad time. It can be frustrating. We were all in the same boat at some point.

11

Wow, all I did was ask some follow up questions to try and understand the problem you are still having. Good luck.

12

freshcoast was ‘asking’ to help you to find the reasons for the error, he was not being snarky.

If you require ‘flowery language’ to elicit a response, and to do it in the least offensive possible way then it will take pages to convey the point and people just give up reading.
Remember that text does not convey tone and intent, you are imposing your own values there.
We are ALL volunteers and we are trying to help, honest :smiley:

Some background : - hardly ANY of my setup is in configuration.yaml but the ‘configuration’ is things ‘you’ have changed and can be in mutiple different files, formatted in different ways, some of it is plain text, some of it isn’t.

Oh and there are different ways of accessing these files, each with their own benefits and penalties.

13

you’re right, I just replied him the way he did, no aggressivity involved. My first post was to congrats all people involved in this wonderful project: Issues getting Aeotec DSA22 Key Fob & Aeotec DSA03202 Minimote working

At this time the two remotes are working. After reincluding my Minimote a second time.
The sequence was:

  1. included Minimote NODE ID was 5. Was able to program all the buttons.
  2. included DSA 22 NODE ID was 15 was able to program all the buttons
  3. it was late, wanted to go to bed, push the button of the minimote for the cover, nothing happens
  4. looking at device list, Minimote was still there
  5. looking in z-wave nodes, was not listed!
  6. just included it again, put parameter 250 to 1 and it was again in z-wave list WITH NODE ID 5.

That’s it! As I found this strange, I reported it there. Peacefully. if a developer needs a log, just ask me, and specify the name of the file.
3.