GPIO Initial state

[kevin]

I can’t speak for the original poster, but I found the command line to be the only way to get GPIO to work in OH V2.0, I can’t speak for V2.1 as I have enough work trying to get my RFXCOM device to come up in a predictable fashion.
After the unreliability of GPIO for inputs in OH V1.9 I’ve transitioned all inputs and most outputs via MQTT to ESP8266 Devices (Adafruit Huzzah) running ESPEasy. At around $10 USD a pop it is much better use of my time than continually battling GPIO problems. The ESP’s have been very reliable as long as I reboot them once a month which I do with a script that looks at their uptime

OH2 GPIO Binding broken and a possible workaround

I’m migrating to OpenHAB2, and I’d like to congratulate everyone who’s worked on it, its a great step up, especially with OpenHAB 2 bindings. Unfortunately on my system at least the included V1.9 GPIO Binding doesn’t work reliably. After working initially, it went on to spit out an obscure error on booting about not being able to get a lock, so after wasting a few hours on it I’ve thrown it away and created a workaround. I only use GPIO for outgoing items so my needs are simple. I’ve installed …

details my journey

I set the initial state of GPIO Pins via a Linux Script ran from Crontab which gets around the original problem of all inputs turning on when OH starts

[Apfelkuacha (LuKe)]

As mentioned already, when the system starts the output pin should be set to HIGH (5 Volts) and this isn’t possible with GPIO binding…

Edit: now it is possible with GPIO binding by setting following: initialValue:high