No control of Z-Wave in Domoticz after certain time

[SVdHeyden]

This item is already added quite often and disappear after some days.

Configuration:
Hardware:

• Cubie board
  Zwave USB stick: Aeotec Z-Stick S2

Software:

• Armbian 5.73 Linux 9 Stretch (4.19.25-Sunxi
  Domotcz version 4.10717 build hash: b38b49e5
  OZW USB Version:1.4-3335-g74e05982-dirty (don't know what 'dirty' means but it was there al the time)

After a few days Domoticz isn't able to control Z-wave devices anymore. commands are sent but nothing happens.
After a restart of the Domoticz server (not a reboot of Linux) and the removal of the file Domoticz/Config/zwcfg_****.xml the system is working again for a few days. This I have put in a Crontab as a work around however sometimes after a restart of the Dooticz server (procedure as given above) the server isn't finding the USB Zwave controler. This has nothing to do with the serial port used by the USB controller as this is configured as given in the wiki page.

This problem started in the previous version of Domoticz. The version before the previous version I didn't have this problem. System was running for years without any issue. It is not due to hardware issues as I have the issue on different hardware platforms.


As the version befor previous version was according to me stable is there a way to do a fallback to that version?
What kind of information can I deliver to solve the issue in current version?

Hope that this will not be deleted after a while... I hope that somone can help.
Currently I'm looking to other sollutions as this system is not workable anymore and the support ....

Thanks anyway

[SVdHeyden]

Is there someone out there to tell me how to install a previous version of Domoticz?

Thanks

[philchillbill]

You need to have saved the installer for an older version somewhere as the historical downloads are not kept on the Domoticz website download area.

Every time I install a beta via sudo ./updatebeta, I also download the zip and save it in a folder with the version number added to the zip name. That way, I have a personal stash of old betas to go back to if something breaks.

I only have these for the Linux versions as I don’t use a pi for Domoticz but a NUC. If an older recent Linux is any good to you then PM me.


Sent from my iPhone using Tapatalk

[SVdHeyden]

Philchillbill,

Thanks for your reply.

Actually I'm looking to a previous stable version like the one where I didn't percieve the current issue. So I'm looking for version 3.8153 of July 30th 2017

Good idea to store earlier versions localy, Something I will do in the future as well.

Thanks

[SVdHeyden]

As a fall back to previous versions is not an option a sollution is needed for the current version.

Until know no suggestions or additional question to try to solve this behaviour in the current Domoticz version.

As said i'm willing to provide the necessary info (logs, etc.) for investigation.

I've a strong feeling that the problem is related to the USB connection with the Z-wave controller (Aeotec Z-Stick S2).
Why?
As mentioned in the first message I'm restarting the Domoticz service every night at 00:00

• Stop the Domoticz service
  remove the file Zwcfg_***.xml file
  Restart the Domoticz service

Quite often the Z-wave devices are not visualised in the hardware tab. The USB device is visualised however the setup button remains 'red'
pressing the setup button the following window doesn't contain any Z-wave device
When going back and change the USB port to the physical port and changing it back to the Symbolic link then the z-wave devices are appearing.
Then Domoticz is running for 2 à 3 days and the issue appears again.

Is there someone out there who is able to give some support?

Thanks

[EddyG]

I had some USB related problems too with 2 RFLinks.
It was a race at bootup.
Did you set your usb ports in /etc/udev/rules.d
And if so how does it look like.

[SVdHeyden]

Hi Eddy,

Thanks for your resonse

Indeed I'm using a udev rule

Launching the command ls -l /dev/ttyUSB*
I get the following:
/dev/ttyUSB0
/dev/ttyUSB0 -> ttyUSB0

The rule itself is as follows:

The rule itself is called: 11-zwave_controller.rules
and it contains the following rule:

Code: Select all

SUBSYSTEM=="tty", /
 SUBSYSTEMS=="usb", /
  ATTRS{idVendor}==10C4",/
  ATTRS{serial}=="0001",/
  ATTRS{idProduct}=="ea60",/
  SYMLINK+="ttyUSB21",/
  OWNER="smarthome",/
  Group="dailout"

[EddyG]

For what is the symlink "/dev/ttyUSB0 -> ttyUSB0" needed for.
Could it be removed?
Mine looks like:

Code: Select all

crw-rw---- 1 root dialout 188, 0 Nov  3  2016 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jun 13 08:52 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jun 13 05:54 /dev/ttyUSB2
lrwxrwxrwx 1 root root         7 Nov  3  2016 /dev/ttyUSB_P1 -> ttyUSB0
lrwxrwxrwx 1 root root         7 Nov  3  2016 /dev/ttyUSB_RFL -> ttyUSB2
lrwxrwxrwx 1 root root         7 Nov  3  2016 /dev/ttyUSB_SOM -> ttyUSB1

Code: Select all

SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{devpath}=="1.1.3", SYMLINK+="ttyUSB_P1"
SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ATTRS{devpath}=="1.1.2", SYMLINK+="ttyUSB_RFL"
SUBSYSTEM=="tty", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="7523", ATTRS{devpath}=="1.3", SYMLINK+="ttyUSB_SOM"

On the raspberry where I have my Zwave stick it is:

Code: Select all

crw-rw---- 1 root dialout 188, 0 Jun 13 08:49 /dev/ttyUSB0
lrwxrwxrwx 1 root root         7 Nov  3  2016 /dev/ttyUSB_ZIG -> ttyACM1

Code: Select all

SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", ATTRS{serial}=="__0X00124B0012023155", SYMLINK+="ttyUSB_ZIG"

A totally different vendor, product and serial, and the stick connects to ttyACM1.
Was it always on your Cubieboard that it connects to ttyUSBx? Perhaps try an other port.

[SVdHeyden]

Hi,

That's a typo

Launching the command ls -l /dev/ttyUSB*
I get the following:
/dev/ttyUSB0
/dev/ttyUSB0 -> ttyUSB21

As specified in the udev rule.

The reason of this symlink is when the board is restarted than the zwave controller can change from USB port therefore the symlink is needed.

But indeed I can change the symlink to something else than USB21

I will try this

Thanks

[flokkie]

FYI, you are not alone. I have the same issues after the installation of 4.10717. Running on a NAS, with an Aeon XW090 Gen5 stick. It looks like Domoticz doesn't see the feedback from devices. It tells me a light is out, while it's still on. Never had that on previous versions. Can't go back to a previous version, 1 Z-wave device was not detected in previous versions. So I won a detected device, but lost stability Hopefully this is resolved in the next release. I don't dare to go to beta, heard some complaints about the new open Z-wave....

Regards,

Folkert

[SVdHeyden]

Hi, flokkie,

Strange that the developpers are not asking for logfiles etc. to investigate the issue. I've a strong feeling that Domoticz is loosing the connection with the USB zwave controller for one or the other reason.

If the developpers are not asking for detailed information needed to investigate the root cause I'm not confident that the issue will be solved in next release. By the way I had already the same behaviour in previous release.

Any way thanks for your reply.

The more people replying on this issue the higher the visibility of the issue.

[EddyG]

My Zwave stick is working fine. It is a Aeotec ZW090 Z-Stick Gen5 EU
But create an issue on https://github.com/domoticz/domoticz/issues
Then it will be really noticed.

[SVdHeyden]

Eddy,

Ok thanks

I will look into that

Greetings