Domoticz

Hi,

I've been using Domoticz for quite a while now, with the RaZberry Z-Wave controller, without any problem. Great product!

Currently I'm installing a new system, with all the latest software, for a new project.
I'm using:
- Raspberry Pi 3
- Domoticz v3.4834 (latest stable)
- RaZberry board
- Raspbian Jessie 8.0 (kernel 4.1.18-v7+)

Like I did with the currently working installation, for use with the RaZberry, I configured the following:
- created /etc/udev/rules.d/09-tty.rules with content 'KERNEL=="ttyAMA0", SYMLINK+="ttyUSB20"'
- created link ln -s /dev/ttyAMA0 /dev/ttyUSB20
- added OpenZwave USB to Domoticz

Also, after some searching, I've made the following modifications - this is different from Wheezy:
- remove "console=ttyAMA0,115200" from /boot/cmdline.txt
- systemctl disable [email protected]
- sudo systemctl mask [email protected]

After a reboot, the RaZberry still doens't work as it should. Icon stays red.

Errors in Domoticz log:
OpenZWave: Received timeout notification from HomeID: 0, NodeID: 255 (0xff)
Errors in OZW log:
Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)

Does anybody know what else should/could be done? Is there something I'm missing?

thanks a lot!!!

I do not have this setup but did read about the serial port on the PI3 header not being compatible with the PI2. Something about remapping the port and the new bluetooth module. Do a search and you will find more info.
Example https://openenergymonitor.org/emon/node/12311

Hi,

1/
Apparantly the 'fix' is available in kernel 4.1.19:
- in /boot/config.txt, add to end: dtoverlay=pi3-disable-bt
- Disable BT modem: sudo systemctl disable hciuart
This "should" work, but sincesudo apt-get dist-upgrade doens't have the 4.1.19 available so it seemd, I had to resort to another option:

2/
So here's what I tried: http://www.briandorey.com/post/Raspberr ... Workaround
Basically tried to remap the pins to the previous (pi2) layout:
- Change /boot/cmdline.txt to
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 kgdboc=serial0,115200 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
- In /boot/config.txt, add to end: dtoverlay=pi3-miniuart-bt-overlay (first DL file from URL above)
- Disable BT modem: sudo systemctl disable hciuart
- In /lib/systemd/system/hciuart.service, replace all ttyAMA0 with ttyS0
Unfortunately, whatever combination or configuration I tried, the same errors kept popping up - no RaZberry
So, last resort, I had to do this:

3/
In http://forum.z-wave.me/viewtopic.php?f=3422&t=22957 it is suggested to just disable the Jessie device tree:
raspi-config --> Advanced --> Device Tree --> disable
After a reboot the Razberry WORKS! YEAH! (I rolled back all other changes I made in 1) and 2) - so this workaround works or should work from a freshly installed Raspbian 8/4.1.19)
BUT, as the post said, I loose the onboard Wifi

So, for the time being, I can go forward with my config, but I'm hoping really bad that there will be a 'fix' for this problem.
So as soon as I can install this 4.1.19 I'll give it another try...

This is not Domoticz related of course, just wanted to provide some info.

Rgds all

I followed the following article:
http://domoticanoob.nl/razberry-met-raspberry-3/

Install rpi-update to get the latest update and run it.

sudo apt-get install rpi-update
sudo rpi-update

sudo nano /boot/config.txt
add to end of the file:
dtoverlay=pi3-disable-bt

sudo systemctl disable hciuart
sudo reboot

For me the RaZberry is detected and wifi works..

sudo rpi-update
that's the one I 'forgot' to update kernel... thanks!
working now...

Does this disable the Bluetooth functionality ?

Yes

Rolo wrote:I do not have this setup but did read about the serial port on the PI3 header not being compatible with the PI2. Something about remapping the port and the new bluetooth module. Do a search and you will find more info.
Example https://openenergymonitor.org/emon/node/12311

I've experienced the same problem as the topicstarter.

After remapping the Bluetooth port, it works like a charm!

I tried upgrading the raspbian from wheezy to Jessie I order to migrate to new Raspberry PI3 but after removing Sd card from rpi2 and putting into rpi3 I wouldn't boot up. I had to put it back to rpi2 and now I am having similar issues albeit on Rpi 2 whereby my razberry is not functioning.
I will follow these steps to see if the above makes any difference. In the meantime, has anyone been able to migrate from pi2 to pi3 without reinstall of rapsbian?

that is correct
you can download the new sd card image with domoticz from sourceforge
install this, transfer your old domoticz folder, and you should be done

@gizmocuz that's if there was only domoticz installed but in reality I have other stuff so this is why I ideally wanted to just upgrade the raspbian from the Jessie repo.

Anyway, this topic is about problems with razberry and Pi3 but that's still ahead of me.

What you can try....

Clone your upgraded raspberry pi 2 jessie sdcard.
copy the contents of the boot folder (the fat32 folder) of the jessie version that you can download from the raspberry pi foundation
Maybe the problem is only with booting

But of course you only run domoticz only on your raspberry pi... !

hi @smartastic, I am exactly in the same situation as your, the same HW / SW configuration. I followed a lot of reply to your post but without success.
did you solved ? any suggestion ?

many thank, Mario

What I found to fix the problem, by default Raspbian is using serial port as console terminal port. Upgrade process must have re-set this.
To disable that function start raspi-config tool:

sudo raspi-config
Go to “8.Advance Function menu” , then “A8.Serial” and select “No” to disable shell terminal on the serial port.
Then:
sudo shutdown -r now

My RaZberry started working again so try this.

Luckily, my setup worked first time. Like free_nsc, I had disabled the serial console, but also followed the advice on the Vesternet website, and created a symlink from /dev/ttyAMA0 to /dev/ttyUSB20. Then choose 'OpeWaveUSB' as the device, and select /dev/ttyUSB20 as the serial port.

Perhaps I spoke too soon. I'm having problems with nodes appearing to be dead, and a reboot of the pi fixes it. Anybody else having 'dead nodes' problem?

Setup: RPi3, RaZberry, Jessie, and three TKB dimmers.

evansnp wrote:Perhaps I spoke too soon. I'm having problems with nodes appearing to be dead, and a reboot of the pi fixes it. Anybody else having 'dead nodes' problem?

Setup: RPi3, RaZberry, Jessie, and three TKB dimmers.

Yes... But it seems a lot more stable this week, apart from the random meter types I get now & again (My RaZBerry sees my Fibaro RGBW reports water meter, gas meter, and now wind as well occaisonally).

Most of my dead node issues come when I move stuff around. Probably as I get more devices that will go away.

H

I have bought a Raspberry pi 3 with a RazBerry board. But so far all my attempts to make it work has failed. I've never gotten to include any of my devices.

I've followed all the guides and tips found.

I've tried:

Using /dev/ttyAMA0 directly from Domoticz when settingup the OpenZwave USB hardware. This will sometimes find the Razberry controller, but after a reboot it will fail - and I am unable to add any nodes.

I've tried to create a symlink from /dev/ttyAMA0 to /dev/USB20, again, I've gotten it to register the Razberry a few times, but never been able to add nodes, and again, after a reboot it will stop working again.

Also, will all the different tips out there I am confused as what is nessesary steps to make it work.

So I am hoping someone with a RPi3 and a Razberry board could help me walk through the steps needed to make it work.

Hi SuneRadich. Did you by any chance install the z-way software too? If so, it is probably set to launch on boot, and taking ownership of /dev/ttyAMA0. You can try stopping it by issuing 'sudo service z-way-server stop', then 'sudo service domoticz restart'. Did you disable the serial console in 'raspi-config'? The only other thing that I did was to perform a 'raspi-update', but that was to fix a wifi issue, where it wouldn't see CH13.

No, I did not install the z-way software.

But as a matter of fact, I have it working now. The weird part is, that I have no idea what made it work. I've completely reinstalled a fresh sdcard image four times, and have more or less made the same changes each time. But because of that, I dont really know exactly what I did different this time around.

I just hope that it stays working