Lawrence's Musings

  • Archives

Webbrick and Loxone Miniserver Migration

Sun 01 December 2013
By Lawrence Klyne

In OSS.

tags: webbrickloxone

The idea of editing a large amount of entries into a Loxone Miniserver configuration did not appeal, so I wrote some python to scan webbrick configuration files and create the entries in the LoxPlan file.

This is aimed at where during migration you want to be able to have the Loxone minserver coexist with existing webbricks. The example case for me

Digital Inputs.

The udp listener is added to listen for the UDP events and then VirtualUdpInputs are created for webbrick inputs whose channel name has been changed from the factory defaults.

Digital Outputs.

An entry is created for the webbrick under VirtualOuputs and then entries created for all outputs whose channel name has been changed from the factory defaults. The on and off command are implemented.

Analogue Outputs.

Are not yet implemented

Others

At present I have done nothing with the other UDP events for the temperature/analogue values or alarms. The scenes are also not currently used.

Rerunnable

The code can be rerun as it does not overwrite or duplicate existing entries in the Loxone config.

Issues

A typical webbrick system uses swithes that pull to ground whilst a Loxone system has switches pulling to 24V. So when connecting existing switches to the Loxone controller, unless it is easy to connect the switch to 24V you will need pull up resistors of 5K (or less). I think this 24V supply to the switches should be on a auto reset fuse of some sort, maybe it is.

Follow up

An adaptor to connect rotary encoders to a Loxone Miniserver using an RS232 interface.

Categories

  • General
  • Hardware
  • Java
  • OSS
  • python
  • raspberry pi

Blogroll

  • About

Social

  • atom feed
  • LinkedIn
  • Github
Proudly powered by pelican, which takes great advantages of python.

The theme is «notmyidea-cms», a modified version of «notmyidea», the default theme.