stuiow wrote:
What z-wave controller do people recommend? The Razberry2 or the Aeon z-wave stick s2?
I have the z-stick s2 on a PI3, this was a no brainer... Being able to include peripherals key unplugged (includes a battery) also proves useful, except using some chinese neo coolcam products that does not include properly this way (you'll get IDs at 0, but as it's battery powered devices that are concerned you can bring them close to z-stick+PI & include from domoticz, only way to get a full inclusion on these ones).
As well, on the device side it's seen as a ttyUSB. So no specific kernel driver (a source of hassle) needs in Linux, it's seen as a serial to usb adapter already managed in standard, to drive it from open zwave library.
You'll only have to make allocated /dev/ttyUSBn with n=fixed nb (see wiki). Otherwise, when unplugging to include, at replug you'll not get the same device path (n will become n+1) & it'll not be seen by domoticz configured using previous dev path.
The only issue I experienced was a default configuration one in domoticz combined with my z-wave network use at the beginning: I only had modules driving heaters, on schedule (no modules reporting statuses/temperatures on their own & quite frequently), leading to z-wave unused for up to several hours.
Domoticz have a timeout on the controller device that cause problems when such conditions are met: 60s with no traffic = domoticz soft-resets the z-stick, probably thinking it's firmware is hanged. So the z-stick have to restart, rebuild it's z-wave mesh network topology, re-read devices parameters: This was about 30s with z-wave network rebuild every 60s, so unable to send command.
And when a scheduled setup was sent, there was about 50% chance for a fail... So take care of this setup.
After setting this timeout to several hours (more than the max delay between 2 schedules), that's rock solid. I started using domoticz 3 month ago, since last update I'm about a month of uptime.
