I have reinstalled app with 3.6.1 version and everything works as should.
1 Like
with my hp23 the MQTT hub crashes after a few seconds, minutes… I have no clue why - the app consumes lots of memory and crashes after a while and restarts…
Could you support me, please? version 3.6.1
Hi after automatically upgrading honey 2019 to 8.1.4 I noticed a lack of data sent over nqtt . After several reboots of the hub. The statuses of sensors and devices started to appear but I can’t control from outside with Home Assistant . . I have tried various ways but no fix so far. Please give me a hint
Not related to FW v8.1.4, but it might help:
Sorry for the late reply but started to use a Homey just a few weeks ago. After days of looking through the code I found a quick and dirty solution for your problem. In the Topics setting of the device change the text “displayName” to “title” like this:
{
"measure_temperature": {
"capability": "measure_temperature",
"stateTopic": "ECODAN/tele/0x0B",
"commandTopic": "",
"valueTemplate": "Outside_Temperature",
"outputTemplate": "",
"title": "Outside"
}
instead of (faulty):
{
"measure_temperature": {
"capability": "measure_temperature",
"stateTopic": "ECODAN/tele/0x0B",
"commandTopic": "",
"valueTemplate": "Outside_Temperature",
"outputTemplate": "",
"displayName": "Outside"
}
Hope this helps
1 Like
You can use an outputTemplate with JSON-T notation like:
{ “SetRoomTemperature” : {{value}} }
from example:
Tested by @robertklep:
Hello @HarriedeGroot
would it be possible to add additional states to exported capabilities?
Example:
I export meter_water and meter_gas and want to use it in HA for energy dashboard.
But these entities can only be added if they have attributes like:
device_class: gas
state_class: total_increasing
The Hub only seems to export friendly_name and unit, but nothing capability based.
Do you think this could be added to device._publishMessage()? I could add some cases if you want and create PR. Or is there a better way? An alternative could be to add attributes to for devices in app settings, but this would need more adjustments.
Edit:
I just added a template sensor to HA which inlo takes the value from the Mqtt sensor and added device_class and state_class.
That works great for me! Now finally the displayname shows the correct name and also at the insights-page.
Thanks for your reply!
Hi,
I successfully connected the ovos/mycroft voice assistance with mqtt hub. This mqtt hub has endless possibilities compared to a straight forward mqtt solution.
I use the skill-homey voor ovos/mycroft and in this skill I have the option to select a location/room. This enables me to switch a specific light in a room, e.g “switch light in office”. Unfortunately, i do not see the homey locations being send over mqtt by hub. I expected this to happen, because I see all my devices including room in the “devices” menu of the Hub.
Can I receive room information over mqtt?
thanks Menne
hello everyone, I am trying to get all my devices from FHEM (on my RPI) to Homey. I am a bit confused with the MQTThub. I think it’s a tool to export the devices from the Homey to for example home assistant. I need the other way around.
You can also use MQTT devices to create virtual devices with capabilities bound to MQTT topics.
were can I find the information to create virtual devices and bound those MQTT topics?
I can add this to my homey, but don’t know how to proceed.
You can’t see the buttons at the bottom of the wizard. Try clicking in the right lower corner to proceed.
1 Like
Thanks, if everything would be that simple 
I found the button and fixed it!
I can control my lights now! I am really happy now.
1 Like
I was wondering if it’s possible to add capabilities that are not in the dropdown when adding a custom MQTT device?
I’m tinkering with a mmWave presence detector connected to an ESP32 microcontroller and I programmed MQTT publishing to Homey on it using the Arduino IDE. This app seems to be the ideal way to add it to Homey and I basically have it working now, just not with the correct capabilities:
The sensor has a “distance” property and an “energy” property (basically the signal strength in percentage, so 0-100). As you can see, I added the distance topic as rain capability (measure_rain) because that seems to be the only one in there measuring a distance/length and I added the energy/signal strength topic as humidity (measure_humidity).
It works, but isn’t there a way of adding a more appropriate capability for those?
Apart from this, thanks for the app! I also use it to let Homey communicate to HA and that part works flawlessly.
With the Home Assistant Community app, you can add HA devices as you like, add and remove entities from a device as well
Funny, I hadn’t even thought of adding it to HA directly instead of adding it to Homey first (and then read the values in HA).
Probably because I use Homey for all the logic for flows and use HA mainly for my dashboard, so Home Assistant has almost no device added directly added to it but communicates with Homey for that (using this MQTT Hub app).
Wouldn’t there be any noticable lag if you add a sensor to HA first and then send its values to Homey for use in flows instead of adding it to Homey directly?
No, it works in real time.
1 Like
Well, you’ll be surprised. As example, most of my zigbee devices respond around 1s quicker than using native Homey (2019) zigbee, but when you look at the steps below it you’d expect the opposite:
Zigbee motion sensor event > zigbee2mqtt add-on > wifi > Homey flow gets triggered and sends a command to turn on a zigbee light > wifi > zigbee2mqtt add-on > zigbee light turns on
