Will this support the Motion Sesors they have just brought out? the Air model?
I am still waiting for mine to arrive so I will know more later.
Thanks Adrian. Waiting on mine also. So if you are going to be working on it, I will wait until something is in place. If you need help testing let me know
Hi Adrian, Iām having trouble getting eMotion Pro sensors to connect to the appās built-in MQTT broker, and Iād appreciate your help. Hereās a detailed diagnostic: Setup - Homey Pro (Early 2023), Homey v13.4.0 - LinknLink app v1.0.8 - Built-in MQTT broker enabled: mqtt://localhost, port 10883, websocket 18888, user ālinknlinkuserā, default password. What works - An eMotion Ultra (id e04b410241bb) connects perfectly. In the appās Log tab I can see its MQTT messages arriving every ~10 seconds, and it shows up correctly in the Detected tab with all its entities. Its presence automations work fine. The problem - I have TWO eMotion Pro units (firmware V61066). I configured them via the appās āā¦ā ā MQTT Connection screen with the exact same MQTT settings as the Ultra, pointing to the Homey IP (10.0.0.58), port 10883, same username/password. - Neither Pro ever reaches the broker: they do NOT appear in the Detected tab, they produce NO entries in the Log tab (not even a failed/rejected connection), and pairing always ends with āNo new device foundā (and sometimes a āTimeout after 10000msā error during the scan). - The mobile app shows āMQTT connection status: not connectedā for the Pros ā but it shows the same for the Ultra, which clearly works, so that indicator seems unreliable. - I already tried: moving a Pro right next to the main mesh router node, matching the Proās MQTT settings to the working Ultra field by field, and a factory reset + fresh setup. Same result. Network - Mesh WiFi (Netgear Orbi). All devices on the same subnet as Homey (Homey 10.0.0.58, one Pro at 10.0.0.9). AP isolation is off (the Ultra reaches Homey over the same mesh). Questions - Is there any additional or different step required to enable local MQTT specifically on the eMotion Pro (firmware V61066) vs the eMotion Ultra? - Is there a known issue with eMotion Pro firmware V61066 and the appās broker discovery? - Anything else I can check to help pin this down? Diagnostic report code: 606085af-f7fc-4734-a63f-04ad8ed6bce5 Thanks a lot for your work on this app.
Hi Adrian
Iām loving the app and got my emotion ultra working are you planning support for unassigned ir devices or is it supported and I canāt get it to work
Iāve set up a ir to control my fire but I canāt find it in homey
I have published a new test version 1.0.10.
Can you install that and then after a minute or so, open the app settings page and select the Detected tab. make sure the Show only available components is switch off and then tap on the Get devices:
Once the list has populated, tap on Send Log and then let me know when you have done that. Hopefully that should provide enough information for me to add support for your fire.
Hi Adrian
Iāve sent the log.
At the moment ive only got two buttons on it one to turn it on/off and one to change the colour.
Thanks
Jason
I have the log but it doesnāt show any new devices. I think I have tracked down the issue but doing some more tests.
How did you add the device to LinknLink, did you select the Home Assistant option or the app option?
Was it a custom device?
Edit: It appears the Universal Panel does not post any information to the MQTT broker, so it canāt be detected by Homey. If that is the one you have used, could you try changing it to a Switch?
I added it by going to the devices tab on the linknlink app then add new device then selecting IR device i then selcted the eMotion Ultra.
on the select device page i used the Universal pannel, the select add target i went for add for HA
selected living room on the My rooms
named the pannel fire and got it to learn the two buttons.
Ok. From my experiments, the Universal panel wonāt work with Homey as nothing is published in the broker. Iām not sure if thatās a bug in LinknLink or by design.
I added a Switch and that is published, so Homey can find that. I think you can add more buttons to that, so maybe try that. I canāt remember if the last test version I published had support for the Switch as I have been making changes to try and get the Universal panel working before I realised LinknLink wasnāt publishing anything for it.
ive added a switch on the linknlink ap, i take it switch should be in your linknlink homey add device page at the moment i just have the ac remore, emotion, emotion pro emotion ultra and tv.
I must have added the Switch after the last test version was uploaded. I will publish a new one this evening.
