Unable to connect to Tapo L535 Matter Smart Bulb

[ScottGibb]

First off thank you so much for building this node. I've been looking for this kind of thing for a while.

I was wondering if I was doing something wrong. I'm trying to set up this light bulb Tapo L535B.

Within the Alexa app I've managed to get the code to control it via another matter owner. However I cant get the device to show up in the command node.

In the device management node I have this:

and the logs tell me this:

2025-01-09 18:55:26.090 DEBUG  UdpChannelNode       Socket created and bound remoteAddress: undefined:undefined localAddress: :::58650
2025-01-09 18:55:26.093 DEBUG  UdpChannelNode       Socket created and bound remoteAddress: undefined:58650 localAddress: 0.0.0.0:58650
2025-01-09 18:55:26.094 WARN   Commission~ontroller BLE is not supported on this platform
2025-01-09 18:55:26.106 DEBUG  CertificateAuthority Loaded stored credentials with ID 0
2025-01-09 18:55:26.107 INFO   MatterController     Creating new fabric
2025-01-09 18:55:26.122 DEBUG  Fabric               FabricBuilder setOperationalCert: nodeId=10088972493286793941, fabricId=1, caseAuthenticatedTags=undefined
2025-01-09 18:55:26.134 DEBUG  DeviceAdvertiser     Announcing fabric: 1
2025-01-09 18:55:26.137 DEBUG  MdnsBroadcaster      Announcement Generator: Fabric id: 0c60d2b2efdfdf15/17605793492469796756 qname: 0C60D2B2EFDFDF15-F45457E6E38BCF94._matter._tcp.local port: 46417 interface: eth0
2025-01-09 18:55:26.139 DEBUG  MdnsBroadcaster      Announcement Generator: Fabric id: 0c60d2b2efdfdf15/7624222040505092205 qname: 0C60D2B2EFDFDF15-69CEAD8D0D02886D._matter._tcp.local port: 51715 interface: eth0
2025-01-09 18:55:26.141 DEBUG  MdnsBroadcaster      Announcement Generator: Fabric id: 0c60d2b2efdfdf15/12117430540597458487 qname: 0C60D2B2EFDFDF15-A829C2E032C7F637._matter._tcp.local port: 55677 interface: eth0
2025-01-09 18:55:26.144 DEBUG  MdnsBroadcaster      Announcement Generator: Fabric id: 0c60d2b2efdfdf15/17520907862216491036 qname: 0C60D2B2EFDFDF15-F326C4DEF5C3401C._matter._tcp.local port: 44845 interface: eth0
2025-01-09 18:55:26.146 DEBUG  MdnsBroadcaster      Announcement Generator: Fabric id: 0c60d2b2efdfdf15/10088972493286793941 qname: 0C60D2B2EFDFDF15-8C033B076B0BE2D5._matter._tcp.local port: 58650 interface: eth0
2025-01-09 18:55:26.152 DEBUG  MdnsScanner          Adding operational device 0C60D2B2EFDFDF15-8C033B076B0BE2D5._matter._tcp.local in cache (interface eth0, ttl=120) with TXT data: SII: 500 SAI: 300 SAT: 4000 T: 0 DT: undefined PH: undefined ICD: 0 VP: undefined DN: undefined RI: undefined PI: undefined

Is there something i'm doing wrong? First time using Matter so any help would be appreciated :)

[sammachin]

Have you actually triggered that device management node to commission the bulb?
You should get an output from that with a device id (long random number)
You can also check its commissioned using the get devices function of the management node.

once that’s complete it should then show up in the device list on the command node

[ScottGibb]

Ooohhhhh. I did not realise I had to use the inject node to trigger the node setup.... That makes so much sense. Im glad to say after I did that it worked perfectly and seamlessly. Thank you so much!