Homebridge-loxone-proxy NPM

Homebridge Loxone Proxy

Homebridge Proxy which exposes a Loxone System to Homekit.

The plugin uses Loxone Lxcommunicator to setup a websocket connection to a Loxone miniserver. It retrieves the loxone StructureFile and tries to map all items to HomeKit accessories.

Mapped Items

loxone Item	HomeKit Accessory	Mapping	Note
`Alarm`	SecuritySystem	Auto
`Brightness`	LightSensor	Manual	Requires an alias in the config.
`ColorPickerV2`	Lightbulb	Auto	Individual ColorPickers, or items parsed from LightControllerV2.
`Dimmer`	Lightbulb	Auto	Individual Dimmers, or items parsed from LightControllerV2.
`Gate`	GarageDoorOpener	Auto
`Humidity`	HumiditySensor	Manual	Requires an alias in the config.
`IntercomV2`	Doorbell, MotionSensor, Camera	Auto
`IRoomControllerV2`	Thermostat	Auto
`Jalousie`	Window Covering	Auto
`Lock`	LockMechanism	Manual	A switch with an alias that is defined in the config.
`MoodSwitch`	Switch Group	Auto	all LightControllerV2 moods are mapped to a Switch Group as a seperate switch.
`Motion`	MotionSensor	Manual	Requires an alias in the config.
`PresenceDetector`	OccupancySensor	Auto
`Switch`	Switch, Outlet, or Lightbulb	Auto
`Ventilation`	Fanv2	Auto

Manual mapping

Some items cannot be mapped automatically and require a naming convention to be recognized. For example, giving all motion detectors the convention "MoXX" in Loxone Config and then setting the alias "Mo" in the plugin will result in all items with "Mo" in the name being recognized as motion detectors.

Items that require an alias are listed in the table above.

Limitations

Apple does not allow more than 150 items per bridge. This plugin will not map more than 150 items, but if you have other plugins activated, you might still hit this limit. To prevent this you can run this plugin as a child bridge. Another way to solve it is to use a dedicated loxone user for the plugin and only expose the items that you want to use in HomeKit.