I have published a new test version with support for a TV remote and an AC remote. They seems to work for me, so hopefully they should be universal.
There seems to be a bug in the LinknLink system for the AC remote that prevents the temperature being set if the Auto Mode is active. It is an issue in the LinknLink app as well, so not just an MQTT issue. I will report that to them to see what they say.
Hi Adrian- thanks for all your work here!
Do you expect to add support for the eMotion Air when it ships? A $13 mmWave sensor thatās also a button is really appealing.
I have pledged on kickstarter and should receive some when they launch.
I hope to add support for them, but they use a different technology, Zigbee, that I havenāt worked with before, so it will be a bit of a challenge 
.
Iāve tried the new version and itās not working for me. I have connected the TV and the AC in the LinknLink app and it works normally. But in the Homey app, when i try to add the TV or the AC it doesnāt find any device. I donāt know if it has to do with the same problem as before, the Ultra 2 version.
Thank you for all the work you do
Could you open the app settings and select the Detected tab, then tap on Get Devices followed by Send Log.
I get this in the log:
[
ā4101a675beac00009ff59624266eā,
{
ādeviceIdā: ā4101a675beac00009ff59624266eā,
ānameā: āTVā,
āmodelā: āTV from eMotion Ultraā,
āmanufacturerā: āLinknLinkā,
āentitiesā: [
and the app uses the model field to identify the type. maybe yours is coming back with something different.
For the TV I match either of theses [āTV from eMotion Ultraā, āTV from eMotion Ultra2ā].
Iāve sent you the log, Iām not getting any device
Know, Iāve connected them via HA, I can see the TV device but not the AC device. Even thought I canāt connect the TV. Iāve send you the log
I donāt know if this could help. The Homey app recognise the TV as an AC remote so I can add it to Homey but it doesnāt work for obvious reasons. (Homey error: No MQTT climate entity found for AC device)
I have been working on using a different method to identify devices as the model name is going to be very unreliable. Iām not how HA copes, but the interface is a bit wishy wishy.
Thank you Adrian, I appreciate it a lot
I have published a new test version that now looks for entities rather than the model type.
Remote TV is now working perfectly. Homey app canāt see the AC device
Hello Adrian. Thank you for your work on this. Iām a novice and been trying to get this to work over the last few days.
I wound up using the homey built-in mqtt broker.
Used localhost and the broker port 10833
On my phone it says the MQTT status is connected.. but when I go to the app to add the emotion ultra, its still not being discovered. Any ideas?
Can you open the app setting page and select the Detected Tab, then tap on Get Devices followed by Send Log once the list has populated. Let me know when you have sent it and I will check. While you are there could you select the Log tab and check for any errors.
You could try installing MQTT Explorer https://mqtt-explorer.com/ and connect that to Homey to make sure the device is publishing data to the broker.
Hey Adrian,
Iām having an issue that might be out of this appās scope, but Iām trying to get the Original eMotion sensors to work in Homey. It seems to be an issue with a lot of platforms (HA, etc). These are not Pro or Ultra models. I got them to work in HA with a normal MQTT Broker, but canāt get them to show up in Homey with the MQTT Server App. Any insight?
OK, it appears there is a small bug in the Settings when you select to use homey as the MQTT broker. The app defaults to localhost, but that needs to be mqtt://localhost.
The broker is started OK with either setting but the client doesnāt find it without the mqtt:// at the front.
So, set it to mqtt://localhost, save the settings and then restart the app. Wait for a minute for everything to start up and register and then you should be able to add the device.
