GPIO binding reset all outputs

[sherif (Marcin)]

Hi !

I have a problem with devices connected to GPIO and controlled by OH 1.8. After each restart of OH (service openhab restart) all PINs are on for the moment, when persistence recover assign items.

When I stop OH service all GPIO pins going from out mode to in and also all of them are “1” = on.

 |  17 |   0 | GPIO. 0 |   IN | 1 | 11 || 12 | 1 | IN   | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |   IN | 1 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |   IN | 1 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |

When I start openhab service again pins are going to out mode. Then they are set according last stage (persistence):

 |  17 |   0 | GPIO. 0 |  OUT | 0 | 11 || 12 | 0 | OUT  | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |  OUT | 0 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |  OUT | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |

Is it and fix for it or work around ?

[rossko57]

I think this is an old story with no satisfactory solution yet?

GPIO Initial state

As far as I remember, it doesn’t work properly. I had relays on GPIO, and I wanted always have HIGH state on startup. I’ve tried System started trigger and it worked in this way: on RPi reboot all GPIO was undefined, but when OH wast started, all used GPIO switched into HIGH states (depending on System started trigger), but after 1-5 (randomly) sec all used GPIO’s switched into LOW state. RestoreOnStartup strategy also doesn’t works properly with GPIO - booth for including and excluding it…

[zertaul (Andrzej)]

I didn't found solution, so finally I decidet to move on Z-Wave hardware. – kind regards Andrzej