Aeotec Doorbell 6 - ZW162

Configuration Z-Wave
8

Does anyone have a good working example of a docker run command to get OZWCP running?

I tried the following:

sudo docker run -d --name="ozw-cp" -u 0 -p 8008:8008 --device=/dev/ttyUSB-ZStick-5G -v /home/finity/docker/hass-config/zwcfg_0xecbef344.xml:/home/ozwcp_user/open-zwave-control-panel/zwcfg_0xecbef344.xml openzwave/openzwave-control-panel

and everything seemed to download and run OK but when I tried to open the control panel at port 8008 at the IP address of my Debian machine I get an error:

ex

Am I missing something in that run command? Obviously I am but I’m not sure what it would be. The instructions at the docker hub for that image are a little sparse.

And just to clarify that docker container should contain the version of OZWCP in order to set the parameters of the newer devices (v1.6)?

9

No reason why you shouldn’t get openzwave frontend when running in docker.

Try running without mapping files to see if you can get frontend. Also, check log for detailed error

10

Thanks for all the comments. Aeotec support and you guys hit the nail on the head. SoundSwitch is required for tones so will have to wait for the upgrade. I suppose I could upgrade myself but would just rather wait for official support.

Thanks everyone!

11

Yes, i generally agree with you. Hence, my question.

Nope. Same error.

here is the latest docker run command:

sudo docker run -d --name="ozw-cp" -p 8008:8008 --device=/dev/ttyUSB-ZStick-5G openzwave/openzwave-control-panel

here are the logs:

2019-07-18 04:18:14.341 Error, Cannot find a path to the configuration files at ./config/, Using /etc/openzwave/ instead...
2019-07-18 04:18:14.341 Info, Reading /etc/openzwave/options.xml for Options
2019-07-18 04:18:14.342 Warning, Failed to Parse options.xml: Failed to open file
2019-07-18 04:18:14.342 Info, Options:
2019-07-18 04:18:14.342 Info, 	appendlogfile: false
2019-07-18 04:18:14.342 Info, 	associate: true
2019-07-18 04:18:14.342 Info, 	assumeawake: true
2019-07-18 04:18:14.342 Info, 	autoupdateconfigfile: true
2019-07-18 04:18:14.342 Info, 	configpath: /etc/openzwave/
2019-07-18 04:18:14.342 Info, 	consoleoutput: true
2019-07-18 04:18:14.342 Info, 	customsecuredcc: 0x62,0x4c,0x63
2019-07-18 04:18:14.342 Info, 	drivermaxattempts: 5
2019-07-18 04:18:14.342 Info, 	dumptriggerlevel: 1
2019-07-18 04:18:14.342 Info, 	enablesis: true
2019-07-18 04:18:14.342 Info, 	enforcesecurereception: true
2019-07-18 04:18:14.342 Info, 	exclude: 
2019-07-18 04:18:14.342 Info, 	include: 
2019-07-18 04:18:14.342 Info, 	includeinstancelabel: true
2019-07-18 04:18:14.342 Info, 	interface: 
2019-07-18 04:18:14.342 Info, 	intervalbetweenpolls: false
2019-07-18 04:18:14.342 Info, 	language: 
2019-07-18 04:18:14.342 Info, 	logfilename: OZW_Log.txt
2019-07-18 04:18:14.342 Info, 	logging: true
2019-07-18 04:18:14.342 Info, 	networkkey: 
2019-07-18 04:18:14.342 Info, 	notifyondriverunload: false
2019-07-18 04:18:14.342 Info, 	notifytransactions: false
2019-07-18 04:18:14.342 Info, 	performreturnroutes: false
2019-07-18 04:18:14.342 Info, 	pollinterval: 30000
2019-07-18 04:18:14.342 Info, 	queueloglevel: 9
2019-07-18 04:18:14.342 Info, 	refreshallusercodes: false
2019-07-18 04:18:14.342 Info, 	reloadafterupdate: AWAKE
2019-07-18 04:18:14.342 Info, 	retrytimeout: 10000
2019-07-18 04:18:14.342 Info, 	saveconfiguration: true
2019-07-18 04:18:14.342 Info, 	saveloglevel: 8
2019-07-18 04:18:14.342 Info, 	securitystrategy: SUPPORTED
2019-07-18 04:18:14.342 Info, 	suppressvaluerefresh: false
2019-07-18 04:18:14.342 Info, 	userpath: 
2019-07-18 04:18:14.342 Always, OpenZwave Version 1.6.-1 Starting Up
2019-07-18 04:18:14.350 Info, Loading Localization File /etc/openzwave/Localization.xml
2019-07-18 04:18:14.352 Info, Loaded /etc/openzwave/Localization.xml With Revision 6
2019-07-18 04:18:14.352 Always, Using Language Localization 
2019-07-18 04:18:14.355 Info, Loading NotificationCCTypes File /etc/openzwave/NotificationCCTypes.xml
2019-07-18 04:18:14.355 Info, Loaded /etc/openzwave/NotificationCCTypes.xml With Revision 9
webserver starting port 8008

Seems to be missing the configuration files but that’s my question.

@Fishwaldo

What is needed for the configuration files in the docker command?

12

I had this same error but cannot remember cause and unable to verify on my server today.

I think maybe caused by folder permission issue but this is long shot guess. Also possible more simple and just need to map /etc/openzwave.

13

The Dockerfile is a little rough, and it was running the ozwcp binary from the wrong directory. I’ve created a pull request to fix it (maybe it will be accepted). You can build your own image by cloning my fork (or download the files) and running docker build (see pull request for instructions) in the ozw-controlpanel directory.

image
image1357×700 58.7 KB

14

I’ve never done any docker builds so pardon my questions to clarify…

I create a “ozw-controlpanel” directory in the machine where i want to download the files (in my case it would be “/home/finity/docker/ozw-controlpanel”), cd to it and clone the repo there?

then while still in that directory I run the docker build command?

sudo docker build -t ozwcp

then I can run the docker run command from anywhere or do I still have to be in that same directory?

And I would still need to bind my ozwcfgxxx and options.xml files from HA config to the container, is that correct? If not then how would ozwcp know which info to modify and which security key to use?

Thanks for the help.

15

Actually, the official docker image is serviceable if you run a bash shell instead of the default ozwcp. That is probably easier than building your own. You’ll need to bind mount the location of your config files and tell ozwcp to use a different directory to read the user files. Assuming $PWD contains your options.xml:

sudo docker run -it --name="ozw-cp" -v $PWD:/config -p 8008:8008 --device=/dev/serial/by-id/usb-0658_0200_E2061B02-4A02-0114-3A06-FD1871291660-if00:/dev/zwave --entrypoint /bin/bash openzwave/openzwave-control-panel

This will start the container in a bash shell, instead of running ozwcp and your options.xml file will be available at /config. You can then start ozwcp manually from the correct directory, with the user path:

[ozwcp_user@b00ec5616e2e ~]$ cd open-zwave-control-panel
[ozwcp_user@b00ec5616e2e open-zwave-control-panel]$ ./ozwcp -p 8008 -u /config
2019-07-18 18:26:43.719 Error, Cannot find a path to the configuration files at ./config/, Using /etc/openzwave/ instead...
2019-07-18 18:26:43.720 Info, Reading /etc/openzwave/options.xml for Options
2019-07-18 18:26:43.720 Warning, Failed to Parse /config/options.xml: Failed to open file
...
2019-07-18 18:27:04.906 Info, 	userpath: /config/
2019-07-18 18:27:04.906 Always, OpenZwave Version 1.6.-1 Starting Up
2019-07-18 18:27:04.919 Info, Loading Localization File /etc/openzwave/Localization.xml
2019-07-18 18:27:04.921 Info, Loaded /etc/openzwave/Localization.xml With Revision 6
2019-07-18 18:27:04.921 Always, Using Language Localization 
2019-07-18 18:27:04.925 Info, Loading NotificationCCTypes File /etc/openzwave/NotificationCCTypes.xml
2019-07-18 18:27:04.926 Info, Loaded /etc/openzwave/NotificationCCTypes.xml With Revision 9
webserver starting port 8008

ozwcp will write the logs to /config (host’s $PWD) as well as the cache file. Note that the cache file in 1.6 is named ozwcache*.xml instead of zwcfg*.xml. I don’t know if it will try to upgrade from an old cache file so you might have to repopulate it. I also don’t know if the options file is the same between versions, but in the container it looks like there is a default version at /etc/openzwave/options.xml.

16

Anyone succes with setting the volume ?
I ran the openzwave-control-panel. Thanks to @freshcoast instructions.

But I can’t seem to be able to set anything.
I can see the settings

I see the default is 100 so i’m assuming the volume has to be set between 0 and 100.
But when i submit 50 as the volume to set, i get the following

So not sure what to do here.

I’m also getting a browser error. Not sure if this is the problem

I hope somebody can help because the volume is just way to loud. Not really necessary for neighbours four houses down the road to hear when somebody is at our door :wink:

17

+1 I’ve looked into the parameters, I’m not sure the “quick fixes” showing all the node entities correspond to the 1st specs provided by Aeotec, or their 2nd version (which seems to incorporate volume)
Also to follow up on Aeotech ZW162 Doorbell
=> seems OZW 1.6 will be the answer when it’s integrated into HA

18

Did you manage to figure this out?

19

Waiting for next version zwave. Should take care of most of this

20

Hi all,

just to let you know that I have changed the volume using Homeseer software on windows. then I plug the stick back to hassio…

hope it helps

1 Like
21

These are the instructions I used. I unplugged the Z-Wave stick, put it in the PC and ran Z-Wave PC Controller, set the doorbell then put everything back - at least my volume is ok now :slight_smile:

http://s000.tinyupload.com/index.php?file_id=06495144458054382305 (Link to software)

"This is how its done via a another controller via Z wave PC controller software

Mute tamper sound.
Command Classes: “COMMAND_CLASS_MULTI_CHANNEL_V2 (or higher V?)”
Command Name: “MULTI_CHANNEL_CMD_ENCAP”

Input these Values:
Source End Point: 00 // leave as default
Res: 00 //Don’t touch this, this does nothing.
Destination Endpoint: 02 // Tamper Switch endpoint of Siren or Doorbell 6, you can use this to control sound of your button or other alarm options
· Endpoint 02 - Tamper Alarm sound
Bit address: 00
Command Class: 79 //Sound Switch Command Class
Command: 05 //Sound Switch Configuration Set Command
Parameter: 00 01 //Volume #5 (as 05) Sounds #01 (as 01)

Change door bell sound and volume

Command Classes: “COMMAND_CLASS_MULTI_CHANNEL_V2”
Command Name: “MULTI_CHANNEL_CMD_ENCAP”

Input these Values:
Source End Point: 00 // leave as default
Res: 00 //Don’t touch this, this does nothing.
Destination Endpoint: 03
· Endpoint 03 - Button #1
Bit address: 00
Command Class: 79 //Sound Switch Command Class
Command: 05 //Sound Switch Configuration Set Command
Parameter: 28 01 //Volume 40% (as 28 in hex) Sounds #01 (as 01)
· Volume is a range between 00 - 65 (in hex which is 0 - 100 in decimal or easily seen as 0 - 100%)
Sound can be a range between 00 - 1E (or decimal value of 1 - 30 or sound #1 - 30)."

1 Like
22

Wow, where did you find all of that information?

Do you know of anyway to set the doorbell to send different ring tones and/or events based on which one of two buttons are paired to it?

right now I have two buttons but the sound the same tone and send the same event. It makes it hard to figure out which door someone is at.

23

HI, lots of google searching!
I’m not sure about the 2 button thing as I only have 1. Perhaps the spec will tell you if that’s a possibility. I’m sure with the notations in the spec you should be able to relate that to my instructions and work out how to do it (if it’s possible).

24

I Looked at the spec, and it looks like Endpoint 3 is remote 1, and Endpoint 4 is remote 2, so I would assume that individual tones and volumes could be set by specifying the appropriate endpoints when sending commands via Z-Wave to the doorbell6.

25

I had read the tech manual a while back and saw those endpoints but I wasn’t smart enough :wink: to dig thru the hex codes and break down what parts needed sent for which functions.

Maybe I’ll give it another try when I get a chance.

26

In case anyone needs, I opened the doorbell button and took some pictures.
I then soldered wires for my actual doorbell button.
Aeotec Doorbell (ZW166) button disassembled

27

lol… did kind of the same… i fried them aeotec button doing so :slight_smile:

how did you connect it? i wanted to have my doorbell button to do both electrical and doorbell 6 ringing… made a mistake on current predictions