Have I got a broken z-Net

[randy]

Thanks, that's it - gpio is in /usr/local/bin rather than /usr/bin. I'll update that.

Yeah, looks like your shed one doesn't have the fixes.

I'll do that, but for the record I have had 0 problems with Z-Nets staying up, remaining connected or connecting on startup since we went through the 1.0.17-1.0.21 fiasco. I attribute that to using high quality SD cards as well as the patches. Before changing to Samsung EVO cards, they would occasionally corrupt on a power cycle. Not too often, but maybe 2-3 times over a year.

The only reason my kitchen Z-Net was replaced is because of a problem in the GPIO card and that problem only surfaced with Z-Wave backup/restore attempts. It would back up fine, but restore would fail 75% of the time. It had a rev D GPIO.

[zwolfpack]

Scripts updated.

My production unit is chugging right along, four months & counting!

pi@Z-Not:~ $ uptime
19:42:29 up 122 days, 20:44, 1 user, load average: 0.00, 0.00, 0.00

[ScottRennie]

Are you familiar with PuTTY? That is the easiest way to SSH in from a PC. http://www.putty.org/

To login, try pi@<znet ip addr> with password raspberry

Once logged in, download the zipfile from the previous message by pasting this to the command line:

wget 'https://forums.homeseer.com/attachment.php?attachmentid=65791&d=1515641659' -O znetcare.zip

unzip to a folder named znetcare:
unzip znetcare.zip -d znetcare

change to the folder and run the first script:
cd znetcare
./znet_info.sh

Then preview the patch commands:
./znet_patch.sh

Ignore this - I'm in!

[ScottRennie]

OK, here's the results:

pi@zBrockhill:~/znetcare $ ./znet_info.sh

Z-Net version 2 revision 1.0.23

External (UZB) device detected.

ser2net port 2001 timeout (seconds): 0 - (per rev. 1.0.18 and prior, and 1.0.23) - not recommended (timeout disabled)
Your installed ser2net contains the patch added in rev. 1.0.21/1.0.22.

pi@zBrockhill:~/znetcare $ ./znet_patch.sh
Note: This is a Z-Net v2, firmware revision 1.0.23
Note: superuser (root) privilege required to install this patch -
Note: displaying commands that would be run by superuser.
Note: /etc/ser2net.conf modifications (< old; > new):
86,87c86,87
< 2001:raw:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
< 2002:raw:0:/dev/ttyUSB0:19200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
---
> 2001:raw:120:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
> 2002:raw:120:/dev/ttyUSB0:19200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
89c89
< #3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner
\ No newline at end of file
---
> #3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner
Note: backing up existing /etc/ser2net.conf...
install -p /etc/ser2net.conf /etc/ser2net.conf-orig
Note: installing patched /etc/ser2net.conf...
install -p -t /etc ser2net.conf
rm -f ser2net.conf
Note: patched ser2net binary is already installed - no action.
pi@zBrockhill:~/znetcare $


Does this make sense?

Scott

[zwolfpack]

OK, here's the results:

pi@zBrockhill:~/znetcare $ ./znet_info.sh

Z-Net version 2 revision 1.0.23

External (UZB) device detected.

ser2net port 2001 timeout (seconds): 0 - (per rev. 1.0.18 and prior, and 1.0.23) - not recommended (timeout disabled)
Your installed ser2net contains the patch added in rev. 1.0.21/1.0.22.

pi@zBrockhill:~/znetcare $ ./znet_patch.sh
Note: This is a Z-Net v2, firmware revision 1.0.23
Note: superuser (root) privilege required to install this patch -
Note: displaying commands that would be run by superuser.
Note: /etc/ser2net.conf modifications (< old; > new):
86,87c86,87
< 2001:raw:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
< 2002:raw:0:/dev/ttyUSB0:19200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
---
> 2001:raw:120:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
> 2002:raw:120:/dev/ttyUSB0:19200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS
89c89
< #3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner
\ No newline at end of file
---
> #3001:telnet:600:/dev/ttyS1:19200 8DATABITS NONE 1STOPBIT banner
Note: backing up existing /etc/ser2net.conf...
install -p /etc/ser2net.conf /etc/ser2net.conf-orig
Note: installing patched /etc/ser2net.conf...
install -p -t /etc ser2net.conf
rm -f ser2net.conf
Note: patched ser2net binary is already installed - no action.
pi@zBrockhill:~/znetcare $


Does this make sense?

Scott

Indeed it does. This shows that you have a European version with external UZB controller, and that the communication patch is not enabled.

The affected file is /etc/ser2net.conf. The lines prefaced with "<" and ">" show existing (<) and to-be-modified (>) entries. The entry used for the zwave communications is the one starting with 2001 (which is a port number).

< 2001:raw:0:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS

will be changed to

> 2001:raw:120:/dev/ttyACM0:115200 8DATABITS NONE 1STOPBIT -XONXOFF -RTSCTS

The difference is that the 3rd field (the timeout) is changed from 0 (disabled) to 120 (2 minutes).

If you run this script prefaced with sudo, the original file will be backed up and the modified file installed.

sudo ./znet_patch.sh

Then reboot.

[ScottRennie]

Looking good I think. Ran the patch with any problems and the scripts now report

pi@zBrockhill:~/znetcare $ ./znet_info.sh

Z-Net version 2 revision 1.0.23

External (UZB) device detected.

ser2net port 2001 timeout (seconds): 120 - recommended value
Your installed ser2net contains the patch added in rev. 1.0.21/1.0.22.
pi@zBrockhill:~/znetcare $ ./znet_patch.sh
Note: This is a Z-Net v2, firmware revision 1.0.23
Note: superuser (root) privilege required to install this patch -
Note: displaying commands that would be run by superuser.
Note: /etc/ser2net.conf already has recommended settings - no action.
Note: patched ser2net binary is already installed - no action.
pi@zBrockhill:~/znetcare $

I presume that's it all done.

I'll keep an eye on it and let you know how it's working.

Thank you again for your help - I would have been sending units back as faulty forever without your advice.

Cheers
Scott

[zwolfpack]

Great, that looks as expected. This should allow it to get reconnected easier.

[ScottRennie]

Great, that looks as expected. This should allow it to get reconnected easier.

Brilliant - thank you again.

Scott

[ScottRennie]

Bad news - this didn't fix the problem.

Any other ideas?

Scott

[zwolfpack]

Bad news - this didn't fix the problem.



Any other ideas?



Scott

What does the log show while it's trying to connect?


Sent from my iPad using Tapatalk

[ScottRennie]

What does the log show while it's trying to connect?

Here's some log entries:

2018-01-15 09:06:42 Z-Wave Error The plug-in attempted to make zBrockhill a SIS (Static Information Server) and it failed. No further information is available.
2018-01-15 09:06:28 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
2018-01-15 09:06:21 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
2018-01-15 09:06:11 Z-Wave Error zBrockhill: Exception transmitting to IP 192.168.0.150: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2018-01-15 09:03:38 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the controller capabilities - it may be disconnected or malfunctioning (3).

Does that mean anything to you?

It works after a cold boot

Scott

[zwolfpack]

You say the problem occurs after rebooting HS3. Does it also occur when cycling the Zwave plugin on the Plugins->Manage page?

From the log, post everything starting at the line "The Z-Wave Command Execution Thread was Started or Restarted", after the Zwave plugin starts. Below is a good startup.

You are still running this on wired Ethernet rather than Wifi, correct?

Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): ......................................................................
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): .............................. FINISHED ..............................
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): ......................................................................
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3) is the SIS for the network.
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3) There is a SUC/SIS in the network.
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3) Controller is static lib.
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3) Controller chip type is ZW050x.
Jan-15 7:50:29 AM	 	Z-Wave	The interface's security support has been set.
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Found 1 Z-Wave nodes in interface node ID 1 (UZB (Z-Not3))
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Z-Wave interface node ID: 1, Home ID: F2954E94
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Z-Wave Serial API version: 5
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Controller firmware version: 5.5
Jan-15 7:50:29 AM	 	Z-Wave	UZB (Z-Not3): Controller Manufacturer: PowerLynx, ID=0x1, Type=0x4
Jan-15 7:50:27 AM	 	Z-Wave	UZB (Z-Not3): Getting node information from controller...
Jan-15 7:50:27 AM	 	Z-Wave	UZB (Z-Not3): The Z-Wave API Execution Thread was Started or Restarted.
Jan-15 7:50:26 AM	 	Z-Wave	UZB (Z-Not3): Z-Wave Ethernet at IP 192.168.1.111, connected to interface ok.
Jan-15 7:50:26 AM	 	Z-Wave	UZB (Z-Not3): The Z-Wave Command Execution Thread was Started or Restarted.
Jan-15 7:50:26 AM	 	Z-Wave	UZB (Z-Not3): ----------------------------------------------------------------------
Jan-15 7:50:26 AM	 	Z-Wave	Initializing Z-Wave interface UZB (Z-Not3) (Ethernet Interface) at 192.168.1.111, port 2002
Jan-15 7:50:26 AM	 	Z-Wave	UZB (Z-Not3): ----------------------------------------------------------------------
Jan-15 7:50:26 AM	 	Z-Wave	UZB (Z-Not3): ======================================================================

[ScottRennie]

You say the problem occurs after rebooting HS3. Does it also occur when cycling the Zwave plugin on the Plugins->Manage page?

From the log, post everything starting at the line "The Z-Wave Command Execution Thread was Started or Restarted", after the Zwave plugin starts. Below is a good startup.

You are still running this on wired Ethernet rather than Wifi, correct?

Yes, cycling the p/i doesn't help. It needs the zNet to be rebooted before it will work. Restarting HS3 also doesn't fix it.

I will try to get more logs next time.

Yes, it's wired

Cheers
Scott

[zwolfpack]

Good. The main reason I asked that is that for testing its much easier/quicker to cycle the plugin vs. restarting HS3 or the PC.
I have a test system which is a Rpi and a UZB controller, same as that used on the Euro-znet except US frequency of course. This disconnects/reconnects without issue each time with the same config as you have as far as I can tell. So you may have a hardware issue with your unit after all But post the logs, that may shed some light on where things are breaking down.

[ScottRennie]

zWolfpack

Happened again this morning - stopped HS3, did a backup and restarted. Here's the gisy of the log...

==================================================
Jan-20 12:21:26 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.150...
Jan-20 12:21:25 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
Jan-20 12:21:06 Z-Wave Error zBrockhill: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (zBrockhill).
Jan-20 12:20:06 Z-Wave Error zBrockhill: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (zBrockhill).

Jan-20 12:19:22 Z-Wave zBrockhill: Getting node information from controller...
Jan-20 12:19:22 Z-Wave zBrockhill: Z-Wave Ethernet at IP 192.168.0.150, connected to interface ok.
Jan-20 12:19:17 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.150...
Jan-20 12:19:16 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
Jan-20 12:19:06 Z-Wave Error zBrockhill: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (zBrockhill).
Jan-20 12:18:06 Z-Wave Error zBrockhill: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (zBrockhill).
Jan-20 12:17:13 Z-Wave zBrockhill: Getting node information from controller...
Jan-20 12:17:12 Z-Wave zBrockhill: Z-Wave Ethernet at IP 192.168.0.150, connected to interface ok.
Jan-20 12:17:10 Informational Host B8-27-EB-D4-72-81 changed from 192.168.0.125 to 192.168.0.150
Jan-20 12:17:09 Z-Wave ************************************************************ *******************
Jan-20 12:17:09 Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
Jan-20 12:17:09 Z-Wave ************************************************************ *******************
Jan-20 12:17:07 Z-Wave Warning Trying to re-connect to Ethernet interface at IP 192.168.0.150...
Jan-20 12:17:06 Z-Wave Error zBrockhill: Error, the Z-Wave API Transmit Queue is not empty after waiting 20 seconds - the interface may be disconnected or not operational (zBrockhill).
Jan-20 12:17:06 Z-Wave Error zBrockhill: The zBrockhill interface did not respond to the request for the HomeID and Node - it may be disconnected or malfunctioning (2).
Jan-20 12:15:52 Startup Start up complete.
Jan-20 12:15:52 Startup HSSentry is disabled in Setup, sentry will not be started.
Jan-20 12:15:52 Startup (Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
Jan-20 12:15:52 Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
Jan-20 12:15:52 Startup Starting Event Scheduler...
Jan-20 12:15:52 Startup Running the startup script Startup.vb
Jan-20 12:15:52 Startup Starting Find service...
Jan-20 12:15:51 Startup Updater services starting...
Jan-20 12:15:51 Speech Listening for remote speaker connections on port 10401
Jan-20 12:15:51 Startup Initializing Speaker Client Interface
Jan-20 12:15:51 Startup Start automation engine...
Jan-20 12:15:51 email Initializing email, found 1481 messages
Jan-20 12:15:51 Z-Wave zBrockhill: Getting node information from controller...
Jan-20 12:15:51 Z-Wave zBrockhill: The Z-Wave API Execution Thread was Started or Restarted.
Jan-20 12:15:51 email Start checking server for email using POP
Jan-20 12:15:51 Startup Creating ASP.NET application host...
Jan-20 12:15:51 Startup Initializing email, will check server for new email
Jan-20 12:15:51 Web Server Web Server started on port 80
Jan-20 12:15:51 Web Server UPNP Discovery started
Jan-20 12:15:51 Web Server Local IP address is: 192.168.0.6
Jan-20 12:15:51 Z-Wave zBrockhill: Z-Wave Ethernet at IP 192.168.0.150, connected to interface ok.
Jan-20 12:15:51 Z-Wave Starting 'Z-Wave Health' Process Starter for (Brockhill)...
Jan-20 12:15:51 Z-Wave zBrockhill: The Z-Wave Command Execution Thread was Started or Restarted.
Jan-20 12:15:51 Z-Wave zBrockhill: ----------------------------------------------------------------------
Jan-20 12:15:51 Z-Wave Initializing Z-Wave interface zBrockhill (HomeSeer Z-NET Ethernet) at 192.168.0.150, port 2001
Jan-20 12:15:51 Z-Wave zBrockhill: ----------------------------------------------------------------------
Jan-20 12:15:51 Z-Wave zBrockhill: ============================================================ ==========
Jan-20 12:15:51 Startup HStouch server started, waiting for clients to connect.
Jan-20 12:15:51 HSTouch Server Server started on port 10200
Jan-20 12:15:51 Plug-In Finished initializing plug-in Z-Wave

====================================================
Cheers
Scott