433 Mhz Transmitter / rcswitch-pi

[mucpi (MucBot)]

Hey Klumpstein,

I am no expert but as I gathered some information about the 433 Mhz exec binding I found something.
The tutorial shows the solution with exec 1.8 or 1.9 under openhab (the old one). The new openhab works with exec binding version 2.0 and the solution from the tutorial doesnt work anymore. Here are some links about workarounds but I couldn’t make mine work.

http://openhabforum.de/viewtopic.php?t=221

Openhab 2 exec binding 2.0 configuration

Honestly, no idea. I found my working configuration by searching the forums. I do not really understand the OH2 configuration concepts yet. Here is an intermediate version which actually worked at the time of writing but had some limitations: Trigger Exec Binding switch with HUE Emulation [SOLVED] My current configuration is much more complex but I can post it if you need it.

Trigger Exec Binding switch with HUE Emulation [SOLVED]

I have the following exec binding which works quite well to switch on/off my NAS via the BasicUI: Thing: Thing exec:command:device-nas-control [ command="/home/openhab/bin/device-nas %2$s", interval=0, autorun=true ] Thing exec:command:device-nas-status [ command="/home/openhab/bin/device-nas status", interval=60, timeout=5 ] Item: String network_device_nas_switch "NAS" <network> (group_location_livingroom) [ "Switchable" ] { channel="exec:command:device-nas-control:input", channel="exec:co…

As far as I know there is no simple solutioon/tutorial yet.

Best,

mucBOT