API can't communicate with device (smart light bulb) but app can (both in the same local network)

[coupeborgward]

I added the new smart light bulb and the api can communicate with it without any issue. After a while I noticed that the light bulb is not an attached device on my router anymore but the broadlink app can still communicate/control it but the API can't since the IP address is not valid anymore. Has anyone seen this behavior before.

[coupeborgward]

I found the issue which unfortunately is a big one for this API. Broadlink are using smart hub technology which means one of the device in the network acts as a hub controlling the rest of the devices. The side affect of this is that not all devices will have an IP address assigned and cannot be communicate to by this API. Even assigning a static IP address etc will not help since the broadlink software itself is the controlling unit and not the router.

[Lull3n]

Yeah, i just came across the same issue. Clever little fuckers... I think there ought to be a way to work around this, given that comms are conducted locally when the device is unlocked. Unfortunately this is way above my level, and i think the maintainers are understandibly pretty busy.

[MichielioZ]

I've had the same problem for a while now. I live in a small apartment and besides my RM4 Pro, I've got a smart bulb (LB27R1) which acts as a hub for my 2 smart plugs (SP4L-EU). I'm unable to use my 2 plugs in an automation like this and have reverted to some old RF plugs (having no feedback about their state is troublesome though).
Saw there is already a pull request here by @felipediel
Hope anybody reading this can help testing as I'm no good at decoding the message(s) :-(

[coupeborgward]

I change over to meross smart light bulbs which work flawless. Their API communicated to the cloud which then establishes the comms to the light bulb itself. I have this setup running since 4 months now without any issues.