Could not resolve thingType - Fibaro Single Switch 2

Add-ons Bindings
,
1

Am seeing this issue when I’m adding a Fibaro Single Switch 2 via HABMin:

13:43:27.838 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 010F:0403:3000::3.2

However this device does exist in the database, it’s this.

It looks like the suffix is different? 1000 vs 3000? Potential firmware update or maybe it’s because it’s the AU/NZ version? Can I manually copy the 0403:1000 config to 0403:3000 to test my theory?

edit Assuming the database gets compiled into the jar? This looks like the line I need to adjust.

Versions:

bundle:list -s | grep openhab
166 | Active   |  90 | 2.0.0                 | openHAB Core                                           | org.openhab.core
167 | Active   |  80 | 2.0.0                 | openHAB Karaf Integration                              | org.openhab.core.karaf
169 | Resolved |  80 | 2.0.0                 | openHAB Sound Support, Hosts: 111                      | org.openhab.io.sound
170 | Active   |  80 | 2.0.0                 | openHAB Dashboard UI                                   | org.openhab.ui.dashboard
176 | Active   |  80 | 2.0.0                 | openHAB 1.x Compatibility Layer                        | org.openhab.core.compat1x
200 | Active   |  80 | 2.0.0                 | openHAB REST Documentation                             | org.openhab.io.rest.docs
201 | Resolved |  80 | 2.0.0                 | openHAB Basic UI Fragment, Hosts: 197                  | org.openhab.ui.basicui
202 | Active   |  80 | 2.0.0                 | openHAB Classic UI Fragment                            | org.openhab.ui.classicui
203 | Active   |  80 | 2.0.0                 | HABmin User Interface                                  | org.openhab.ui.habmin
204 | Active   |  80 | 2.0.0                 | HABPanel User Interface                                | org.openhab.ui.habpanel
205 | Resolved |  80 | 2.0.0                 | openHAB Paper UI Theme Fragment, Hosts: 199            | org.openhab.ui.paperui
209 | Active   |  80 | 1.9.0.201701200211    | openHAB Piface Binding                                 | org.openhab.binding.piface
210 | Active   |  80 | 1.9.0                 | openHAB Mail Action                                    | org.openhab.action.mail
211 | Active   |  80 | 1.9.0                 | openHAB Twitter Action                                 | org.openhab.action.twitter
213 | Active   |  80 | 2.0.0                 | ZWave Binding                                          | org.openhab.binding.zwave
214 | Active   |  80 | 1.9.0                 | openHAB Serial Binding                                 | org.openhab.binding.serial
215 | Active   |  80 | 1.9.0                 | openHAB MQTT Binding                                   | org.openhab.binding.mqtt
216 | Active   |  80 | 1.9.0                 | openHAB MQTT Transport Bundle                          | org.openhab.io.transport.mqtt
217 | Active   |  80 | 1.9.0                 | openHAB RRD4j Persistence Bundle                       | org.openhab.persistence.rrd4j
218 | Active   |  80 | 1.9.0                 | openHAB InfluxDB Persistence bundle                    | org.openhab.persistence.influxdb
219 | Active   |  80 | 2.0.0                 | Network Binding                                        | org.openhab.binding.network
2

@chris “Please note that you must contact the administrator to get edit rights to the database once you have registered.”

Happy to make the adjustments required on your Z-Wave database. Same username here as there.

3

Your access has been updated - any problems etc, just let me know…

Cheers
Chris

1 Like
4

Have requested a review. What’s the validation process? Can I replace the zwave binding jar with a snapshot one with the updated database to confirm it works or do I need to switch my whole install to snapshot?

5

Just closing this loop.

The April 15th Snapshot of the zwave binding (latest always here, info on that snapshot here.) contained the database updates. Installed and am now able to communicate with my device.

Thanks @chris.

1 Like