Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lidl Melinera Smart LED string lights #3716

Closed
sonar98 opened this issue Nov 20, 2020 · 101 comments · Fixed by #3953
Closed

Lidl Melinera Smart LED string lights #3716

sonar98 opened this issue Nov 20, 2020 · 101 comments · Fixed by #3953

Comments

@sonar98
Copy link

sonar98 commented Nov 20, 2020

Device

  • Product name: The device name as shown on the product or package.
  • Manufacturer: _TZE200_s8gkrkxk
  • Model identifier: TS0601
  • Device type : Light

Screenshots

cluster-of-node

node-info

basic-cluster-1

basic-cluster-2

cluster-colorcontrol-1

cluster-colorcontrol-2

cluster-colorcontrol-3

cluster-colorcontrol-4

cluster-colorcontrol-5

@Mimiix
Copy link
Collaborator

Mimiix commented Nov 20, 2020

What is missing on this one?
seems to be alright?

@sonar98
Copy link
Author

sonar98 commented Nov 20, 2020

Choosing a color is not working correctly. Colors do not match the choosen color.
And the lights have buttons for different programs. These are not available in zigbee.

@Mimiix
Copy link
Collaborator

Mimiix commented Nov 23, 2020

@Smanar Can you include this 😃?

@Smanar
Copy link
Collaborator

Smanar commented Nov 23, 2020

I m searching the product to have information, but a part a video on youtube, and not sure was the same.
Do you think you can act on button using zigbee ? (instead of using them manually ?)
Do you have seen something special about color ? For exemple orange instead of blue ?

For button, if you enable log, you will be probably able to see log starting with
"Tuya debug X: xxxxxxxxxxxxxxxxxxxxx"

When using them

@sonar98
Copy link
Author

sonar98 commented Nov 24, 2020

How can I enable log? Is that possible on a RPI or windows computer?

@Mimiix
Copy link
Collaborator

Mimiix commented Nov 24, 2020

@sonar98 From deconz gui click "Help" and click "debug view"

@sonar98
Copy link
Author

sonar98 commented Nov 24, 2020

I tried but I don't see any line starting with: "Tuya debug X

@Mimiix
Copy link
Collaborator

Mimiix commented Nov 24, 2020

Even if you enable all ?

@Smanar
Copy link
Collaborator

Smanar commented Nov 24, 2020

You will have this kind of log every time the device use the tuya cluster. So try to use the switches on the devices.

BTW which one color have you instead of full red, full blue and full green ?

@sonar98
Copy link
Author

sonar98 commented Nov 24, 2020

When I switch it on I see:
16:58:12:200 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:12:200 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:12:397 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:12:399 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:12:599 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:12:600 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:12:803 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:12:804 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:12:997 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:12:999 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:13:191 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:13:192 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:13:393 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:13:394 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:13:684 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:13:686 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:13:794 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:13:795 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:13:999 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:000 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:14:189 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:190 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:14:391 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:392 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:14:592 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:593 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:14:797 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:798 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:14:983 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:14:984 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:15:188 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:15:189 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:15:390 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:15:391 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:15:595 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:15:597 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:15:783 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:15:785 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:15:988 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:15:990 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:16:188 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:16:190 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:16:380 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:16:382 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:16:603 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:16:604 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:16:782 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:16:784 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1
16:58:16:984 Tuya debug 4 : Address 0x588E81FFFEDB7E9A Payload 00280101000101
16:58:16:986 Tuya debug 5 : Status: 0 Transid: 40 Dp: 257 (0x01,0x01) Fn: 0 Data 1

But when pushing the buttons nothing happens

@Smanar
Copy link
Collaborator

Smanar commented Nov 24, 2020

Hooow, I think we can call this spam ^^, 10 request by seconds.

And yes 0x01 0x01 is good, like you said, it s generaly the command used to turn on a device.
But useless, as the cluster 0x0006 is already working

Unfortunately, the tuya cluster is the only one possible to receive information about the switches.

Do you know if the official lidl app can change the programs too ?

@sonar98
Copy link
Author

sonar98 commented Nov 24, 2020

I don't know (yet). The Lidl app only works with the silvercrest gateway. Friday there Will be a special offer in the shop. I will try to get a silvercrest gateway to test the capabilities.

Screenshot in the commercial looks like it is possible

https://www.voordeelmuis.nl/img/jpg/2786/2786583.jpg

@Smanar
Copy link
Collaborator

Smanar commented Nov 24, 2020

Do you have a picture of the switches on the device ?

Perhaps it s memorised scene, but the "setting" of the scene can come from another device, you can change locally the programs and it s working, but nothing usefull is visible on log ? (other than tuya debug)

@sonar98
Copy link
Author

sonar98 commented Nov 24, 2020

There are two physical buttons.

  1. Color
  2. Function

@Smanar
Copy link
Collaborator

Smanar commented Nov 25, 2020

And what they are doing ? You don't see anything on log when using them (about scenes for exemple), even it s not tuya cluster ?

@alex3305
Copy link

alex3305 commented Nov 26, 2020

An online manual is also available for this device. And this seems to be the Zigbee Alliance certification.

@Smanar
Copy link
Collaborator

Smanar commented Nov 26, 2020

Ok I hve found some informations on z2m https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/HG06467.md

But How to use those with deconz ...
Perhaps using "state/effect" for effect, "state/colorloopspeed" for speed and for color will see later ...

@sonar98
Copy link
Author

sonar98 commented Nov 26, 2020

Is this usefull?

Koenkk/zigbee-herdsman-converters#1799

@Smanar
Copy link
Collaborator

Smanar commented Nov 26, 2020

Yep, but I prefer avoid to make a so hudge code for a device used only 1 month by year ^^
I have checked the deconz code, I think I will avoid to use the api command just for that, I will use an hidden command with same parameter than the z2m code, like that I will not break the deconz code, and can make all the code in a separate file.

Do you have the json generated for this device ?

Do you need some return from it, or just be able to ask for effect ?

@sonar98
Copy link
Author

sonar98 commented Nov 26, 2020

"5": {
		"etag": "d47e9d5b3db50b4459f4ed3e1bd203cc",
		"hascolor": true,
		"lastannounced": null,
		"lastseen": "2020-11-24T13:16Z",
		"manufacturername": "Heiman",
		"modelid": "TS0601",
		"name": "Color dimmable light 5",
		"state": {
			"alert": "none",
			"bri": 2,
			"colormode": "xy",
			"effect": "none",
			"hue": 65018,
			"on": true,
			"reachable": false,
			"sat": 127,
			"xy": [
				0,
				0
			]
		},
		"swversion": null,
		"type": "Color dimmable light",
		"uniqueid": "58:8e:81:ff:fe:db:7e:9a-01"
	}

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 26, 2020

The user manual is online, https://www.lidl-service.com/cps/rde/xchg/SID-1FC8C7D5-504DC4E3/lsp/hs.xsl/product.html?id=5019460647&title=LED-verlichtingsketting&count=1.

Strip is for inside and outside use. No individual control of lights (at least from the app), but 16 pre-programmed effects. The app seems to support selecting speed and colours for (some of the) effects.
Looks like we'll need their gateway to sniff how to set the effects. EUR 70 for gateway and strip, I'm tempted...

@sonar98
Copy link
Author

sonar98 commented Nov 26, 2020

Tomorrow I will receive the gateway.

@sonar98
Copy link
Author

sonar98 commented Nov 27, 2020

Some screenshots from the LIDL Home app when using the Silvercrest gateway:

white
color
scene1
scene2
scene3
scene4

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 27, 2020

Got one, incl. gateway, see #3762. Zigbee sniffer is working overtime.

The X-Mas lightstrip consists of 200 LEDs, which seem to be individually addressable, at least from the controller. I think LEDs are chained, connecting the data in of the next LED to the data out of the previous LED, like the Neopixel or Pimoroni Blinkt! (see Homebridge RPi). When setting the strip to a single colour, the new colour "travels through" the strip, suggesting a serial protocol. Same for the occasional erroneous setting of a single LED.

I'm not sure of this detailed level of control is exposed over Zigbee, though.

The strip seems to be controlled from cluster 0xEF00, but no Manufacturer Specific bit. Any change (be it white, colour or scene) results in a 0x00 command, followed by one or more 0x01 commands. The commands have a variable payload, up to 56 bytes. Even combined, the payloads doesn't seem to be large enough to hold the RGB and brightness values per LED. Presumably, the controller uses the payload to generate the serial signal.

BTW, if you hold an X-Mas tree, a window pops up to change the speed and colours for the scene.

@Smanar
Copy link
Collaborator

Smanar commented Nov 27, 2020

@ebaauw, the protocole is already sniffed and decrypted (look at z2m project) it use classic tuya command, can use the tuya code without problem.

bool DeRestPluginPrivate::SendTuyaRequest(TaskItem &taskRef, TaskType taskType , qint8 Dp_type, qint8 Dp_identifier , QByteArray data )

My problem is include this device without adding 5/6 command in deconz core for only one device, used 1 month by year.

I think using only 1 command, that take aall params, and put the code in tuya file.

@Smanar
Copy link
Collaborator

Smanar commented Nov 27, 2020

I have not the device, so nothing is tested, just deductions.

The command to use are for exemple for effect

//command
#define MELINERA_MODE 2
#define MELINERA_COLOR 5
#define MELINERA_EFFECT 6

//Mode
#define MELINERA_MODE_EFFECT 0x02
#define MELINERA_MODE_COLOR 0x01
#define MELINERA_MODE_WHITE 0x00

//Effect
QByteArray effect = QByteArray("\x48\x52", 2); // "04" for twinkle 
QByteArray speed = QByteArray("\x49\x48", 2); // speed = 10
QByteArray color= QByteArray("\x52\x52\x52\x49\x49\x49", 6); // color RGB 44,44,44 and color RGB 11,11,11 as twinkle  use 2 color

data = effect  + speed + color

SendTuyaRequest( taskRef, taskType , DP_TYPE_ENUM, MELINERA_MODE  , MELINERA_MODE_EFFECT)
SendTuyaRequest( taskRef, taskType , DP_TYPE_STRING, MELINERA_EFFECT , data)

Or for color

//command
#define MELINERA_MODE 2
#define MELINERA_COLOR 5
#define MELINERA_EFFECT 6

//Mode
#define MELINERA_MODE_EFFECT 0x02
#define MELINERA_MODE_COLOR 0x01
#define MELINERA_MODE_WHITE 0x00

//Color
QByteArray c1 = QByteArray("\x48,\x49,\x54,\x56", 4); // color 360
QByteArray c2 = QByteArray("\x48,\x51,\x101,\x56", 4); // color 1000
QByteArray c3 = QByteArray("\x48,\x51,\x101,\x56", 4); // color 1000

data = c1 + c2 + c3

SendTuyaRequest( taskRef, taskType , DP_TYPE_ENUM, MELINERA_MODE  , MELINERA_MODE_COLOR )
SendTuyaRequest( taskRef, taskType , DP_TYPE_STRING, MELINERA_COLOR , data)

brightness

//command
#define MELINERA_MODE 2
#define MELINERA_COLOR 5
#define MELINERA_EFFECT 6
#define MELINERA_Brightness 3

//Mode
#define MELINERA_MODE_EFFECT 0x02
#define MELINERA_MODE_COLOR 0x01
#define MELINERA_MODE_WHITE 0x00

//Brightness
QByteArray data = QByteArray("\x00,\x00,\x00,\x88", 4);


SendTuyaRequest( taskRef, taskType , DP_TYPE_ENUM, MELINERA_MODE  , MELINERA_MODE_WHITE )
SendTuyaRequest( taskRef, taskType , DP_TYPE_VALUE, MELINERA_Brightness , data)

@sonar98
Copy link
Author

sonar98 commented Nov 27, 2020

if you tell me how, I can test.

@ebaauw
Copy link
Collaborator

ebaauw commented Nov 27, 2020

OK with help from @Smanar , pointing me to earlier work by @Koenkk, I think I now understand how the X-mas lightstrip works.

The device seems to be "write-only": you can set it's state, but it doesn't report its current state. The app doesn't reflect the actual state, when changing the state manually, using the buttons on the controller. As advertised, the device supports 16 effects, which, depending on the effect, can be modified for speed and up to 6 colours used. The strip can also be set to a single colour for all LEDs. While the LEDs are individually addressable by the controller, this level of control doesn't seem to be exposed over Zigbee (for sure the LIDL Home app isn't using this).

The strip uses Tuya cluster 0xEF00. The gateway sends a 0x00 command to set the lightstrip state; the lightstrip returns a 0x01 command, echoing the state. Basically, the payload of these commands follows a TVL16-like scheme. It consists of a one-byte status (always? 0x00), a one-byte sequence number, and one or more TVL16 encoded "attributes". The "type" consists of one-byte attribute ID (data point in Tuya speak), followed by a one-byte data type. The length is two-byte, big-endian. The encoding of the value obviously depends on the data type.

The lightstrip supports three modes: white, colour, and effect. It seems to keep separate states for each mode. So does the LIDL Home app, but as the lightstrip is "write-only" the states aren't synced when updating the state manually.

The lightstrip supports the following attributes:

attribute data type length description
0x01 0x01 (bool) 1 On/Off
Values: 0x00: off, 0x01: on
0x02 0x04 (enum) 1 Mode
Values: 0x00: white, 0x01: colour, 0x02: effect
0x03 0x02 (number) 4 Brightness (in 0.1%).
Value is a big-endian u32.
0x05 0x03 (string) 4+4+4 Hue (in °), sat (in 0.1%), bri (in 0.1%).
Values are ascii-encoded, big-endian hex values.
0x06 0x03 (string) 2+2+n*6 Effect (0x00 - 0x0F), speed (in %, or 0 if n/a), n Colours in RGB (0-255).
Values are ascii-encoded, big-endian hex values.

Attribute 0x03 seems applicable only in white mode; 0x05 only in colour mode; and 0x06 only in effect mode. The gateway typically sends attributes 0x01, 0x02, and 0x06 in a single 0x00 command. Note that in colour mode, 16-bit hue/sat values are used, whereas in effect mode, 8-bit RGB values are used. You cannot control brightness while in effect mode.

I haven't yet tried the strip with deCONZ, but I seriously doubt that the Color Control cluster would be usable. I don't think the lightstrip supports the CIE 1931 colour space, so the xy values would be bogus.

Supporting the lightstrip in the REST API will be challenging from a design perspecitive and ugly from an implementation perspective.

  • I don't think we currently expose mode for lights. We could use "effect": "none" to switch to colour mode, and {"effect": "name"} to switch to effect mode. I'm not sure how to switch to white mode.
  • It's probably easiest to use hue and sat in colour mode, but this will be hell for API clients, who (should) use xy. I suppose we better use xy values, and transform them to RGB hue/sat values. On the other hand, setting sat to 0 would be a natural way for switching to white mode.
  • Exposing the effects using effect with new values for the effect names seems doable. We already have colorloopspeed; best rename that to effectspeed (speed is already taken by fans, unfortunately). The effect colours are best modelled as an effectcolors array of RGB values. I suppose few API clients will go to this level of detail (I, for one, wouldn't know how to expose this to HomeKit), so accepting xy values and translating them to RGB seems to have little benefit.

@eric1905
Copy link

eric1905 commented Dec 4, 2020

I use it as a OpenHAB integration

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 4, 2020

Is there a possibility to reach this "steady" multicolour mode via the API?

Can you reach it through the LIDL app? As far as I can tell, the Steady scene only takes a single colour. The strip does not report its actual state, so our only change would be catching the LIDL app and gateway in the act of setting this mode.

The LIDL gateway does some magic when pairing the device (writing some manufacturer-specific attributes, sending some Tuya commands with a very small payload). The LED strip responds with some Tuya commands as well. However this doesn't seem to influence the working of the strip. I tried sending all Tuya commands from 0x00 to 0x1F (using the CLI plugin), to see if one of them could lure the strip into reporting its state, but no joy.

you do not happen to use ZHA in Home Assistant (depends on zigpy and zha-device-handlers) as well as deCONZ?

No, I only use HomeKit. I don't even use Phoscon.

Any chance that you would be willing to also open up the control-box and take pictures of the circuit board inside it?

The circuit board would likely contain a Zigbee chip and a microcontroller (or a single chip combining both functions). The microcontroller generates the serial signal to the LEDs, controlling each LED individually. However, it only accepts a fixed number of effects over Zigbee, so we cannot control each LED individually over Zigbee. The serial signal is write-only by nature. The microcontroller is write-only by (poor) design, maybe limited by the resources on the board. So there's no way to get the current state of the microcontroller.

@dasoho
Copy link

dasoho commented Dec 4, 2020

Can you reach this "steady" multicolour mode through the LIDL app?

Actually, I don't have a LIDL gateway, just operate it via deconz, so I can't crosscheck. Anyway, thank you very much for having this checked from you side.

@Smanar
Copy link
Collaborator

Smanar commented Dec 4, 2020

Someone can tell me if RGB color are working fine using phoscon ?
Using "sat" slider.

@Somberland
Copy link

Somberland commented Dec 5, 2020

BTW if using those Lights with HomeKit (homebridge): do I need iOS 14 for them? Get this "not supported" error

image

@grrrmml
Copy link

grrrmml commented Dec 5, 2020

First of all thanks to @ebaauw and everybody participating here to add support for the new 'xmas' device!

There ist one issue with the device identification: according to the initial data the manufacturername currently has to be "_TZE200_s8gkrkxk".

I have seen this name only once, when i included the device for the FIRST time, on my Hue bridge (luckily I did not yet delete the device data).
All other recent inclusions on the Conbee II ended up with manufacturername "Heiman", like also seen in the json data from @sonar98 (from 9 days ago). On the screenshot from @Somberland it is shown (translated? raw data?) as "Melinera".

I can confirm the modelid is "TS0601". But I have no knowledge if modelid TS0601 alone would be sufficient to identify the device (and whether using the effect routine on other devices could harm them).

After building the code locally with an additional OR condition with Heiman and TS0601 within isXmasLightStrip, i can use the effects via API. (Before that I had already updated Conbee II firmware to version 26680700, no idea if that was also a requirement for it to work.)

Maybe @ebaauw could add a fix to his code. [UPDATE: not required]

Thanks again for all the efforts - if I can aid with some tests, I'd be glad to participate, as I am used to squeeze all out of the (Hue) API - deconz is still very knew to me. And because I haven't written any C code for the last 5 years, that would not yet be a point to contribute.

@Smanar: "sat" basically works, but the colors (I just tested red) were only saturated when "bri" was between 16 and 39. Increasing "bri" from 39 to 40 then lead to a green tone with very low brightness. The color changes do really behave a bit odd.
I will probably do some more (scripted) tests using the API, to see what is really going on and what is "good" to do and what is "bad".

With best regards,
grrrmml

@Smanar
Copy link
Collaborator

Smanar commented Dec 5, 2020

"Heiman" again ?
I have removed it for VENDOR_EMBER how it can be possible again ?

Because of the tuya code where I m looking in the database ? but it need to be writted inside before ...

And we realy need to use manufacture name, because you can have different device with the same model id "TS0601"

Have you tried to :

  • delete the device.
  • check in the sql if the device is still inside somewhere (if you can)
  • check if the device is realy deleted in deconz too
  • re include it

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 5, 2020

BTW if using those Lights with HomeKit (homebridge): do I need iOS 14 for them? Get this "not supported" error

Not a clue where that comes from. Could you attach Homebridge Hue’s debug dump file?

On the screenshot from @Somberland it is shown (translated? raw data?) as "Melinera".

That’s courtesy of Homebridge Hue.

I can confirm the modelid is "TS0601". But I have no knowledge if modelid TS0601 alone would be sufficient to identify the device (and whether using the effect routine on other devices could harm them).

No, other devices use that model id as well. We need the manufacturer name (which obviously isn’t) to identify the device.

"sat" basically works, but the colors (I just tested red) were only saturated when "bri" was between 16 and 39. Increasing "bri" from 39 to 40 then lead to a green tone with very low brightness. The color changes do really behave a bit odd.

Then you’re not running my code, or the device isn’t recognised so my code doesn’t kick in. Be sure to re-pair the light strip after upgrading to v2.7.0.

@grrrmml
Copy link

grrrmml commented Dec 5, 2020

Hello again, and thank you for your quick and helpful replies.
@Smanar I haven't worked with the sql db of deconz yet (is there some documentation for it?) so I just reset the gateway.
Now I got "_TZE200_s8gkrkxk" on the first and second inclusion, and model TS0601 resolved to "Thermostat".
@ebaauw The mentioned effect with the "sat" works better now. Changing brightness is another story, but I assume this is also work in progress.

@jannnfe
Copy link

jannnfe commented Dec 5, 2020

"sat" basically works, but the colors (I just tested red) were only saturated when "bri" was between 16 and 39. Increasing "bri" from 39 to 40 then lead to a green tone with very low brightness. The color changes do really behave a bit odd.

Then you’re not running my code, or the device isn’t recognised so my code doesn’t kick in. Be sure to re-pair the light strip after upgrading to v2.7.0.

After upgrading to v2.7.0 and re-pairing the device i still have the situation described above. I deleted the fairy lights via Phoscon and added new. Do I have to delete directly via the deconz GUI?

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 5, 2020

What does the /lights resource for the Xmas light strip look like? It should look like #3716 (comment)

Deleting it from Phoscon and re-pairing should be enough, I think, but maybe you need to delete the record physically from the database.

@jannnfe
Copy link

jannnfe commented Dec 5, 2020

The /lights resource looks like this:

"26": {
        "etag": "52a4c605a656533d9be0f8670d2f6ce0",
        "hascolor": true,
        "lastannounced": null,
        "lastseen": "2020-12-05T21:51Z",
        "manufacturername": "Heiman",
        "modelid": "TS0601",
        "name": "Wohnzimmer Weihnachtsbaum",
        "state": {
            "alert": "none",
            "bri": 254,
            "colormode": "xy",
            "effect": null,
            "hue": 4128,
            "on": false,
            "reachable": false,
            "sat": 16,
            "xy": [
                0.5499,
                0.393
            ]
        },
        "swversion": null,
        "type": "Color dimmable light",
        "uniqueid": "84:2e:14:ff:fe:05:dd:2c-01"
    }

Can you give me a little instruction please what i should do next? :)

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 5, 2020

The manufacturername has been mutilated to "Heiman", causing my code not to recognise it as the Xmas lightstrip. I don't quite know what's causing this, I think I read a report that it fixes itself after restarting deCONZ. I don't know if this is the old database record being restored or a new record. Do you know what was the previous resource id? It should get a new id after deleting the resource and re-pairing the light strip.

@jannnfe
Copy link

jannnfe commented Dec 5, 2020

I think I remember that the device was called Color dimmable light 25 at the beginning and after deleting and adding it was also called Color dimmable light 25. Maybe I have to try again?

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 5, 2020

I'm sorry your guess is as good as mine. Your list above shows id 26 instead of 25, suggesting its a newly created resource, rather than a restored one.

@jannnfe
Copy link

jannnfe commented Dec 5, 2020

I've just tried again using the REST API. The ID changes but is still recognized incorrectly. Shouldn't I have the right foundation with these specifications?
Bildschirmfoto 2020-12-05 um 23 31 42

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 5, 2020

That's the right version, afaik.

@SwoopX
Copy link
Collaborator

SwoopX commented Dec 5, 2020

Try reading the manufacturer name from basic cluster in deconz GUI. That should update the name in the DB as well as in Phoscon.

@Somberland
Copy link

Somberland commented Dec 5, 2020

The Thermostate-thing is also something that occurred (or better is still present) in phoscon. After adding the device to an group I can control it via phoscon. Maybe that's also the reason why homebridge is kinda Buggy for me. Will dump homebridge tomorrow.

BTW: first updated to 2.07. before added those lights the first time.

{
    "etag": "87a89542bf9b9d0aa8134919056844f8",
    "hascolor": true,
    "lastannounced": null,
    "lastseen": "2020-12-05T22:57Z",
    "manufacturername": "_TZE200_s8gkrkxk",
    "modelid": "TS0601",
    "name": "xmas light",
    "state": {
      "bri": 25,
      "colormode": "hs",
      "effect": "none",
      "hue": 53691,
      "on": false,
      "reachable": true,
      "sat": 141
    },
    "swversion": null,
    "type": "Color dimmable light",
    "uniqueid": "58:8e:81:ff:fe:db:7b:be-01"
  }

image

image

@jannnfe
Copy link

jannnfe commented Dec 5, 2020

Try reading the manufacturer name from basic cluster in deconz GUI. That should update the name in the DB as well as in Phoscon.

That worked for me! Thanks everybody for your help :)

@SwoopX
Copy link
Collaborator

SwoopX commented Dec 5, 2020

@Somberland The model identifier is also exposed by some thermostats, so that's the reason why.

#3304

@Smanar
Copy link
Collaborator

Smanar commented Dec 6, 2020

BTW I m interested by the log when including the device, if someone still have "heiman" as manufacture name.

@jd-network
Copy link

Für die einzelnen Effekte können auch mehrere Farben definiert bzw. übermittelt werden:
{
"effect": {
"effect": "snake",
"speed": 100,
"colors": [
{
"r": 255,
"g": 0,
"b": 0
},
{
"r": 0,
"g": 255,
"b": 0
},
{
"r": 0,
"g": 0,
"b": 255
}
]
}
}

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/HG06467.md

@OptiMael
Copy link

OptiMael commented Dec 7, 2020

BTW I m interested by the log when including the device, if someone still have "heiman" as manufacture name.

image
image

@Mimiix
Copy link
Collaborator

Mimiix commented Dec 7, 2020

Hi there,

As this topic is slowly turning into a generic help topic, i am closing this off. Phoscon needs to add support by itself, please open a issue in their repository.

@ebaauw told me he wanted to have another PR in regards to this issue. He will keep this issue updated with the latest developments.

If anyone has a issue with this device, feel free to open a user question issue or stop by in our discord server!

Thanks for anyone involved 👍 !

@Mimiix Mimiix closed this as completed Dec 7, 2020
@dresden-elektronik dresden-elektronik locked as resolved and limited conversation to collaborators Dec 7, 2020
@ebaauw
Copy link
Collaborator

ebaauw commented Dec 7, 2020

The PR is already there, #3716 (comment). I just want it to be merged in the next (beta) release.

@ebaauw
Copy link
Collaborator

ebaauw commented Dec 17, 2020

Latest PR doesn't work out as I'd hoped. Setting the brightness when in colour mode might change the colour, see ebaauw/homebridge-hue#860. Need to revert supporting bri_inc and trying to keep Current Level attribute in the Level Control cluster reflecting the actual brightness.

@ebaauw ebaauw linked a pull request Dec 17, 2020 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.