10 hours ago
The manufacturer confirmed the correct pairing method: Press the button 5 times slowly. They acknowledged this is not in the documentation.
Another question:
When i try to configure the device, it show this:
![[Image: Cb3sV4w.png]](https://i.imgur.com/Cb3sV4w.png)
But when I go to device information it shows this:
Is this because there is not made a profile for this specific product ?
The product have 4 buttons, what I want is to call a different scene from each button, can I do anything to achieve this?
Another question:
When i try to configure the device, it show this:
![[Image: Cb3sV4w.png]](https://i.imgur.com/Cb3sV4w.png)
But when I go to device information it shows this:
Code:
Manufacturer: YOKIS
Model: TLC4-UP
Firmware version: 2.8.3
Device type: End device
Power source: Battery
Receive when idle: No
Endpoint 1
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- LightLink (4096)
- 64521
- 64513
- 64514
Output clusters
- Identify (3)
- OnOff (6)
- LevelCtrl (8)
- ClosuresWindowCovering (258)
- LightLink (4096)
- 64514
- 64518
- 64519
- 64520
- 64522
Endpoint 2
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- LightLink (4096)
- 64521
- 64513
- 64514
Output clusters
- Identify (3)
- OnOff (6)
- LevelCtrl (8)
- ClosuresWindowCovering (258)
- LightLink (4096)
- 64514
- 64518
- 64519
- 64520
- 64522
Endpoint 3
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- LightLink (4096)
- 64521
- 64513
- 64514
Output clusters
- Identify (3)
- OnOff (6)
- LevelCtrl (8)
- ClosuresWindowCovering (258)
- LightLink (4096)
- 64514
- 64518
- 64519
- 64520
- 64522
Endpoint 4
Profile: 260
Input clusters
- Basic (0)
- Identify (3)
- LightLink (4096)
- 64521
- 64513
- 64514
Output clusters
- Identify (3)
- OnOff (6)
- LevelCtrl (8)
- ClosuresWindowCovering (258)
- LightLink (4096)
- 64514
- 64518
- 64519
- 64520
- 64522Is this because there is not made a profile for this specific product ?
The product have 4 buttons, what I want is to call a different scene from each button, can I do anything to achieve this?
