Loxone download5/6/2023 ![]() ![]() ![]() ![]() HomeKit has a limit of 100 accessories per bridge. Name changes in Eve are not reflected in Home and thus not known by Siri. Special note: organizing into rooms can be done from Eve, but renaming the items should (unfortunately) be done from the IOS Home app. That is a manual action to be done once using the IOS Home app (or the Eve app which is much more user-friendly). The Homebridge/HAP protocol does currently not allow attaching the Loxone rooms to the accessories. Then you can ask Siri to 'turn on the main light in the kitchen'. Eg LIGHT_KITCHEN can be renamed to 'main light' and added to room Kitchen. Rename them through the iOS Home app to make it more intuitive for using with Siri. The controls will be named like you named them in Loxone Config. This can be used for Homekit automation like triggering a scene to become active. The Doorbell will show 'Not compatible' but it will still send the notification. Sensors, Doorbell, Triggerįor the following accessory's you will have to use a "Virtual Status block" inside Loxone config to make the following sensors. To make a valve or sprinkler accessory you have to give a switch the prefix "Valve" or "Sprinklers". To make a lock accessory you have to give a switch the prefix "Lock". To make a fan accessory you have to give a switch the prefix "Fan". *You can use a different category name as long as the category has the power icon. To make a lightbulb accessory you have to give a switch the prefix "Outlet" or you can give it the power category. *You can use a different category name as long as the category has the lightning icon. To make a lightbulb accessory you have to give a switch the prefix "Lighting" or you can give it the lightning category. The prefixes can be changed in assumption aliases. To create the correct accessory type from Loxone items, some attribute parsing is required inside Loxone config. (Default 'Off')įor more information check assumptions. Optional, time (in seconds) until the lock will auto lock if enabled, default: "5". Optional, whether the lock should automatically lock after being opened, default: "1". Optional, choose at what level the alarm notification will be send to HomeKit, default: "5". Optional, choose between instant and delayed activation of the alarm, default: "delayedon". Optional, displays Loxone radio switches, default: "1". * only : only include moods and filter out any other element. * all : include moods as actionable item. Optional, displays Loxone moods (wich are part of LightControllerV2 elements) as seperate buttons, default: "none". * on : Light will stay on as long as the switch is enabled. * pulse : Normal operation, light will stay on for fixed amount of time. ![]() Optional, choose the switch behavior of the Stairwell Light Switch, default: "pulse". If empty or not given, all elements are used.Įxample: specifying "rooms" : will limit your bridge to only elements from those 2 rooms. Optional, specify an array of interested rooms to filter on. Optional, port of your miniserver (default: 80) See config-sample.json for an example configuration. $ sudo npm update -g homebridge-loxone-connect Configuration Install the plugin through npm or download the files from here. Prerequisitesįollow all the installation steps there. The only configuration required is the credentials to your Loxone miniserver. *Needs additional configuration, check assumptions. Switches (On/Off, Pushbutton, Stairwell, Radio).Sensors (Temperature, Humidty, Light, Motion, Contact, Leak and Smoke)*.Lights (Switches, Dimmers and RGB/ Smart-actor RGBW leds).The plugin will be able to communicate with the following items from your Loxone setup: Those are the two main reason that i made this plugin, i also added a lot of fun and useful stuff. Most of them are abandoned and they don't work completely. There are a few variants from the original loxone homebridge plugin,īut they all have the same problem. Homebridge plugin for controlling Loxone. ![]()
0 Comments
Leave a Reply. |