New user - can't get Aeotec z-stick gen5 operational on Windows 10

[dave@jadco.com]

Successfully installed FHEM on an up-to-date Windows 10, and played with the tutorial (created switches and lights) - everything works.  Plugged in Aeotec z-stick gen5, and defined a dongle with:

define ZWDongle_1 ZWDongle COM3@9600

ZWDongle_1 shows up with a STATE of Initialized.

When I perform: get ZWDongle_1 homeId, I get a response of: "homeId is unsupported by this controller."

I do not know how to proceed - any recommendations?  The log contains this:

2020.05.31 08:24:20 1: starting in console mode
2020.05.31 08:24:20 1: Including fhem.cfg
2020.05.31 08:24:20 3: WEB: port 8083 opened
2020.05.31 08:24:20 2: eventTypes: loaded 4 events from ./log/eventTypes.txt
2020.05.31 08:24:20 3: Opening ZWDongle_1 device COM3
2020.05.31 08:24:20 3: Setting ZWDongle_1 serial parameters to 9600,8,N,1
2020.05.31 08:24:20 1: PERL WARNING: Second Read attempted before First is done at ./FHEM/00_ZWDongle.pm line 907.
2020.05.31 08:24:20 1: PERL WARNING: Use of uninitialized value $got in numeric ne (!=) at C:/fhem/perl/vendor/lib/Win32/SerialPort.pm line 1216.
2020.05.31 08:24:20 3: ZWDongle_1 device opened
2020.05.31 08:24:20 1: Including ./log/fhem.save
2020.05.31 08:24:20 1: Messages collected while initializing FHEM:SecurityCheck:
  WEB is not password protected

Protect this FHEM installation by defining an allowed device with define allowed allowed
You can disable this message with attr global motd none

2020.05.31 08:24:20 3: initialUsbCheck return value: This command is not yet supported on windows
2020.05.31 08:24:20 0: Featurelevel: 6
2020.05.31 08:24:20 0: Server started with 7 defined entities (fhem.pl:22041/2020-05-27 perl:5.030002 os:MSWin32 user:Dave pid:14628)
2020.05.31 08:24:21 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 08:24:21 5: SW: 01030007fb
2020.05.31 08:24:21 1: PERL WARNING: Second Write attempted before First is done at FHEM/DevIo.pm line 197.
2020.05.31 08:24:21 1: PERL WARNING: Use of uninitialized value $written in numeric ne (!=) at C:/fhem/perl/vendor/lib/Win32/SerialPort.pm line 1580.
2020.05.31 08:24:22 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 08:24:22 5: SW: 01030007fb
2020.05.31 08:24:23 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 08:24:23 5: SW: 01030007fb
2020.05.31 08:24:24 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 08:24:24 1: ERROR: max send retries reached, removing 01030007fb from dongle sendstack

[krikan]

Please try:

Code Auswählen Erweitern

define ZWDongle_1 ZWDongle COM3@115200

[dave@jadco.com]

I deleted the ZWDongle_1, and redefined it as suggested.  I restarted fhem, and still have the same problem:
"homeId is unsupported by this controller."

I've spent many hours on the forum, trying to understand how to proceed, but can't find any leads.  Any help is appreciated.


Log:

2020.05.31 09:42:22 3: Setting ZWDongle_1 serial parameters to 115200,8,N,1
2020.05.31 09:42:22 1: PERL WARNING: Second Read attempted before First is done at ./FHEM/00_ZWDongle.pm line 907.
2020.05.31 09:42:22 1: PERL WARNING: Use of uninitialized value $got in numeric ne (!=) at C:/fhem/perl/vendor/lib/Win32/SerialPort.pm line 1216.
2020.05.31 09:42:22 1: COM3 reappeared (ZWDongle_1)
2020.05.31 09:42:23 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 09:42:23 1: PERL WARNING: Second Write attempted before First is done at FHEM/DevIo.pm line 197.
2020.05.31 09:42:23 1: PERL WARNING: Use of uninitialized value $written in numeric ne (!=) at C:/fhem/perl/vendor/lib/Win32/SerialPort.pm line 1580.
2020.05.31 09:42:24 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 09:42:25 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 09:42:26 2: ZWDongle_ProcessSendStack: no ACK, resending message 01030007fb
2020.05.31 09:42:26 1: ERROR: max send retries reached, removing 01030007fb from dongle sendstack

[rudolfkoenig]

2020.05.31 09:42:22 1: PERL WARNING: Second Read attempted before First is done at ./FHEM/00_ZWDongle.pm line 907.

This is definitely wrong, and I have no idea how to fix it, as I do not have a Windows 10 installation to do a step-by-step debugging.
Are you sure that COM3 is the ZWave Dongle and the right driver is installed? The Baud rate should be irrelevant, as it is not a real serial device.

@krikan: Did you ever tested FHEM on Windows with a ZWave-Dongle? If yes: what type of windows was it?

@dave: Less then 1% of the FHEM user are using it on Windows, so experience with some setups is scarce. I advise using FHEM on Linux, it might be sufficient to start it in a docker container.

[krikan]

@krikan: Did you ever tested FHEM on Windows with a ZWave-Dongle? If yes: what type of windows was it?

FHEM runs here permanently on windows 10 and windows 2012 backup server without problems (strawberry perl). However, both systems are not up to date. I will test with updated FHEM. So far I have not encountered the WARNING mentioned here.

[krikan]

Windows 10 Pro (May 2020 update)
strawberry perl 5.30.2.1 32bit portable
fhem.pl:22074/2020-05-30
Vision Controller
=> no problems

The Baud rate should be irrelevant, as it is not a real serial device.

Tested -> That's right.

Is it possible that Win32::SerialPort was not installed properly or in an old version? I often had trouble with this when installing Win32::SerialPort.

[krikan]

@dave: Did you solve the problem?

[dave@jadco.com]

No.  Since less than 1% of users are on Windows, I will stop trying to get this to work.  How do I "close" this post?  -Dave

[krikan]

How do I "close" this post?  -Dave

That's not necessary.

To test Windows with FHEM and ZWave, this way works for me: https://wiki.fhem.de/wiki/FHEM_Installation_Windows/en
If you can choose, then take Linux.