[Request Device Support] Tint remote control by Müller-Licht

[Thomas-Vos]

Hello, would it be possible to add support for the Tint remote control? This is a Zigbee remote control made by Müller-Licht. I was able to add the remote to deCONZ by pressing the reset button in the battery compartment and starting a sensor search.

Clusters of the node:

Basic cluster:

Node info panel:

[blaupert]

Yes! Another requests to add this Remote Devices from me!

[ghost]

Any news here?

Trying to connect my Tint remote with deconz.

But the sesor search in not finding my remote.

How did you connect it?

[Thomas-Vos]

How did you connect it?

Press the reset button in the battery compartment and start a sensor search. It won't be visible in Phoscon because support for this remote has not been added yet.

[realwax]

+1 on the request list for Müller tint support of the remote. Thank you very much!

[Philje123]

Just bought a GU10 and remote so hoping for support in the future.

I noticed Also are selling these off cheap now (€14 for the GU10 RGB + remote, €5 for the GU10 white and €7 for GU10 RGB). That's all they had.

So is the remote usuable as it is? Does it publish anything to the API?

[ghost]

@Philje123 Short form: YES

If you are starting a sensor search from the api, you will get the address and the id of your remote control.

But it does NOT appear in Phoscon app.

[Philje123]

Thank you.

That will be fine as I mainly use home assistant to control my lights so as long as it the message gets through to there i can set it up to do what i want.

[Philje123]

Any update on this?

I've tried to use the remote in it's current form but I don't get anything showing in Hass.io when I listen to "deconz_event". Do the remote buttons not get pushed through this way?

[ghost]

Nope ...

Push

[GottZ]

somehow i think about abandoning raspbee now and moving over to a direct zigbee binding in openhab2

this missing device support is kind of annoying.

sadly it's not even open source.

[ink0gnito]

it would be nice if this remote were supported

[StevusPrimus]

Vote +1 for an integration

[drumdum]

Count me in as well. Is there anything to be done by people having this remote to ease the integration? I am willing to test and give information needed. Just give a heads up.

[snador1977]

Vote +1 for an integration

[Expodermius]

I managed to connect the tint remote with the system and it was possible for me to pair it with the lightbulbs and using the remote control, the groups in Phoscon app and the Hue Essentials app on android at the same time. But after a while the remote control does not react anymore and I have to pair it again with the bulbs. The new pairing leads to conflicts in the Phoscon app and I have to assign all light devices in the groups once again. A similar problem when I restart the Raspberry Pi with RaspBee module. After reboot not only the remote control but also the groups in Phoscon app don´t work and everything has to be set up once again. Does anybody have the same problems and maybe a solution for it?

[Manlycookiebear]

I also would be grateful, if this device could be added to Phoscon.

[monotek]

+1

Remote and bulps are also available in Globus Baumarkt.

[GottZ]

just fyi: the remote bundled with lamps was available in aldi süd in germany again potentially increasing market share of this product yet again.

there is also zigbee light strips from müller-licht now. i bought two of them so if you need any deconz output just ping me.

[Viguri]

I also got the pair, E27 bulb and the remote... just if anyone needs testing. A question, how do you pair the bulb with homebridge (raspbee)??

[monotek]

I also got the pair, E27 bulb and the remote... just if anyone needs testing. A question, how do you pair the bulb with homebridge (raspbee)??

I've used the deconz app. Started search for new light. Switched the light on and off several times and it was there...

[Viguri]

Thanks monotek, I did it like that... It will be nice to be able to use the remote... If there's a way I could help, just ask me. Thanks!!

[monotek]

I was not able to pair the remote with openhab. But I've read somewhere you can pair both devices. So you can switch the light with the remote & openhab for example.

[maikkoe]

First you have to pair the bulb and after that you can pair the bulb with the remote

[muetzekoeln]

+1

just bought a black one in Toom market

[Karl-Napp]

me too!

[ralfkaminski]

I was not able to pair the remote with openhab. But I've read somewhere you can pair both devices. So you can switch the light with the remote & openhab for example.

Hello, This solution works only for some minutes after you Have connected remote with the bulb. Then you Have to reconnect it again. So it would be very nice, if the remote will be supported by deconz directly.

[turricanus]

I'd like a solution for a direct pairing in the phoscon app also. Thanks in advance.

[monotek]

next week at aldi again...

[Shamal2008]

I would also appreciate support of Tint within Phoscon. I think about it, to buy LED-Panels with Zigbee and Remote for 3 rooms.

So +1 for Support

[Klagio]

Still not supported?

[Klagio]

Thank you.

That will be fine as I mainly use home assistant to control my lights so as long as it the message gets through to there i can set it up to do what i want.

I use home assistant too, how do you add it directly without the deconz integration??

[Klagio]

Usually deconz team are fast in adding products.

This time no, some German rivalry?

[DocEverdream]

+1

[Xshakma]

+1

[fdnic99]

With my Raspbee the remote is visible in deconz, but it seems not to be paired, Phoscon doesn't show the remote and the Plugin doesn't send any signal when buttons are pressed.

So please intrgrate! +1

[nerdiges]

+1

[Klagio]

+1

[bortim]

At the moment the remote can be bought in Amazon Germany for 15 €. Maybe this is interesting for a developer.

Maybe @ebaauw or @SwoopX needs one. 😊

Otherwise is there any documentation on how to add new devices as a pull request?

[ebaauw]

No, I'm sorry, I don't need one. Have plenty of unused remotes lying around already. For me this is a hobby, and I don't want to spend money on devices I'm not going to use myself.

I'll be happy to have a look at it, if some-one can lend me or donate one.

[ghost]

I can send my over, not needed right now.

[ebaauw]

Please PM me on Discord for my address details.

[bortim]

Hello @serenity182 and @ebaauw, thank you very much!

[ebaauw]

@serenity182 I received the remote yesterday, thanks Marc!

Does any-one have a manual for this remote? I can only find an uninformative Datenblatt on the Müller web site. I'm not sure I understand all the nuances of the remote.

My first impressions:

• To reset the remote, hold the little button in the battery compartment for 5+ seconds until the red LED blinks quickly. After that, I pairs to deCONZ without any issue.
• It's a ZHA Color Controller, but with a ZLL Commissioning cluster. The cluster reports four groups, but the device seems to send commands to different groups? Also, I cannot seem to get the remote to use the fourth group.
• No Power Configuration cluster, but the Power Descriptor seems legit.
• The remote has state. Pressing the On/Off button cycles between sending On and Off. No hold nor long presses.
• Pressing or holding the colour wheel results in a Move to Color command. The xy values depend on the last values sent and where on the wheel you press or hold. I think the wheel has four different contacts (let's call them North, East, South, West). Each press "moves" the xy values towards the corresponding point on the CIE 1931 colour space: North: (0.3010, 0.1487) - pink-ish, East: (0.7, 0.3) - red, South: (0.3726, 0.5885) - green-ish, and West: (0.1164, 0.3473) Turquoise-ish. A hold "moves" directly to the corresponding point. So e.g. to get yellow, hold South for green-ish and then press East to move towards red. There seem to be eight steps between adjacent directions; opposite directions go through an in-between direction: East/West over South; and North/South over East. So a total of 36 different xy values.
• Pressing the Warm and Cool button sends Move to Color Temperature. It seems to remember the colour temperature and use for steps: 153, 200, 250, and 370. Warm goes up one step, Cool goes down one step.
• The DimDown and DimUp buttons behave fairly standard: Step on press; Move on hold, and Stop on release (after hold).
• The six scene buttons send a Write Attributes to manufacturer-specific (0x121b) uint8 attribute 0x4005 of the Basic cluster. The value indicates the scene, although the order is a bit odd: Read: 3, Day: 1, Disco: 2, Night: 6, Fire: 4, Love: 5.
• The multi-light button doesn't send anything, but cycles between the groups. I cannot seem to find out what all it means when all four green LEDs are lit. I would expect a broadcast or fourth group, but the remote doesn't seem to send anything.
• The groups used by the remote are 0x4004 (left green LED), 0x4005 (middle), 0x4006 (right). I expect these to be picked at random when the remote is reset. The ZLL Commissioning cluster reports groups 0x8bd3, 0x8bd4, 0x8bd5, and 0x8db6. I'm not sure whether to trust this: Wireshark reports malformed packages (actually both on the Get Group Identifiers Request and on the Get Group Identifiers Response), and the device sends commands using different groups.

Exposing this remote will be interesting:

• I need to figure out how to deal with the groups. Other devices sending commands to multiple groups use different source endpoints. Based on that, we know to which position in config.groups the group corresponds. As long as you only use one group, it's probably OK to use a single value in config.groups, but I'm worried the REST API might want to delete the previous group when switching to the next, thinking the remote has been configured for a new group;
• The On/Off, DimUp_, DimDown and scene buttons are pretty straightforward: 1002, 2001, 2002, 2003, 3001, 3002, 3003, and six x002 button events;
• The Warm and Cool buttons might be a bit challenging, as the REST API plugin needs to remember the last value and compare the current value to deduce which button was pressed. I think I've already done something similar for the Lutron Aurora;
• I won't be possible to deduce which area on the wheel is pressed: when e.g. you're at full East, pressing South and West result in the same new xy value. On first attempt, I think I'll simply expose the wheel as a single button (x002).
• It will be possible to link each of the 36 xy values to an angle representing the colour sent (rather than the position pressed or held). Not sure how best to expose that: it doesn't quite fit button event nor rotary event nor tilt angle. Could also expose state.xy with a note that it's only valid for the corresponding button event value x002.

[UweRP]

Unter https://www.mueller-licht.de/fileadmin/404013_tint-BDA_021.pdf gibt es eine Anleitung für das Set in der auch die FB beschrieben wird.

[Thomas-Vos]

Great to see you are looking into this @ebaauw!

• The multi-light button doesn't send anything, but cycles between the groups. I cannot seem to find out what all it means when all four green LEDs are lit. I would expect a broadcast or fourth group, but the remote doesn't seem to send anything.

My remote only has three LEDS at the bottom. When all three are lit, it controls the lights in all of the three groups.

• I won't be possible to deduce which area on the wheel is pressed: when e.g. you're at full East, pressing South and West result in the same new xy value. On first attempt, I think I'll simply expose the wheel as a single button (x002).
• It will be possible to link each of the 36 xy values to an angle representing the colour sent (rather than the position pressed or held). Not sure how best to expose that: it doesn't quite fit button event nor rotary event nor tilt angle. Could also expose state.xy with a note that it's only valid for the corresponding button event value x002.

A single button event looks like the easiest way for now. With just a simple button event, an app could configure the rules to send a hue_inc/xy_inc command to cycle through the colours. Unfortunately there is no way to match the light colour to the colour wheel this way.

A state.xy would be interesting, but I am not sure how that could be used in the rules. What about something like state.angle? It would be easier to configure the rules that way.

A ZLLRelativeRotary sensor could also be used. This way it is possible to detect if the wheel is "rotated" to the left or the right. (alternatively left/right rotation could be two button events?). A drawback of using a rotary sensor is that it is still not possible to know exactly which colour to send to the light.

[ebaauw]

The manual does give some more insights:

• It confirms the four contacts on the colour wheel, and the short vs long press function.
• When holding the Warm and Cool buttons the remote sends some more values with Move to Color Temperature, all the way up to 555 mired (down to 1800 K). Unfortunately, the API cannot distinguish between press and hold.
• The scenes, of course, have more inspiring names than what I can come up with: Work Light, Sunset, Party, Night Light, Campfire, Romance. From the description these would actually trigger dynamic effects on the lights (except for Work Light and Night Light). Might be cool to expose these through the API using state.effect on the /lights resource.
• The fourth group is actually the other groups combined (makes kinda sense as all green LEDs are lit). I think it works only when lights are touch-linked to the remote.

[ebaauw]

My remote only has three LEDS at the bottom. When all three are lit, it controls the lights in all of the three groups.

I assume you touch-linked the lights to the remote? Or are using the out-of-the-box pairing?

A state.xy would be interesting, but I am not sure how that could be used in the rules. What about something like state.angle? It would be easier to configure the rules that way.

My thoughts exactly. There is already a state.tiltangle (for the vibration sensors).

A ZLLRelativeRotary sensor could also be used. This way it is possible to detect if the wheel is "rotated" to the left or the right. (alternatively left/right rotation could be two button events?). A drawback of using a rotary sensor is that it is still not possible to know exactly which colour to send to the light.

I suppose when remembering the previous xy value / absolute angle, the relative (delta) angle for the rotaryevent could be deduced. I'm not sure that's very informative, though. It would be +10° or -10° for presses, and anywhere between -170° to 180° (in 10° steps) for hold, with no clue about the position pressed, nor the current colour. The absolute angle would seem far more useful.

[Thomas-Vos]

I assume you touch-linked the lights to the remote? Or are using the out-of-the-box pairing?

This was without deCONZ. I just paired the remote to the lights like described in the manual.

[ebaauw]

First attempt, but I think I nailed most of it.

config.group will be populated with the three groups, as the remote sends commands to them. The corresponding /groups resources should be created as config.group is populated. Note that the uniqueid of the /groups resources isn't.

I use the same buttonevent values for all groups, see the table below:

buttenevent	button	action	remarks
1002	On/Off	press
2001	DimUp	hold
2002	DimUp	press
2003	DimUp	long release
3001	DimDown	hold
3002	DimDown	press
3003	DimDown	long release
4002	Warm	press, hold	multiple 4002 events while holding
5002	Cool	press, hold	multiple 5002 events while holding
6002	Colour Wheel	press, hold	see below
7002	Work Light	press
8002	Sunset	press
9002	Party	press
10002	Night Light	press
11002	Campfire	press
12002	Romance	press

Note that there's no way to tell holding the colour temperature buttons (Warm and Cool) from pressing them. Holding them could result in multiple x002 events, as long as the temperature is changing.

Note that state.xy and state.angle are updated only on buttonevent 6002. If you set websocketnotifyall to false, they'll only be included in the web socket notification when they change.

The is one unsolvable bug: when you hold Warm, ct will go up to 555. If you then press Warm, it goes down to 370, which generates a 5002 instead of a 4002, same as pressing Cool in that situation. There is no way to tell these buttons apart in this case.

For completeness: here's the /sensors resource:

$ ph get /sensors/16
{
  "config": {
    "group": "16388,16389,16390",
    "on": true,
    "reachable": true
  },
  "ep": 1,
  "etag": "3e8679bd6e84ebfefca53031ae2a62c9",
  "lastseen": "2020-05-30T18:44:50.385",
  "manufacturername": "MLI",
  "mode": 1,
  "modelid": "ZBT-Remote-ALL-RGBW",
  "name": "Tint",
  "state": {
    "angle": 90,
    "buttonevent": 1002,
    "lastupdated": "2020-05-30T18:44:50.386",
    "xy": [
      0.7,
      0.3
    ]
  },
  "swversion": "20180605-17",
  "type": "ZHASwitch",
  "uniqueid": "00:15:8d:00:03:41:88:92-01-1000"
}

And the /groups resources (again, with a non-unique uniqueid):

$ ph get /groups/16388
{
  "action": {
    "bri": 127,
    "colormode": "hs",
    "ct": 0,
    "effect": "none",
    "hue": 0,
    "on": false,
    "sat": 127,
    "scene": null,
    "xy": [
      0,
      0
    ]
  },
  "devicemembership": [
    "16"
  ],
  "etag": "3e8679bd6e84ebfefca53031ae2a62c9",
  "id": "16388",
  "lights": [
    "7"
  ],
  "name": "ZBT-Remote-ALL-RGBW 16",
  "scenes": [],
  "state": {
    "all_on": false,
    "any_on": false
  },
  "type": "LightGroup",
  "uniqueid": "00:15:8d:00:03:41:88:92"
}
$ ph get /groups/16389
{
  "action": {
    "bri": 127,
    "colormode": "hs",
    "ct": 0,
    "effect": "none",
    "hue": 0,
    "on": false,
    "sat": 127,
    "scene": null,
    "xy": [
      0,
      0
    ]
  },
  "devicemembership": [
    "16"
  ],
  "etag": "cb3c2706803fd865a2c20362806d8427",
  "id": "16389",
  "lights": [],
  "name": "ZBT-Remote-ALL-RGBW 16",
  "scenes": [],
  "state": {
    "all_on": false,
    "any_on": false
  },
  "type": "LightGroup",
  "uniqueid": "00:15:8d:00:03:41:88:92"
}
$ ph get /groups/16390
{
  "action": {
    "bri": 127,
    "colormode": "hs",
    "ct": 0,
    "effect": "none",
    "hue": 0,
    "on": false,
    "sat": 127,
    "scene": null,
    "xy": [
      0,
      0
    ]
  },
  "devicemembership": [
    "16"
  ],
  "etag": "2aea617ebc2640c6e997b1869e8e49c3",
  "id": "16390",
  "lights": [],
  "name": "ZBT-Remote-ALL-RGBW 16",
  "scenes": [],
  "state": {
    "all_on": false,
    "any_on": false
  },
  "type": "LightGroup",
  "uniqueid": "00:15:8d:00:03:41:88:92"
}

[Klagio]

@ebaauw thanks a lot for your work. I have a sitting remote, that soon thanks to you will come back to life