Aeotec Garage Controller not being properly detected after Firmware Update 1.14

Add-ons Bindings
1

I hope this is the right spot to post. I have just recently updated my firmware for an Aoetec Garage Cotroller V5. This is what I see after scanning for the Thing.

Aeotec Garage Controller
Aeotec Garage Controller726×1024 191 KB

When I look in frontail I get this message.
2021-07-18 13:59:27.218 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 38: Device discovery could not resolve to a thingType! 0086:0203:003E::1.14.
The unit was working this morning. The firmware reported that it had worked successfully. Any help would be much appreciated.

2

What version of openHAB? Did you try deleting (NOT exclude from the network) & re-adding the Thing to OH?

3

I am using Openhab 3.1. I have deleted from Openhab. I have also removed from my ZWave Stick (Aeotec Gen5). I factory reset my garage controller and re added. I live in Australia and the firmware update was successful. I am a little confused as I had disabled the opening and closing alarm. These are still disabled even after resetting. Does the database need updating as this firmware update was only released in Jan of this year.

4

The database entry allows for all versions but if the firmware added new features a new entry would need to be created by somebody in the community.

5

2021-07-19 18:33:51.761 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 15: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-07-19 18:33:51.805 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 21: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-07-19 18:33:51.835 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 24: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-07-19 18:33:51.900 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 34: Device discovery could not resolve to a thingType! Manufacturer data not known.

2021-07-19 18:33:51.920 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 40: Device discovery could not resolve to a thingType! 0086:0203:003E::1.14

2021-07-19 18:33:51.923 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:a7533472a4:node40’ to inbox.

==> /var/log/openhab/events.log <==

2021-07-19 18:33:51.924 [INFO ] [openhab.event.InboxAddedEvent ] - Discovery Result with UID ‘zwave:device:a7533472a4:node40’ has been added.

2021-07-19 18:33:55.047 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ZWaveSerialController_StartFrames’ changed from 11490 to 11491

2021-07-19 18:33:55.112 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘ZWaveSerialController_StartFrames’ changed from 11491 to 11492

2021-07-19 18:33:55.116 [INFO ] [openhab.event.InboxRemovedEvent ] - Discovery Result with UID ‘zwave:device:a7533472a4:node40’ has been removed.

2021-07-19 18:33:55.127 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:device:a7533472a4:node40’ changed from UNINITIALIZED to INITIALIZING

2021-07-19 18:33:55.142 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:device:a7533472a4:node40’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2021-07-19 18:33:55.149 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zwave:device:a7533472a4:node40’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2021-07-19 18:33:55.159 [INFO ] [openhab.event.ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]

The node number has changed from 39 to 40 as i have tried to add it properly after another firmware update of 1.14. The log file of my ZWave Stick seems to get no config status message. Is this right to assume.

6

I have just upgraded to OH3 from OH2 and this device is no longer recognised. I am running 1.12 of the firmware and having the same problem.

This is the information reported for the thing. I checked the database and the device is still there (https://opensmarthouse.org/zwavedatabase/256).

{
  "statusInfo": {
    "status": "ONLINE",
    "statusDetail": "NONE"
  },
  "editable": true,
  "label": "Z-Wave Node 082 (0086:0203:003E:1.12)",
  "bridgeUID": "zwave:serial_zstick:ef4ae6a4",
  "configuration": {
    "group_1": [],
    "node_id": 82,
    "group_2": []
  },
  "properties": {
    "zwave_class_basic": "BASIC_TYPE_ROUTING_SLAVE",
    "zwave_class_generic": "GENERIC_TYPE_ENTRY_CONTROL",
    "zwave_frequent": "false",
    "zwave_neighbours": "",
    "zwave_version": "1.12",
    "zwave_listening": "true",
    "zwave_plus_devicetype": "NODE_TYPE_ZWAVEPLUS_NODE",
    "zwave_deviceid": "62",
    "zwave_nodeid": "82",
    "zwave_routing": "true",
    "zwave_plus_roletype": "ROLE_TYPE_SLAVE_ALWAYS_ON",
    "zwave_beaming": "true",
    "zwave_secure": "false",
    "zwave_class_specific": "SPECIFIC_TYPE_SECURE_BARRIER_ADDON",
    "zwave_manufacturer": "134",
    "zwave_devicetype": "515"
  },
  "UID": "zwave:device:ef4ae6a4:node82",
  "thingTypeUID": "zwave:device",
  "channels": []
}

Any thoughts?

7

As you point out, the device is already in the database. I’m not sure what version of OH you’re running, but I would suggest that the first thing to do is to ensure you are using the latest binding - possibly using the snapshot would ensure this works.

8

Thanks Chris.

I am running 3.1.0. I will update tomorrow and see if it works.

9

I updated to 3.2.0.M3 and it finds the device.

Thanks @chris

1 Like