#Loxone eib dimmer full#
Taking advantage of full flexibility, it was easy to design freely and plan for future. 4 dimming channels 120V (200 watts per channel) universally applicable for resistive, capacitive and inductive load 8 digital inputs (24VDC) Top hat rail mounting ETL Listed LoxLink. 2 Compatible products to Loxone Dimmer Extension Relay extension with fourteen 16A rated relay. The dimmer has 4 outputs that can handle up to 50W 24VDC per output for LEDs. I have tried resetting the whole installation, checked the wiring, reconfigured the extension. With the Loxone Dimmer Extension, you can easily dim all common 230V lamps - from conventional light bulbs to LED lamps. Everything works fine but 1 dimmed output only keeps giving me between 30 and 40v AC. Egyszerre tudunk világítást vezérelni, ellenőrizni a garázsajtó pozícióját, továbbá ellenőrizhetővé válik pl. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. STREAM* pTcpStream = stream_create("/dev/tcp//80/api//groups/1",0,0) // create tcp streamĬhar* pTcpCmd = "GET /api//groups/1 HTTP/1.Objednáno Kód: 100029. 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#
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 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.FHEM has all current readings of wall plug, including "state" (see attachment 1) I'm using FHEM Plugin to manage my Z-wave devices.Hi will describe it for you briefly in points.