RaZberry 7 Pro Firmware
Re: RaZberry 7 Pro Firmware
Please show the Z-Way log
Re: RaZberry 7 Pro Firmware
Here you go.... (this is right after start of the Rpi, log file was removed before restart)
-
- Posts: 174
- Joined: 02 Mar 2020 22:41
Re: RaZberry 7 Pro Firmware
Based on the log file, it's clear your controller is definitely not happy:
[2022-04-19 12:07:52.611] [D] [zway] Opened device: /dev/ttyAMA0
[2022-04-19 12:07:52.611] [i/o] Setting port speed to 115200
[2022-04-19 12:07:52.611] [D] [zway] Worker thread successfully created
[2022-04-19 12:07:52.611] [D] [zway] Worker thread entry point
[2022-04-19 12:07:52.612] [zway] Adding job: Get controller info and supported function classes
[2022-04-19 12:07:52.622] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:52.823] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:52.823] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:53.025] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:53.025] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:53.226] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:53.226] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
There are several possible explanations, from an unresponsive controller, dead controller, incorrect/poor seating of the controller and /dev/ttyAMA0 serial port contention. To troubleshoot the problem, do a full controller reset by fully powering off your Pi. Don't just do a reboot, remove power, confirm the controller card is installed correctly, and then re-apply power. There are 2 LEDs on the controller - did both LEDs turn on and then turn off after 2 seconds? If not, then you probably have a dead controller. @PoltoS might have suggestions on what to do if the LEDs do not turn on and then turn off.
With the Pi re-booted, check the z-way-server log file to see if you're still getting No ACK timeout errors shortly after you see: "Opened device: /dev/ttyAMA0". With luck, you had an unresponsive controller and power-cycling the controller solved the problem. If you still see the No ACK error messages, then a possible cause is some other process is trying to use the serial port. Run: "sudo lsof -n | grep AMA0". You should see a single z-way process (with multiple threads). If the lsof command shows another process, you have a configuration error (e.g., bluetooth or console port trying to use the serial port) that you will need to fix ( e.g., /boot/config.txt or /boot/cmdline.txt has to be updated).
[2022-04-19 12:07:52.611] [D] [zway] Opened device: /dev/ttyAMA0
[2022-04-19 12:07:52.611] [i/o] Setting port speed to 115200
[2022-04-19 12:07:52.611] [D] [zway] Worker thread successfully created
[2022-04-19 12:07:52.611] [D] [zway] Worker thread entry point
[2022-04-19 12:07:52.612] [zway] Adding job: Get controller info and supported function classes
[2022-04-19 12:07:52.622] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:52.823] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:52.823] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:53.025] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:53.025] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2022-04-19 12:07:53.226] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2022-04-19 12:07:53.226] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
There are several possible explanations, from an unresponsive controller, dead controller, incorrect/poor seating of the controller and /dev/ttyAMA0 serial port contention. To troubleshoot the problem, do a full controller reset by fully powering off your Pi. Don't just do a reboot, remove power, confirm the controller card is installed correctly, and then re-apply power. There are 2 LEDs on the controller - did both LEDs turn on and then turn off after 2 seconds? If not, then you probably have a dead controller. @PoltoS might have suggestions on what to do if the LEDs do not turn on and then turn off.
With the Pi re-booted, check the z-way-server log file to see if you're still getting No ACK timeout errors shortly after you see: "Opened device: /dev/ttyAMA0". With luck, you had an unresponsive controller and power-cycling the controller solved the problem. If you still see the No ACK error messages, then a possible cause is some other process is trying to use the serial port. Run: "sudo lsof -n | grep AMA0". You should see a single z-way process (with multiple threads). If the lsof command shows another process, you have a configuration error (e.g., bluetooth or console port trying to use the serial port) that you will need to fix ( e.g., /boot/config.txt or /boot/cmdline.txt has to be updated).
Re: RaZberry 7 Pro Firmware
Thanks for all these tips, I checked all of them.
What I can see is when I " switch" controller to the PRO7 is this:
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
z-way-ser 391 root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 515 Optimizin root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 516 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 517 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 518 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 519 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 520 zway/core root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 539 zway/webs root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 540 zway/time root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 2304 zway/dev/ root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
So, you can see it tries (for a second or 3, 4) and then, when I do the grep again, nothing....
After checking connections and powercycle, I do see the 2 leds going on and then off, so that looks good.
It cannot be that the old controller (UZB on USB) is in the way right ?
What I can see is when I " switch" controller to the PRO7 is this:
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
z-way-ser 391 root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 515 Optimizin root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 516 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 517 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 518 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 519 v8:Sweepe root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 520 zway/core root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 539 zway/webs root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 540 zway/time root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
z-way-ser 391 2304 zway/dev/ root 7u CHR 204,64 0t 0 136 /dev/ttyAMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
pi@raspberrypi:~ $ sudo lsof -n | grep AMA0
So, you can see it tries (for a second or 3, 4) and then, when I do the grep again, nothing....
After checking connections and powercycle, I do see the 2 leds going on and then off, so that looks good.
It cannot be that the old controller (UZB on USB) is in the way right ?
Re: RaZberry 7 Pro Firmware
Can you check please if the chip heats up? Can you hold the finger on it?
Re: RaZberry 7 Pro Firmware
How can I get which firmware version my 7 pro currently have?
Z-Way shows:
Is that right place to look at?
Z-Way shows:
Code: Select all
Firmware version v3.2.3
UI version v1.13.5
Re: RaZberry 7 Pro Firmware
That is the Z-Way software. Go into Expert, Network, Controller Info and then click Firmware Update near the bottom.
Re: RaZberry 7 Pro Firmware
Yes ;(
Please ask your shop for a replacement
Please ask your shop for a replacement