Miele Home Automation API

It’s annoying to have ‘smart’ devices that can only interact with the manufacturer’s own website or smartphone app. Much better is for them to have an API which can hook into other home automation systems, either to bring everything together in one user interface or to support automation logic (like running the dishwasher when electricity is cheapest).

Miele have been exploring various options for home automation over the years and they’re in the process of moving from a peer-to-peer ZigBee architecture to a Cloud-based WiFi solution.

There’s been a smartphone app for a while (MIele@mobile) which clearly uses an API to connect to the Cloud-hosted back-end and now the “3rd Party API” is official released for other uses.

More info at https://www.miele.com/developer/index.html

There’s also some work ongoing to hook this into openHAB and MQTT; see https://community.openhab.org/t/cloud-based-miele-home-to-mqtt/52155

IT Installation Tidy-Up

There are a total of 120 Ethernet network outlets distributed around the house which terminate in 5 x 24-port patch panels on the second floor. Some of these are used for specific fixed items like CCTV cameras (x5) and wireless access points (x6) whereas others are available in case there is a need to connect a portable device in a particular location. It’s highly unlikely that all of the outlets will be in use at any one time so there’s no need to have 120 switch ports available. Initially I started with a single 48-port switch which has been adequate up to now but the plan was always to have a second 48-port switch which I’ve just installed.

The primary driver for the second switch is to double the port capacity but a secondary factor is that switches can fail and having two provides a degree of redundancy. Many of the devices rely on Power over Ethernet (PoE) which means that both switches must support PoE, which is unfortunate because PoE-capable switches are roughly double the price of non-PoE switches.

Adding the second switch made it possible to greatly simplify the wiring to the patch panels, which now looks a lot tidier.

Patch panels, network switches and supporting equipment

The Ethernet switches (painted silver) are 48-Port UniFi models from Ubiquiti Networks, each capable of supplying 500W of PoE. These are linked together using 2 x 10 Gb/s UniFi DAC cables in their SFP+ ports (the black cables connecting to the right of each switch) so they pretty much act as one 96-port switch. However, strictly speaking they are not stackable switches which means they must be configured separately (no big deal) and also means they don’t support the more advanced types of link aggregation across the two switches.

The plan is now to re-configure the main Router/Firewall (the red box at the top) to be wired to both switches in an Active-Backup configuration, so its connections will flip over to the second switch in the event of a problem with the first switch or with one of the ports or the cable. So far I haven’t decided whether to do the same with the HP MicroServer or to leave that with 2 x 1 Gb/s connections into just one switch (using LACP which uses both cables to provide high availability and also double the bandwidth).