How to use multiple Tinkerforge IO 16 bricklet

Add-ons Bindings
1

How has the configuration to be done in the tinkerforge.cfg to use multiple IO 16 bricklets? The binding documentation does not mention it. Using one or the other in the cfg works fine. Using both in the cfg results in one working IO 16 only, too. Firmware for both is 2.0.6. They are connected to different Masterbricks but on the same stack, so same IP.

io16.uid=wjW
io16.type=bricklet_io16
io16.debouncePeriod=100

io16ina0.uid=wjW
io16ina0.subid=ina0
io16ina0.type=iosensor
io16ina0.pullUpResistorEnabled=true

and

io16.uid=wj6
io16.type=bricklet_io16
io16.debouncePeriod=100

io16ina0.uid=wj6
io16ina0.subid=ina0
io16ina0.type=iosensor
io16ina0.pullUpResistorEnabled=true

The uid=wj6 is the one which always works when entered to the cfg. The wjW works only w/o wj6 in the cfg.
maybe @theo @sihui

The Ind. Dig. In and Outs which don’t need config in the tinkerforge.cfg work fine in multiple use.
Using OH 2.2 Snapshot with tinkerforge1 binding.

2

Did you try a different prefix?

For example:

Aio16ina0.uid=wjW

Bio16ina0.uid=wj6

1 Like
3

Tried it, but ran into a non removable error:

CONFIG: duplicate device config for uid "wj6" and subId "ina2": fix openhab.cfg

Did cache and tmp deletion, tinkerforge.cfg correction… but error seems to be cached somewhere else.
Any idea how to avoid a full new SD card installation?

4

Delete /userdata/config/org/openhab/tinkerforge.config and restart openHAB.

1 Like
5

thanks
deleted
/var/lib/openhab2/config/org/openhab/tinkerforge.config
and tf binding is running again. Will try again for prefix changes tomorrow.

6

Working! Thank you @sihui

io16_2_.uid=wjW
io16_2_.type=bricklet_io16
io16_2_.debouncePeriod=100

io16_2_ina0.uid=wjW
io16_2_ina0.subid=ina0
io16_2_ina0.type=iosensor
io16_2_ina0.pullUpResistorEnabled=true

and

io16.uid=wj6
io16.type=bricklet_io16
io16.debouncePeriod=100

io16ina0.uid=wj6
io16ina0.subid=ina0
io16ina0.type=iosensor
io16ina0.pullUpResistorEnabled=true
1 Like
7

I have submitted a change to the docs to reflect this issue.

1 Like