

Do this, then select ‘Learn’ in the EIB window, not ‘Monitor’! You can then quickly and easily insert group addresses for your EIB actuators and sensors. To use the EIB Learn Mode, you must first enable the EIB monitor.

To make this possible the following settings must be set in the ETS Connection Manager.Ĭlicking on the EIB Search function lists all devices that are configured in the EIB installation. The Miniserver is automatically detected by ETS as a gateway. The Loxone Miniserver acts as a full IP gateway which enables you, for example, to program with ETS directly on the local network.
Loxone eib dimmer software license#
GENERALįor the KNX bus a separate and product specific power supply needs to be used (the KNX/EIB power supply).įor addressing and configuration of the sensors/actuators a full ETS programming software license is required. The number needed depends on the size of the rest of the program. In addition, NAT Mode must be activated in ETS.Īn accurate number of required EIB sensors/actuators will vary. In order to program KNX devices remotely, the following port must be forwarded to the Miniserver: EIB function blocks in the Configuration Software.STREAM* pTcpStream = stream_create("/dev/tcp//80/api//groups/1",0,0) // create tcp streamĬhar* pTcpCmd = "GET /api//groups/1 HTTP/1. 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#
Create a Program functional block and put the source code at the bottom of this post in it.Connect the Q output to this virtual output command.Create (you probably already have it) a virtual output command to send commands to hue.Connect the virtual input to the state input of the EIB push button.Create a EIB push button functional block to control the hue bulbs.Create a virtual input that holds the state of the hue bulbs in a room (defined in hue app).I do know the feeling :-) Loxone makes simple tasks very difficult sometimes. You will probably figure out all details on your own, if not - just ask me for details on the very specific points of this mini-howto 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.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
