Tinkerforge Binding: "IO 16 Bricklet" -> OpenHAB suddenly detects inversion of all inputs

,
1

Hi,

I am using the Tinkerforge Binding (1.9) to connect to different Tinkerforge Bricklets and I have a problem with the IO 16 Bricklet. Although there is no change of state on all inputs (Brickviewer shows still same states), OpenHab2 (e.g. Habpanel) suddenly shows an inversion of all inputs. I am using this inputs to detect the open/close state of all doors and windows in our house. This happens from time to time and I have to restart the RPi to get the right status back. A simple restart of the OpenHab2 service does not help.

Here is what I see the in the event log.

2017-04-04 19:51:13.789 [ItemStateChangedEvent ] - ina3 changed from OPEN to CLOSED
2017-04-04 19:51:51.096 [ItemStateChangedEvent ] - ina1 changed from CLOSED to OPEN
2017-04-04 19:51:51.119 [ItemStateChangedEvent ] - ina0 changed from CLOSED to OPEN
2017-04-04 19:51:51.153 [ItemStateChangedEvent ] - ina2 changed from CLOSED to OPEN
2017-04-04 19:51:51.162 [ItemStateChangedEvent ] - ina5 changed from CLOSED to OPEN
2017-04-04 19:51:51.170 [ItemStateChangedEvent ] - ina4 changed from CLOSED to OPEN
2017-04-04 19:51:51.177 [ItemStateChangedEvent ] - ina7 changed from CLOSED to OPEN
2017-04-04 19:51:51.182 [ItemStateChangedEvent ] - ina6 changed from CLOSED to OPEN

Is this a bug in the Binding?

Thanks for your help!

2

When I remember correctly there was a problem in the firmware, so make sure you have the latest:

http://download.tinkerforge.com/firmwares/bricklets/io16/bricklet_io16_firmware_latest.bin

1 Like
3

I updated the Master Brick and the Bricklet. Hopefully this will help. Thanks for the hint!

4

Did it?

5

Yes and no…
After the update of the Bricklet I don’t see this nasty input inversions anymore, but …
I also updated the Master Brick and now the brick deamon seems to loose the connection to the brick every few hours so that I have to reset the brick.
I have to find out what’s going on there (USB connection, brick deamon …).

6

According to the Tinkerforge forum this is mostly caused by a weak power supply or bad usb cable (shielding) … good luck.

7

I now changed the cable, the power supply and the Master Brick to a 2.1. hardware version.
… stable since 24h :+1:

1 Like