Can not configure HEAT-IT Z-TRM3 Z-wave thermostat

Hi!

I think Im missing smth really basic, but I not able to connect HEAT-IT Z-TRM3 Thermostat(this is the only zwave device is have, the rest is zigbee) to my HomeAssistant setup(on raspberry pi 4), although I see many people are using it without many problems.

So, here is what I tried so far with the zwave usb recommended by the HomeAssistant community:

  1. First try with Aeotec Z-stick Gen5 starting z-wave inclusion process in HomeAssistant, the result: no matter which mode is it (S2, S0 or no encyption), the Heatit device is not detected, nothing in the logs as far as I can see.

Probably important to note 2 points:
1.1 the thermostat was detected once in the No encryption inclusion mode, but it was reported as dead, like in this thread. It was not possible to do anything with it. And it was never detected again afterwards(i did reset all the devices before running inclusion again)

1.2 looks like it was possible to include the thermostat by de-attaching the Zwave USB stick from the Pi4 and initiating inclusion mode by a button on the usb stick(there is such possibility in this Aeotec Z-stick Gen5). At least the Heatit thermostat gave me “Inc” message, not Error. But again once the usb stick was attached back to PI4 it did not worked just like in 1.1 above.

1.3 tried with SmartStart way of inclusion, did not worked either.

  1. second try with this device, it is again among recommended devices, detected fine by the HomeAssistant, but it does not see HeatIT thermostat in any inclusion mode, Im attaching logs here below.

Also it lets me add it by SmartStart, smth is listed in the provisioned devices, but thats it:

.

Logs are below:

Inclusion Logs

2022-10-10T18:47:35.549Z CNTRLR [Node 001] The node is alive.
2022-10-10T18:47:35.550Z CNTRLR [Node 001] The node is ready to be used
2022-10-10T18:47:35.551Z CNTRLR All nodes are ready to be used
ZwaveJS server listening on 0.0.0.0:3000
New client
2022-10-10T18:47:36.546Z DRIVER Usage statistics sent - next transmission scheduled in 23 hours.
2022-10-10T18:48:01.588Z CNTRLR Starting inclusion process with strategy Default…
2022-10-10T18:48:01.620Z SERIAL » 0x0105004ac10170 (7 bytes)
2022-10-10T18:48:01.623Z DRIVER » [REQ] [AddNodeToNetwork]
node type: Any
high power: true
network wide: true
callback id: 1
2022-10-10T18:48:01.627Z SERIAL « [ACK] (0x06)
2022-10-10T18:48:01.631Z SERIAL « 0x0107004a01010000b2 (9 bytes)
2022-10-10T18:48:01.634Z SERIAL » [ACK] (0x06)
2022-10-10T18:48:01.637Z DRIVER « [REQ] [AddNodeToNetwork]
status: Ready
callback id: 1
2022-10-10T18:48:01.648Z CNTRLR The controller is now ready to add nodes
2022-10-10T18:48:48.896Z CNTRLR stopping inclusion process…
2022-10-10T18:48:48.921Z SERIAL » 0x0105004ac50277 (7 bytes)
2022-10-10T18:48:48.923Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 2
2022-10-10T18:48:48.926Z SERIAL « [ACK] (0x06)
2022-10-10T18:48:48.977Z SERIAL « 0x0107004a02060000b6 (9 bytes)
2022-10-10T18:48:48.982Z SERIAL » [ACK] (0x06)
2022-10-10T18:48:48.985Z DRIVER « [REQ] [AddNodeToNetwork]
status: Done
callback id: 2
2022-10-10T18:48:48.999Z CNTRLR The inclusion process was stopped
2022-10-10T18:48:51.008Z CNTRLR Starting inclusion process with strategy Security_S0…
2022-10-10T18:48:51.028Z SERIAL » 0x0105004ac10372 (7 bytes)
2022-10-10T18:48:51.029Z DRIVER » [REQ] [AddNodeToNetwork]
node type: Any
high power: true
network wide: true
callback id: 3
2022-10-10T18:48:51.032Z SERIAL « [ACK] (0x06)
2022-10-10T18:48:51.036Z SERIAL « 0x0107004a03010000b0 (9 bytes)
2022-10-10T18:48:51.038Z SERIAL » [ACK] (0x06)
2022-10-10T18:48:51.040Z DRIVER « [REQ] [AddNodeToNetwork]
status: Ready
callback id: 3
2022-10-10T18:48:51.047Z CNTRLR The controller is now ready to add nodes
2022-10-10T18:49:28.443Z CNTRLR stopping inclusion process…
2022-10-10T18:49:28.461Z SERIAL » 0x0105004ac50471 (7 bytes)
2022-10-10T18:49:28.462Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 4
2022-10-10T18:49:28.465Z SERIAL « [ACK] (0x06)
2022-10-10T18:49:28.517Z SERIAL « 0x0107004a04060000b0 (9 bytes)
2022-10-10T18:49:28.520Z SERIAL » [ACK] (0x06)
2022-10-10T18:49:28.522Z DRIVER « [REQ] [AddNodeToNetwork]
status: Done
callback id: 4
2022-10-10T18:49:28.559Z CNTRLR The inclusion process was stopped
2022-10-10T18:49:33.791Z CNTRLR Starting inclusion process with strategy Insecure…
2022-10-10T18:49:33.811Z SERIAL » 0x0105004ac10574 (7 bytes)
2022-10-10T18:49:33.812Z DRIVER » [REQ] [AddNodeToNetwork]
node type: Any
high power: true
network wide: true
callback id: 5
2022-10-10T18:49:33.815Z SERIAL « [ACK] (0x06)
2022-10-10T18:49:33.821Z SERIAL « 0x0107004a05010000b6 (9 bytes)
2022-10-10T18:49:33.823Z SERIAL » [ACK] (0x06)
2022-10-10T18:49:33.825Z DRIVER « [REQ] [AddNodeToNetwork]
status: Ready
callback id: 5
2022-10-10T18:49:33.833Z CNTRLR The controller is now ready to add nodes
2022-10-10T18:50:20.392Z CNTRLR stopping inclusion process…
2022-10-10T18:50:20.409Z SERIAL » 0x0105004ac50673 (7 bytes)
2022-10-10T18:50:20.411Z DRIVER » [REQ] [AddNodeToNetwork]
action: Stop
high power: true
network wide: true
callback id: 6
2022-10-10T18:50:20.414Z SERIAL « [ACK] (0x06)
2022-10-10T18:50:20.466Z SERIAL « 0x0107004a06060000b2 (9 bytes)
2022-10-10T18:50:20.469Z SERIAL » [ACK] (0x06)
2022-10-10T18:50:20.472Z DRIVER « [REQ] [AddNodeToNetwork]
status: Done
callback id: 6
2022-10-10T18:50:20.492Z CNTRLR The inclusion process was stopped
2022-10-10T18:51:18.519Z CNTRLR Enabling Smart Start listening mode…
2022-10-10T18:51:18.535Z SERIAL » 0x0105004a4900f9 (7 bytes)
2022-10-10T18:51:18.537Z DRIVER » [REQ] [AddNodeToNetwork]
action: Enable Smart Start listening mode
2022-10-10T18:51:18.541Z SERIAL « [ACK] (0x06)
2022-10-10T18:51:18.549Z CNTRLR Smart Start listening mode enabled
Starting logging event forwarder at debug level
Stopping logging event forwarder
Starting logging event forwarder at debug level
Stopping logging event forwarder

and Im attaching Diagnostics information.

Diagnostics
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.10.2",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.5",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Amsterdam",
    "os_name": "Linux",
    "os_version": "5.15.61-v8",
    "supervisor": "2022.10.0",
    "host_os": "Home Assistant OS 9.0",
    "docker_version": "20.10.17",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.28.0",
      "requirements": [
        "aiogithubapi>=22.2.4"
      ]
    },
    "yandex_station": {
      "version": "3.11.0",
      "requirements": []
    },
    "xiaomi_gateway3": {
      "version": "2.1.1",
      "requirements": [
        "zigpy>=0.33.0"
      ]
    },
    "ble_monitor": {
      "version": "10.5.1",
      "requirements": [
        "pycryptodomex>=3.14.1",
        "janus>=1.0.0",
        "aioblescan>=0.2.13",
        "btsocket>=0.2.0",
        "pyric>=0.1.6.3"
      ]
    },
    "samsungtv_smart": {
      "version": "0.7.8",
      "requirements": [
        "websocket-client!=1.4.0,>=0.58.0",
        "wakeonlan>=2.0.0",
        "aiofiles>=0.8.0"
      ]
    },
    "xiaomi_miot": {
      "version": "0.6.13",
      "requirements": [
        "construct==2.10.56",
        "python-miio>=0.5.6",
        "micloud>=0.3"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zwave_js",
    "name": "Z-Wave",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zwave_js",
    "requirements": [
      "pyserial==3.5",
      "zwave-js-server-python==0.43.0"
    ],
    "codeowners": [
      "@home-assistant/z-wave"
    ],
    "dependencies": [
      "usb",
      "http",
      "websocket_api"
    ],
    "iot_class": "local_push",
    "usb": [
      {
        "vid": "0658",
        "pid": "0200",
        "known_devices": [
          "Aeotec Z-Stick Gen5+",
          "Z-WaveMe UZB"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*z-wave*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      }
    ],
    "zeroconf": [
      "_zwave-js-server._tcp.local."
    ],
    "loggers": [
      "zwave_js_server"
    ],
    "is_built_in": true
  },
  "data": {
    "versionInfo": {
      "driverVersion": "10.3.0",
      "serverVersion": "1.24.0",
      "minSchemaVersion": 0,
      "maxSchemaVersion": 24
    },
    "entities": [],
    "state": {
      "nodeId": 1,
      "index": 0,
      "status": 4,
      "ready": true,
      "isListening": true,
      "isRouting": true,
      "isSecure": "unknown",
      "manufacturerId": 277,
      "productId": 1,
      "productType": 1024,
      "firmwareVersion": "5.39",
      "deviceConfig": {
        "filename": "/data/db/devices/0x0115/zme_uzb.json",
        "isEmbedded": true,
        "manufacturer": "Z-Wave.Me",
        "manufacturerId": 277,
        "label": "UZB",
        "description": "Z-Wave USB Stick",
        "devices": [
          {
            "productType": 1024,
            "productId": 1
          }
        ],
        "firmwareVersion": {
          "min": "0.0",
          "max": "255.255"
        }
      },
      "label": "UZB",
      "interviewAttempts": 0,
      "endpoints": [
        {
          "nodeId": 1,
          "index": 0,
          "deviceClass": {
            "basic": {
              "key": 2,
              "label": "Static Controller"
            },
            "generic": {
              "key": 2,
              "label": "Static Controller"
            },
            "specific": {
              "key": 1,
              "label": "PC Controller"
            },
            "mandatorySupportedCCs": [],
            "mandatoryControlledCCs": [
              32
            ]
          },
          "commandClasses": []
        }
      ],
      "values": [],
      "isFrequentListening": false,
      "maxDataRate": 100000,
      "supportedDataRates": [
        40000,
        100000
      ],
      "protocolVersion": 3,
      "supportsBeaming": true,
      "supportsSecurity": false,
      "deviceClass": {
        "basic": {
          "key": 2,
          "label": "Static Controller"
        },
        "generic": {
          "key": 2,
          "label": "Static Controller"
        },
        "specific": {
          "key": 1,
          "label": "PC Controller"
        },
        "mandatorySupportedCCs": [],
        "mandatoryControlledCCs": [
          32
        ]
      },
      "interviewStage": "Complete",
      "deviceDatabaseUrl": "https://devices.zwave-js.io/?jumpTo=0x0115:0x0400:0x0001:5.39",
      "statistics": {
        "commandsTX": 0,
        "commandsRX": 0,
        "commandsDroppedRX": 0,
        "commandsDroppedTX": 0,
        "timeoutResponse": 0
      },
      "isControllerNode": true,
      "keepAwake": false
    }
  }
}

I tried reseting usb sticks, the thermostat, updating to the latest version of HA, bringing the PI4 closer to the thermostat(they are any way not that far), no luck. Also tried with Zwave JS UI addon.

So, not sure what to do next. Try another zwave USB stick? Get another Heatit thermostat(I need one more anyway) to try it out(return if it is no working)?

Any advice is highly appreciated…

Are you plugging the zwavel stick directly in the Pi?

Try an USB extension cable. There is a well known problem with zwave sticks plugged directly in the Pi having interference issues.

1 Like

I used the QR code. Firstly I scanned the code. Then I mounted the thermostat into the wall. When it got electricity HA displayed the thermostat correctly. (Using HA Blue with Aeotec Z-Stick 700)

1 Like

I would try a factory reset on the device. Have your stick plugged in on an extension cable and try again.

1 Like

When I read it for the first time, I though this is a brilliant suggestion, since it would explain all the strange behavior in 1, 1.1, 1.2 points above.

So, I got the usb extension(1m enough I guess?) and tried it with the usb stick from point 2 above, no luck so far with a quick try, but ill try devices reset, then if it does not work re-order the Aeotec stick once again and will try with it again attaching it to the cable. So, there is a hope =) Thank you folks!

Sometime you get a “used” device that was returned and already “paired” to avoid this I tend to due a factory reset on all new devices before attempting pairing.

2 Likes

@PeteRage @BebeMischa @Tomahawk Hi Folks, I have to admit the advises you provided are just brilliant! The trick was with actually adding a long(1-1,5m usb cable) which will move the z-wave usb stick away from the Raspberry PI and then it started working as a charm! You can’t image home much time I spent before with all the different setups and combinations, thank you very much!

1 Like