Z-Net

[macromark]

Z-NET passed Z-Wave Plus certification today. Barring any unforeseen circumstances, the beta should be ready for sale next week.

[S-F]

Is transferring a network from a Z-Stick and Z-Troller working reliably?

[happnatious1]

I see a znet beta plugin in the updater and was wondering if the plan is to fork the zwave plugin or eventually keep all controllers under one.

[macromark]

Is transferring a network from a Z-Stick and Z-Troller working reliably?

Yes.

I see a znet beta plugin in the updater and was wondering if the plan is to fork the zwave plugin or eventually keep all controllers under one.

The Z-NET plug-in is already backwards compatible but we have not done extensive testing on it with older controllers yet. The plan is to release just one plug-in.

[NicolaiL]

Z-NET passed Z-Wave Plus certification today. Barring any unforeseen circumstances, the beta should be ready for sale next week.

Great news! Well done guys.

[jlrichar]

Looking forward to this! Just curious, if the pi part goes belly up sometime in the future is it possible to replace just that part? Or if some glutton for punishment wants a different pi version or some such could that be swapped in?

Awesome news. Though I am still curious about the possibility of replacing the pi part. Based on what you describe of the architecture this should be simple hardware swapping. Not sure what would be required for software.

I think the price you set is a fair price considering the work you guys did, the design of the device, and the expected capabilities.

[macromark]

Awesome news. Though I am still curious about the possibility of replacing the pi part. Based on what you describe of the architecture this should be simple hardware swapping. Not sure what would be required for software.

I think the price you set is a fair price considering the work you guys did, the design of the device, and the expected capabilities.

If the Pi board fails, you should be able to replace it with exactly the same model board. If you change to a different board, it's not likely to work.

[sooty]

A little off topic and there are also a couple of Bugzilla's on the subject but any chance of getting the Z-Wave plug-in to communicate with non-FTDI USB controllers?

Previous versions and the latest Z-Wave Beta .196 don't work with CDC-ACM based controllers like the .me UZB1.

The UZB1 works perfectly with Zensys-Tools and some other HA software that I've tested but not with Homeseer and also not with anything based on OpenZWave.

The issue appears to be related to the serial comms with the controller and locks the controller up on some transmissions.

Here is a chunk of debug log that may be of help.

06/02/2015_17:10:28 Exec with 1 CAPI Control objects for Z-Wave interface UZB 500 (1)
06/02/2015_17:10:28 Handling COMMAND=Command, sub-type=EXEC_DEVICE Node=0 Wait=False
06/02/2015_17:10:28 Device=Node 6 Z-Wave Switch Binary, Ref=6, CC=COMMAND_CLASS_SWITCH_BINARY, Node=6, EndPoint=-1, CAPI=Button
06/02/2015_17:10:28 [[[ In ExecNow PROCESSING 1 commands, NoQueue=True ]]]
06/02/2015_17:10:28 [[[ In ExecNow handling 1 NOW commands and 0 WAKE-UP commands using command class COMMAND_CLASS_SWITCH_BINARY, NoQueue=True ]]]
06/02/2015_17:10:28 Send_To_Collection (objCol)=1
06/02/2015_17:10:28 Send_To_Collection (NodesSP)=0, Regular Nodes=1, = 06
06/02/2015_17:10:28 Sending SINGLECAST frame to node 06
06/02/2015_17:10:28 Sending frame to node 6, frame=25-01-FF
06/02/2015_17:10:28 UZB 500: Attempt 1 sending to node 6 (UnSecured)
06/02/2015_17:10:28 EE34567C-001: S > 01-0A-00-13-06-03-25-01-FF-25-21-3C
06/02/2015_17:10:28 EE34567C-001: S > 06 (ACK)
06/02/2015_17:10:28 UZB 500: FRAME BEING PLACED IN FramesQ!
06/02/2015_17:10:28 UZB 500: PROCESSING - RESPONSE - Frame
06/02/2015_17:10:28 EE34567C-001: S > 06 (ACK)
06/02/2015_17:10:28 Process response frame
06/02/2015_17:10:28 UZB 500: RESPONSE: ZW_SEND_DATA, Frame=04-01-13-01-E8
06/02/2015_17:10:28 EE34567C-001: RQ < 07-00-13-21-00-00-02-C8
06/02/2015_17:10:28 UZB 500: PROCESSING - REQUEST - Frame
06/02/2015_17:10:28 ProcessFrame_STATUS from interface 1 (UZB 500) Type: ZW_SEND_DATA, Length: 8, Frame=07-00-13-21-00-00-02-C8
06/02/2015_17:10:28 UZB 500: REQUEST: ZW_SEND_DATA, Frame=07-00-13-21-00-00-02-C8
06/02/2015_17:10:38 UZB 500 LEAVING WaitForFinish FALSE (MASTER_Send_Data_REAL) with ZW_SEND_DATA/21
06/02/2015_17:10:38 UZB 500 LEAVING WaitForFinish FALSE (ZW_SEND_DATA/33 of ZWaveAPIThreadProc) with ZW_SEND_DATA/21
06/02/2015_17:10:38 UZB 500: MSDR Return: Node=6, Meta=False, FAIL: Not Complete
06/02/2015_17:10:38 SEND_DATA Timeout (Not Complete, SEND ABORT)=ZW_SEND_DATA-21

Paul.

[macromark]

Z-NET beta available for Pre-sale now!

http://board.homeseer.com/showthread.php?p=1162090

[macromark]

The UZB1 works perfectly with Zensys-Tools and some other HA software that I've tested but not with Homeseer and also not with anything based on OpenZWave.
Paul.

Rich tested this today and put a fix in for the next beta of the Z-Wave plug-in.

[sooty]

Rich tested this today and put a fix in for the next beta of the Z-Wave plug-in.

And I can confirm that plug-in .200 works fine with the .me UZB1.

Thank you


Paul..

[sooty]

Not sure if it's supposed to work with other controllers but FYI:
I tried the backup and restore feature documented in the Z-Net instructions from an older .me USB_C to the new UZB1.

I followed the instructions to the letter, backing up the old controller, disabling it, deleting it then physically removing it. I added the new controller then selected restore which all seemed to go OK

Feb-16 22:18:36 Z-Wave UZB1: Sigma Designs UZB reset, waiting for reset to complete.
Feb-16 22:18:36 Z-Wave UZB1: Exiting COM Device Thread
Feb-16 22:18:36 Z-Wave Warning A Z-Wave interface on the system is being restarted - some Z-Wave signals could be missed.
Feb-16 22:18:36 Z-Wave UZB1: Node information has been successfully loaded - restarting the controller...
Feb-16 22:18:32 Z-Wave UZB1: Restoring node information for node 19...
Feb-16 22:18:32 Z-Wave UZB1: Restoring node information for node 18...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 17...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 16...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 15...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 14...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 13...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 12...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 11...
Feb-16 22:18:31 Z-Wave UZB1: Restoring node information for node 10...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 8...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 7...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 6...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 5...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 4...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 3...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 2...
Feb-16 22:18:30 Z-Wave UZB1: Restoring node information for node 1...
Feb-16 22:18:22 Z-Wave UZB1: Erase complete - sending the network ID to the interface.
Feb-16 22:18:22 Z-Wave UZB1: Controller firmware version: 5.1
Feb-16 22:18:22 Z-Wave UZB1: Controller Manufacturer: PowerLynx, ID=0x1, Type=0x4
Feb-16 22:18:19 Z-Wave Z-Wave Interface UZB1 (1) has been reset to its defaults.
Feb-16 22:18:19 Z-Wave Warning UZB1: Erasing the interface...
Feb-16 22:18:19 Z-Wave UZB1: Restoring node information from the file C:\Program Files\Homeseer HS3\Data\Z-Wave\ZNet_Network FABFE13A_FABFE13A_2015-02-16_22.13.33.ZWave. Please wait...

The network ID and node numbers in the log correspond to the test network I backed up.

When the controller restarted it didn't take on the network ID of the previous network but created a new network with node numbers 1, 105, 106, 107 etc. The number of nodes was correct but they were in the wrong network and consequently couldn't communicate with the new controller.

Paul..

[macromark]

Not sure if it's supposed to work with other controllers but FYI:
I tried the backup and restore feature documented in the Z-Net instructions from an older .me USB_C to the new UZB1.

I followed the instructions to the letter, backing up the old controller, disabling it, deleting it then physically removing it. I added the new controller then selected restore which all seemed to go OK



The network ID and node numbers in the log correspond to the test network I backed up.

When the controller restarted it didn't take on the network ID of the previous network but created a new network with node numbers 1, 105, 106, 107 etc. The number of nodes was correct but they were in the wrong network and consequently couldn't communicate with the new controller.

Paul..

The new Z-Wave plug-in should be able to backup just about any controller but restore only works for Z-NET and for the discontinued Z-Troller.

[sooty]

The new Z-Wave plug-in should be able to backup just about any controller but restore only works for Z-NET and for the discontinued Z-Troller.

To avoid confusion, perhaps then it would be a good idea to remove the restore option from the drop down if its not supported for a particular controller.

Paul..

[macromark]

To avoid confusion, perhaps then it would be a good idea to remove the restore option from the drop down if its not supported for a particular controller.

Paul..

agreed. Rich is looking into this.