Livolo touch switches

Hello,

I am looking in Livolo touch switches to use in my new house and would like to integrate it with HA.

Any experience with this (found some older themes only)?

There is more types of this switches(rf, wifi, zigbee…), what would you suggest, what will be the most easyest to implement?

Or maybe some other switches like this(touch) to recommend(must be available in EU)?

im using livolo zigbee switches , but they have bugs in zigbee realisation , so they works…
but on my expirience only on single channel 26 and only you must leave “join” open.
maybe something changed …

I’m using Livolo switches with HA, BUT using Livolo Integration to Alexa as a workaround ( helpers + alexa integration – not perfect but works )

Also March 2022 I got an email from Livolo Support tell me they’re working on a integration for HA for “near future”, an improvement from last year :wink:

Perhaps if more livolo customer push’em thru support this integration could be available sooner.

On the other hand switches compatible with Tuya or Son-off are already integrated in HA.

cheers.

1 Like

Hi SandroP,

I too have Livolo switches and am wodering how you set up that alexa integration to control them via HA?

Probably a very noob question but I am a total HA noob at this point haha.

Thank you.

hi… lotohov posted how to connect Alexa/HA ( no subscription required :wink:)… so at Alexa you just add livolo skill, than Alexa will be able to control Livolo switches. (“Alexa turn on kitchen light”). kitchen light been a livolo switch name.
from HA you can create a switch ( at Helpers) which call a script/trigger to issue a voice command (TTS) to Alexa. issue here will be light status synchronization but it’s a work around.
hope this helps.

1 Like

Awesome, thanks so much Sandro appreciate the help on such a simple question mate.

1 Like

Is there any hack to keep join opened, but drop all unknown devices?)

I connected switches successfully with disabled join by default, but they stop working after sometime. Looks like I need to allow joining by default.

yes, just use whitelist

So I have been using Livolo switches for a 6 month. Maybe my experience could be helpful. Overall I managed to configure them properly but not without tricks.

My home assistant is installed as a docker container, along with MQTT broker and two zigbee2mqtt instances for two zigbee sticks.

One stick is used exclusively for Livolo another one for other devices. Livolo stick is configured according to manual Livolo TI0001 control via MQTT | Zigbee2MQTT. Network is always opened for joining but whitelist is configured to accept only switches.

However I was experiencing some sort of timeout issues with Livolo or my stick. After sometime usually during the day switches were falling from the network. Errors in logs were always different depending on version of stick firmware. The last one I saw was related to route map at zigbee stick. At some point I tired of checking different versions of firmware/containers/etc. The solution I came with is a script which is launched by crontab every 8 hours and restarts zigbee stick by disconnecting and connecting power to it, so all my Livolo devices are kept in network.

#!/bin/bash

hub="1-1" #lsusb -t: {bus}-{port}(.{subport})
port="2"

power_usb() {
  uhubctl -l "$1" -p "$2" -a on
}

unpower_usb() {
  uhubctl -l "$1" -p "$2" -a off
}

docker container stop z2m_livolo
unpower_usb "$hub" "$port"
sleep 60
power_usb "$hub" "$port"
sleep 10
docker container restart z2m_livolo

im working c couple of years in mixed network livollo-tuya-xiaomi-sonoff-ikea-heiman-moes with ha and z2m all fine Network is always opened for joining but whitelist is configured to accept only my devices. chan 26 nothing fall off ) and im using sonoff usb stick

This is an old thread but here’s my experience:

Back in the day when I got into the Livolo bandwagon there were only RF switches available. It took me the best part of a year to set them up with HA and Alexa and finally reach a point where they work at about 85% consistency.

The basic idea was to use a Broadlink RM Pro RF blaster device to learn the RF sequences from my Livolo remotes (I got three), then in HA use the Broadlink integration to trigger the switches. After that, I used the Philips Hue Bridge emulation integration in HA, to expose all of the switches as “fake” philips hue lights on my local wifi network, so that they can be discovered by Alexa and control them with my voice.

Unfortunately, what I discovered soon enough were two major issues. The first was that the Livolo RF switches do not have separate RF sequences for On and Off. They just toggle states between on and off on the same command, with a small cooldown time so that repeating RF commands wouldn’t cause them to switch on and off in quick succession. This meant that any type of automation was nearly impossible as HA would not know (or even assume) the state of a switch, and any voice commands would be moot, as if I said “turn on kitchen light” but the kitchen light was already on, it would turn it off.

The second major issue was that the learning of RF commands on the Broadlink was spotty at best. Very few of the learned codes would actually work somewhat consistently. Most would either not work at all, or manage to turn the switch on or off only 10-30% of the time.

After a while I found the solution in a web app made in javascript (I don’t recall the name of it or the URL, but it is posted in a thread on this forum so you can find it, and hopefully it is still available) which emulated the codes that Livolo remotes produce, and since it is a virtual thing, you could have as many remotes as you want (which is crucial to solve the first problem). The RF command sequences produced by the app produced extremely more reliable results. I had to manually put the codes in the Broadlink integration configuration file on HA, and then pair the switches with those codes, but it resulted in all switches working. But again not at 100%. I still have some switches that depending on the time of day and ambient RF interference might refuse to work and I have to repeat the command until they do.

Now as I said, Livolo RF switches accept a toggle RF command instead of separate On/Off ones. However, they respond to specific states if you send a “set scene” RF command. As such I created two scenes for each switch, one that turns it on and one that turns it off, and that’s why I needed a lot of virtual remotes as each remote only supports limited scenes.

I also used scenes to turn on/off groups of lights.

It has been somewhat frustrating though as sometimes I issue a voice command to shut off all of my roller blinds as I leave the house, only to return home later and discover that one of them did not receive the command and stayed open which is a security risk and has me double checking that all rollers are closing when I am about to leave the house (not to mention that controlling them when away from home through the broadlink app does not guarantee the result and you don’t have visual confirmation to be sure)

Fast forward a few years and technology has advanced, so I have replaced a lot of my lights with colored wifi led bulbs and led strips (mostly by Yeelight and TPLink) essentially deprecating the remote/RF functionality of the Livolo switches.

This in turn presented a new set of problems.

First, in order for the wifi lamps/strips to work and receive wifi/voice commands the livolo switch must be always on, something that is not guaranteed as anyone (a guest or even yourself) can switch them off and then you have to first switch them on before you can control the led lights.

Then, led lights and especially led strips are a tad challenging (wattage wise) to the livolo switches. That’s because the switches in order to recieve RF commands (and light up blue) need to always be powered even when they’re off, as such when you switch them off they still send a very small amount of current through the circuit which is enough to keep them operating but not enough to light up a regular lightbulb. However, led lamps are of low wattage and even small amounts of current might cause them to either dimly light up or flicker. For such cases livolo has issued some small circuits (I think they have a capacitor in them) which you install in the circuit and it solves the flickering issue. I don’t however think that they can work with led strips that use a power supply/transformer as when you switch the led strip off (through wifi) or you set it at a very dim level the livolo switch thinks that no lamp is present and enters a weird standby mode (switch ring does not light up, and does not respond to touch) but there is still power going through the circuit. If you turn the led strip on again through wifi, it will light up normally, however the livolo switch thinks that you just installed a new lamp and to protect you it turns itself off after a couple of seconds. This is also the case for non-remote-control Livolo touch switches. To solve this (and still keep the same livolo black glass panel aesthetics) I had to buy and install a regular push switch.

To solve the issue of RF command reliability for my shutters I resorted to installing Livolo Wifi curtain switches. These switches work flawlessly, but they do require that you have a Livolo gateway so that they can connnect to. I’m not sure if there are wifi switches that do not need a gateway, or if those labeled as wifi are actually zigby ones and just use the gateway to be exposed to your LAN or the cloud. I suspect the second. Personally I prefer having a gateway as this way I do not pollute my wireless network with a lot of IP leases for all my switches.

And then came the most recent problem which I haven’t solved yet and for which I am waiting for a reaponse by Livolo support. In order to get the wifi switches working with alexa, I have to enable the Livolo Home skill. Unfortunately, alexa fails to link your livolo account to the skill every time, which looks like an issue on the Livolo api server.

In addition, the skill has very low review ratings from people who complain that it times out a lot during voice commands and fails to execute them (Alexa reports that the device is unresponsive).

All in all, for all those who are looking into Livolo switches here’s my pros and cons list after many years of experience:

Pros:

  • Beautiful design with the glass feel, touch panel and illuminated ring
  • extremely easy to install
  • quality and durable materials (I bought many switches and all of them worked and are still working)
  • protection features. No matter how you install the wires, the switch will protect itself if you do a booboo with the wiring. I am not an electrician and at points I had to do quite a bit of trial and error, especially for two or three way wiring, and the switches did not blow up :wink:
  • availability of spare parts (glass panels, frames etc)
  • no need for ground/neutral lines
  • multitude of configuration options (single, double, triple, quadruple gangs, two eay, curtains, doorbells, sockets, ethernet etc)

Cons:

  • unreliable operation with RF remote control if you want voice control or automation
  • No switch state publishing (on RF switches)
  • you need a lot of work/hacks and third party services/hardware to set up voice control
  • for some cases the crystal panel does not align perfectly with the capacitive touch switches inside causing touches on the glass panel to not be registered (although rare)
  • crystal panel after installation is not flush against the wall causing dust pileup on the bezel which is a bit hard to reach to clean

I switched to sonof dongle e and now everything works like a charm

1 Like

Hi,

Have the sonoff dongle e and Livolo dimmer switch. I can pair it fine, it works, but then fully drops shortly. Tried all the suggestions listed in z2mqtt site but nothing.

Mind sharing your setup for “everything working like a charm”?

  • Separate dongle for Livolo?
  • Permit join needs to be always on?
  • Whitelisting and how to do that specifically for Livolo

Read online that their gateway might be needed to officially “register” the switch, and then it wouldn’t supposedly drop itself. But yeah, either that or send switches back.

Any details would be much appreciated.

1 Like

Any luck?

I am also using several Livolo switches. The normal on/off ones are usually trouble free (maybe every 3 or 4 months I have to pair them again). However the dimmers are a pain… once paired, they usually work for hours, even though this last time it’s been one or two weeks and they are still up and running. I haven’t changed anything, so no clue why (they had been a year and a half basically not working or working just a few hours)

Ended up returning mine Livolo dimmers.
Sad as the design and quality was good and look-wise similar to my existing glass switches, though the hassle to get it working and then maintaining that was simply too much

Thought about buying another zigbee dongle or even ordering the original Livolo hub, but …meh.

Since my last post I realized that allowing devices to join permanently in Zigbee2MQTT fixed all my issues