[App][Pro]LinknLink eMotion

[NeosS]

Got it! In the end, connecting to the MQTT broker like you mentioned in your last message worked! Thanks!

[B3rt]

I have similar problem.

I run broker on my NAS (so external), I use it with Homeassistat and zigbee2mqtt

HA finds the eMotion ultra via MQTT but Homey find no devices.

undefined

• 2026-02-28T15:37:16.599Z
  setupMQTTClient connect: 192.168.1.2:1883

• 2026-02-28T15:37:16.753Z
  LinknLink app has been initialized

• 2026-02-28T15:37:16.768Z
  eMotionProDriver has been initialized

• 2026-02-28T15:37:16.773Z
  eMotionUltraDriver has been initialized

I believe this is the lnknlink device is MQTT explorer, but not detected by app

[Adrian_Rockall]

Try using the setting like this

But obviously change the IP to match your NAS.

I am also running a broker on my NAS and it’s working fine.

[B3rt]

After changing the port and save the app crashed, but after it restarted it started to work.

Maybe you can clarify what the 9003 port/field exactly is or do, maybe then it is clear to users what to fill in here?

Personaly I have no clue why it is 9003..

9003 is not a port my broker uses, that is 1883, so why does 9003 work?

Is it neccarry to add mqtt:// in front of the IP?

[Adrian_Rockall]

The 9003 port is for the web socket connection. That provides an optional encrypted connection, but it was probably just that it was the same as the MQTT port that caused an issue. I will add a label to that field as it was an oversight that it is missing.

I need to check the code to see if the mqtt:// is required as I might have added it if it’s missing, and if that’s not the case then I will add it.

[Luis_Chaves]

Hello,

I am trying to integrate two LinknLink eMotion sensors with Homey Pro using the LinknLink app and the built-in MQTT broker, but Homey cannot discover the devices.

Configuration

• Homey IP: 192.168.1.177

• MQTT Broker Port: 10883

• Username: Userlfc

• Password: Passlfc

• “Use Homey built-in MQTT broker”: Enabled

Sensor status

Both sensors were converted to HA Panel mode in the LinknLink app.

The MQTT configuration on the sensors is:

• Host: 192.168.1.177

• Port: 10883

• Username: Userlfc

• Password: Passlfc

The sensor shows:

MQTT connection status: Connected

Problem

When trying to add the device in Homey:

Devices → Add Device → LinknLink → eMotion Pro

Homey reports:

"No new device found"

Additional error in the Homey log

server error: listen EADDRINUSE: address already in use :::10883
Error: listen EADDRINUSE: address already in use :::10883

Diagnostic report

5bbbb5b9-9c62-46b2-bcf7-7c66558da90d

Question

If the sensors are already connected to the MQTT broker, should Homey automatically discover them via MQTT discovery, or is there an additional step required?

Thank you for any guidance.

[Adrian_Rockall]

The error seems strange, so could you try restarting the app to see if it happens again?

You have specified the Homey IP address in the Homey app configuration. Is that just to show me the Homey IP or have you changed it from localhost?

What type of eMotion sensor is it?

The app should discover the devices from the MQTT broker.

[Luis_Chaves]

Hi Adrian, thanks for the help!

1. It is an eMotion Ultra sensor.

2. The IP 192.168.1.177 is the static IP of my Homey Pro. I set it manually in the settings, but I can change it back to localhost if needed.

3. I have already tried restarting the app several times. The log shows eMotionUltraDriver initialized at 08:34:10, but the ‘Detected’ list remains empty even when passing in front of the sensor.

4. My MQTT Explorer does see the messages from the sensor on port 1883, but the app doesn’t seem to ‘discover’ them.

[Adrian_Rockall]

Have you got mqtt:// in front of the IP address?

[Luis_Chaves]

Hi Adrian, it actually works with just the IP (no mqtt:// needed). The real issue is that the Ultra sensor worked fine for 3-4 days and then just froze.

When I tried to reinstall it, Homey never detected it again, even though I can see both the Ultra and the Pro working perfectly in the native Linknlink app. It seems like once they drop from the MQTT broker in Homey, they become ‘invisible’ to the app’s discovery process

[Adrian_Rockall]

The app uses the information in the MQTT broker to discover the devices, so if they are not published data then they won’t be discoverable.

[Luis_Chaves]

Hi Adrian,

Thanks a lot for taking the time to respond. I really appreciate your help and all the work you do for the Homey community.

To be honest, I’ve been battling with this LinknLink setup for four days now, and they definitely won this round!. As a new Homey user, I was looking for that ‘plug and play’ experience, and I think my lack of experience with MQTT is making this harder than it should be.

For now, I’m going to try some other brands to keep my setup simple while I keep learning how Homey works. I’m sure that if the problem isn’t on my end, you’ll eventually have it sorted out for everyone else.

Thanks again for the support, and I’ll probably give LinknLink another shot in the future once I have more experience.

Best regards!