If (light is off) and (Aq of the lighting block changes from 0 to 1) then trigger (the light if off and should be switched on) If (light is on) and (Aq of the lighting block changes from 1 to 0) then trigger (the light is on and should be switched off) If (light is on) and (Aq of the lighting block changes from 0 to 1) then do not trigger (the light is already on) Just of the top of my head, I imagine something like: I suspect that it should be possible to create some logic that can trigger the TR input of my eib pushswitch block. At the moment, I store the states of a light in a memory flag (one for every light), which is then used as input to the S of a eib pushbutton (to show the correct status of the button in the loxone app). 1/1/1 switches a light whereas 1/2/1 gives me the status of the light), the leds on the switches are connected to sync with that. My installer configured all knx lights with an address from which I can get the status (e.g. As I do not know KNX (nor have the license), I will either have to contact my installer or try something in Loxone. So either in ETS it is necessary to change things, similar to how Loxone shows it on their website for an extended knx sensor, or I have to come up with something else. STREAM* pTcpStream = stream_create("/dev/tcp//80/api//groups/1",0,0) // create tcp streamĬhar* pTcpCmd = "GET /api//groups/1 HTTP/1.I get it. This way, these things are always (or after 60 seconds) in sync even if you use the hue app or any hue hardware device such as the dimmer. It will set the status of both the virtual input and virtual output according to what it gets from the api This pico program will call the hue bridge api every 6 seconds to get the status of the hue thing you want to control.
#Loxone eib dimmer code
#Loxone eib dimmer full
Think of ct / bri / rgb readings for a full blown RGB(W) bulb. A different challenge is to sync back more than just a state (on or off).If you had more than one bulbs/lights used on that Lighting Controller, that's another challenge, but I suppose it is out of the scope of this topic.Then you might use Edge detection block out of its input and connect it to O and R inputs of Lighting Controller block.
![loxone eib dimmer loxone eib dimmer](https://deinempassen-wahr.com/vwo/zzEmZjFu2x7eFA04LAXkdQHaCk.jpg)
Finally, I would create Virtual Input with Philips Bulb 1 state in Loxone Config.Then I would subscribe to that topic in MQTT Gateway plugin and push it to Loxone.Since I push all readings to MQTT, I would have that bulb state under something like fhem/Philips_Bulb_1/state.See Attachment 8 for readings of one of my Philips bulbs. After you sync lights from HUE Bridge to FHEM, you will be getting all reading for every Light.
#Loxone eib dimmer how to
Read FHEM HUE-module docs for details how to connect it. Command set starts with something like define MyBridge HUEBridge HUEbrideIP:HuePort. Connect FHEM to HUEBridge with included Hue module.So you may do exactly the same with Hue Lights. Since new Loxone Config version >10.3 you've better use new "Edge detection" block instead. Please note: Push switch block is used here solely to detect edge (it's not used in Visualization!). The point is, it also has external input control. I've used a simple Switch block in Loxone Config that has a Virtual Output connected to control the wall plug (http call to FHEM "/fhem?cmd=set%20Fibaro_Wall_Plug_1%20on" and ".off").Now I just need to add Virtual Input in Loxone Config.To have it sent to Loxone I need: a) subscribe that topic in MQTT-Gateway plugin and b) convert "off" to value 0 and "on" to value 1, as I'm using UDP.So now I have MQTT topic fhem/Fibaro_Wall_Plug_1/state with value on or off depending on real state of the wall plug.For command set to push all FHEM reading to MQTT see attachment 2 In FHEM I could publish only wall plug state to MQTT, but as I have multiple different devices in FHEM with different readings I'm interested in, it's more convenient for me to push ALL FHEM readings to MQTT.I'm using MQTT-Gateway plugin, that includes Mosquito MQTT broker and an engine for pushing new MQTT readings to Loxone Miniserver over UDP or HTTP.
![loxone eib dimmer loxone eib dimmer](https://www.loxone.com/enen/wp-content/uploads/sites/3/2016/10/EN_KB_Config_DMX_PWM_Function-300x132.png)
![loxone eib dimmer loxone eib dimmer](http://www.comexio.com/wp-content/uploads/2015/09/IO-Server_Rolladen_Anschluss_1.png)
FHEM has all current readings of wall plug, including "state" (see attachment 1)