Errors in zipgateway.log


#1

Hello!

In my zipgateway.log contains lots of repeated errors related with SerialAPI and I would like to know what’s happening.

Below is a part of /tmp/zipgateway.log file.

18259065 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18259065 create failed, will retry
18259065 queue_send_done to node 4 queue 1
18259065 DTLS for Classic node
18260066 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18260066 create failed, will retry
18261066 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18261066 create failed, will retry
18262066 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18262066 create failed, will retry
18262346 DHCP Timeout
18262346 Sending DISCOVER
18262346 DHCP pass completed
18262346 update flag 1 135
18263066 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18263066 create failed, will retry
18264068 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18264068 create failed, will retry
18265068 Creating virtual node
 SerialAPI: Command: 0xa4 is not supported by this SerialAPI
 SerialAPI: Assertion failed at /var/lib/jenkins/jobs/Full_S2_Gateway_release/workspace/src/serialapi/Serialapi.c:600
 SerialAPI: SendFrameWithResponse() returning failure
18265068 create failed, will retry

#2

Hi Alexander,

Creating virtual nodes is one of the usual behaviours when Z/IP gateway starts and it’ll try to create repeatedly if creating also keeps failing since virtual node is necessary for gateway to operate normally.

You might want to check the version of z-wave bridge controller and gateway here. It seems, from the log, the command cannot be recognised by the SerialAPI.

Anta


#3

Anta thank you for your reply!

Worth to mention that despite this errors I can connect to the controller, list, add and remove nodes.

$ ./reference_client -p 123456789012345678901234567890aa -s fd00:aaaa::3
(ZIP) list
List of discovered Z/IP services:
---   zwC6A173A705.local: "Switch Binary [c6a173a70500]"
---   zwC6A173A701.local: "Static Controller [c6a173a70100]"

But when I try to switch my device on/off the command terminates with fail:

(ZIP) send "Switch Binary [c6a173a70500]" COMMAND_CLASS_SWITCH_BINARY SWITCH_BINARY_SET 00
(ZIP)
Transmit attempt timed out

And at the end nothing happens. I mean the device does not change its state. (When I communicate with this device through Z-Wave directly everything works fine.)

I also noticed that the above mentioned errors starts as soon as I send commands to the switch (see the attached gif - on the left side is the client console, on the right side is zipgateway.log).

Alternative source (gif): https://i.imgur.com/9lEhEIR.gifv

P.s. I’m using the latest versions of the firmware and Z/IP Gateway.


#4

That’s exactly what should happen with 0 virtual nodes being created.

The virtual node is being used as interfaces communicating with Z-Wave nodes so even the client is able to connect to gateway, the command won’t arrive to Z-Wave side, and gateway fails to operate normally.

Now I would say the issue is most probably in your Bridge controller (Z-Wave chip) or could also be the interface like USB.

If the issue persists for you, you may also contact Z-Wave support (z-wavesupport@silabs.com) or post in Hardware category.

Anta


#5

@anta.huang Thank you. Yes, it’s probably hardware issue.