[mh] Need a working Z-Wave configuration

I'm hoping someone with a working Z-Wave configuration under MH will 
share their relevant configuration information with me, as I can't get 
mine to work.

Details:

I'm starting to dabble with Z-Wave under MH. I have an AEOTec Z-Stick 
(Gen5) plugged into my Raspberry Pi. I've tested the Z-stick using the 
Open Z-Wave control panel (ozwcp) installed and executed under the MH 
login. It can control my one Z-Wave light switch, so I know the Z-stick 
is good and the MH login has all the necessary permissions.

MH can't seem to connect to the Z-stick however. At start-up it attempts 
to send a reset to the Z-Stick, but fails.

I'm running the latest MH code pulled from the master branch (last 
update 10/29/2022).

In mh.private.ini I have:

    ZWave_RZC0P_serial_port=/dev/ttyACM0
    rzc0p_errata=4
    rzc0p_retry_limit=5
    rzc0p_update10=0
    rzc0p_update100=1
    rzc0p_update1000=1
    rzc0p_timeout=10                      # Tried this at 60, no difference.
    rzc0p_id=001

In items.mht I have:

    #Item Type              Zwave ID#       name groups         
    interface       polling_interval        2way(1 or 0)    resume_level
    (if dimmer)
    ZWAVE_APPLIANCE,        006,            office_fan, All_Lights,    
    ZWave_RZC0P,    7,                      0

Here's the log:

    12/10/22 09:15:52 AM ZWave_RZC0P Info: Specified retry_limit of 5
    12/10/22 09:15:52 AM ZWave_RZC0P Info: Specified timeout of 10 seconds
      to Zwave interfaceM ZWave_RZC0P Debug: Writing data >DE
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: ZWave interface
    timeout, cmd:>DE
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: data timeout
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: cmd timeout
    12/10/22 09:15:52 AM Oops1: Use of uninitialized value in hash
    element at /home/mh/mh/bin/../lib/ZWave_RZC0P.pm line 420.
    12/10/22 09:15:52 AM Oops1: Use of uninitialized value $upd_count in
    numeric gt (>) at /home/mh/mh/bin/../lib/ZWave_RZC0P.pm line 423.
    12/10/22 09:15:52 AM Oops1: Use of uninitialized value in hash
    element at /home/mh/mh/bin/../lib/ZWave_RZC0P.pm line 429.
    12/10/22 09:15:52 AM Oops1: Use of uninitialized value in numeric gt
    (>) at /home/mh/mh/bin/../lib/ZWave_RZC0P.pm line 429.
    12/10/22 09:15:52 AM ZWave_RZC0P Adding
    id:006,type:ZWAVE_APPLIANCE,inst:0 to node list
    12/10/22 09:15:52 AM ZWave_RZC0P Debug: Writing data >?N006 to Zwave
    interface
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: ZWave interface
    timeout, cmd:>?N006
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: data timeout
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: xmit timeout
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: cmd timeout
    12/10/22 09:15:52 AM ZWave_RZC0P Info: Retrying Command >?N006,
    Retry Number:1 time:1670692573.43541
    12/10/22 09:15:52 AM ZWave_RZC0P Debug: Writing data >?N006 to Zwave
    interface
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: ZWave interface
    timeout, cmd:>?N006
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: data timeout
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: xmit timeout
    12/10/22 09:15:52 AM ZWave_RZC0P ZWave_RZC0P error: cmd timeout
    12/10/22 09:15:52 AM ZWave_RZC0P Was in Zwave check_for_data sub for
    10.0004432201385 seconds

The Oops1 errors are in the timeout handler, so they probably wouldn't 
happen if the timeout didn't occur. The simple problem is that the 
initial send is timing out.

It's probably something simple, like needing to declare a baud rate 
(which baud and how) or something similar. Do I need to run setserial 
first? Can anyone put me on the right track?

                                            -Brian M

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users