Steuerung Licht und Beschattung mit den Smarthome Tasten einer Logitech Harmony?

[duncan]

i got is sorted thanks to the advice (i used loxberry mqtt http updates to virtual inputs on the minserver rather than udp), that is until i reinstalled the ubiquiti controller on the loxberry, which totally killed the iobroker installation but left the loxberry function working still

the combination failed a second time as well so there seems to be a compatability issue between iobroker or one of its plugins and ubiquiti
ubiquiti coexists with the loxberry software fine

ill have to start again with a new setup, but put ubiquiti on another pi

[TomekWaw]

Ubiquiti controler is Java.... heavy. Better to have it somewhere separate.
And Unifi adapter in ioBroker is ok, but it's tricky.
My advice: from insane amounts of data/object that it provides it's worth to select only one: Clients -> is_online. That's all you probably need. It makes the number of unifi objects minimal.

[duncan]

thanks for the advice:

im going to put the ubiquiti controller on a separate pi

i dont need any data elements from ubiquiti brought into iobroker/loxone so ill not install the iobroker unifi adapter

[duncan]

a further question:

ive got this all working thanks to your help and decided to see if i can control the harmony hub using mqtt instead of the simple API
in iobroker ive enabled mqtt on the harmony functions eg 'Sky' for subcribe and publish

i can read the state of the harmony activity in the loxberry mqtt - i can see
iobroker/harmony/0/bedroom1/activities/Sky is visible as harmony_0_bedroom1_activities_Sky with its number eg 0 for off, 2 when on

now if i modify the mqtt from loxone using a virtual output to the loxberry using udp i can change
harmony_0_bedroom1_activities_Sky 0 to harmony_0_bedroom1_activities_Sky 1 but the harmony iobroker entry doesnt change and the harmony doesnt turn on

any ideas why loxone can change the mqtt broker but the mqtt broker doesnt modify the iobroker/harmony hub?
my iobroker mqtt settings are:

duncan

To execute Harmony commands from Loxone (both from Media Controller remote or wall button) you need to:

1. Add Simple RestFul API adapter to ioBroker
2. Configure it to a not used TCP port (I believe I'm using the default)
3. Add Virtual Output and VO Commands as below:

Virtual Output Adress: http://192.168.X.Y:8087 (X.Y - is your ioBroker IP address)

Virtual Output Commands (few examples):

activity Netflix
Command for ON: /set/harmony.0.Harmony.activities.Netflix?value=1

activity Spotify
Command for ON: /set/harmony.0.Harmony.activities.Spotify?value=1

activity Off
Command for ON: /set/harmony.0.Harmony.activities.currentStatus?value=0

command AVR VolumeUp
Command for ON: /set/harmony.0.Harmony.AVR.VolumeUp?value=1

command AVR VolumeDown
Command for ON: /set/harmony.0.Harmony.AVR.VolumeDown?value=1

command TV Info
Command for ON: /set/harmony.0.Harmony.TV.Info?value=1

command TV Select
Command for ON: /set/harmony.0.Harmony.TV.Select?value=1

command PVR Play
Command for ON: /set/harmony.0.Harmony.PVR.Play?value=1

command PVR Stop
Command for ON: /set/harmony.0.Harmony.PVR.Stop?value=1

command FR Play
Command for ON: /set/harmony.0.Harmony.FR.Play?value=1

command FR Pause
Command for ON: /set/harmony.0.Harmony.FR.Pause?value=1

You get the idea.
Netflix, Spotify - those are examples of my Harmony activities.
AVR, TV, PVR, FR - those are the names of my Harmony devices.

The list of commands is pretty long and I recommend to create them as an XML virtual output template file and then just import.



For the incoming data from ioBroker to Loxone (current activity - that's the only info Harmony provides) it's best to use MQTT-client adapter and publish to topic loxone/harmony/0/Harmony/activities/currentActivity

Then you also need to add some MQTT Conversions. Mine are:

PowerOff=0
Television=1
Netflix=2
YouTube=3
Spotify=4
Music=5

I'm sure you get it.

I might make a tutorial out of this on LoxWiki some day.

[TomekWaw]

First you should always remember to uncheck "ack" flag on subscribe settings (this is based on my experience with ioBroker MQTT).
Second: remember to reset this topic to 0 again (from Loxone) as this should be a pulse not a state.
Haven't tried but should work fine.