Hi
Worked perfectly. But it seems my homey was some kind of stuck.
Didn’t worked on first try, but perfectly after a Reboot of my homey
Thanks for your help
1 Like
Is there a problem with the app?
I am running latest version 4.3.11
When I go into the app settings there is no configaration menu anymore and also whenI try to restart the app it error that the app is not installed anymore…
All my MQTT devices in HA are not found anymore.
What is causing this and how to solve it?
Sound like your app is stopped, disabled or crashed. Can you see any details in app details screen?
An app restart should solve for now…or your Homey is running out of memory and stops some apps.
An app restart was not possible, when you tried this then you got an error that the app was not installed…
The default app screen looked very normal, nothing to see/report if it was crashed, running or stopped etc.
I tried a homey reboot this fixed the problem…
So what the cause was is still a mistery to me.
New test version 4.3.12
- Updates Node module athom-api.
@RonnyW , Just updated to HomeAssistant 2025.3.1. It broke all my “meter_power” from Homey. In the release note for HA i do not fin anything that should affect it, do you see something? 2025.3: View those headers! - Home Assistant
MQTT Explorer:
HA:
Edit: after a really close look, could this be it?
Here is the log-error:
I have only snipped one, but everyone reads the same.
The device class in the auto discover template, should be “energy”, not “power”?
New test version 4.3.13:
- Fixed device class for meter_power for HA discovery.
@Marius_Stensrod Thanks for your hint and solution 
The class for meter_power is now changed to “energy”. I hope that’s working again with the new HA version.
2 Likes
Thanks, that fixed it , all my entities is back with the rendered template:slight_smile:
1 Like
Has anyone used the “Then” card “Set value of capability” for a MQTT Device with any success?
Trying to set a value but all I’m getting is, “Invalid Token: homey:device:67152e36-…”
Edit: Seems like when picking an available value from the device, “Power” in this case. It doesn’t work. But if I manually type “measure_power” in this case, it works!
[Power] is the name of a numeric tag/variable, which can hold any numeric value but not a string like measure_power.
Always enter capability names yourself
When you want the value of the tag [Power] to be entered as measure_power value, you’d add the [Power] tag to the (value) field, where you now entered the number 10.
Thanks for the response @Peter_Kawa
Using the information you provided I was also able to set meter_power.imported and meter_power.exported, along with measure_power and meter_power. The MQTT Device now works and looks like any smart meter in the energy tab with all the correct values.
The device setup looks like this.
{
“measure_power”: {
“capability”: “measure_power”,
“stateTopic”: “”,
“setTopic”: “”,
“valueTemplate”: “”,
“outputTemplate”: “”,
“displayName”: “Power”
},
“meter_power”: {
“capability”: “meter_power”,
“stateTopic”: “”,
“setTopic”: “”,
“valueTemplate”: “”,
“outputTemplate”: “”,
“displayName”: “Energy”
},
“meter_power.imported”: {
“capability”: “meter_power.imported”,
“stateTopic”: “”,
“setTopic”: “”,
“valueTemplate”: “”,
“outputTemplate”: “”,
“displayName”: “Imported”
},
“meter_power.exported”: {
“capability”: “meter_power.exported”,
“stateTopic”: “”,
“setTopic”: “”,
“valueTemplate”: “”,
“outputTemplate”: “”,
“displayName”: “Exported”
}
}
For anyone out there using Swedish Ferroamp Hub, you can get all the required values from the Ferroamp Cloud API and Ferroamp MQTT, that you need to update the MQTT Hub Device to act as a smart meter.
1 Like
New test version 4.3.14:
- Added climate min/max/step settings and unit for HA discovery.
The app is using the capability options from the device.
I’m not sure if these values are already localized (to °F) or still in internal format (°C).
And I tried to add the unit (temperature_unit), but my HA is ignoring it.
Based on: MQTT HVAC - Home Assistant
I can’t find the topic where this issue was posted. So please feel free to post if you are using °F and thermostats are still in °C in HA.
Until now, I have imported the MQTT data from my Hichi IR electricity meter sensor (Tasmota) to Homey via Home Assistant (HA → Home Assistant Community App).
I am currently in the process of changing the data import via an MQTT Hub device, which I have managed to do in general.
What I’m missing is a flow card especially for the imported and exported energy, like I had with the HA Community App:
From the MQTT device there are just following similar flow cards available:
– Die Stromversorgung wurde geändert (“The power supply has been changed”)
– Value changed (with no reference to any tags)
The MQTT Hub app also provides the following similar flow card:
– An MQTT device changed (but just with text tags, even for values):
I tried already different kind of flows for reproducing the HA Community flow, but with no success.
Am I missing something?
BTW, to ensure that the recordings for the import and export energy in the PbtH devices are not interrupted, I’m currently using a flow card from the Device Capabilities app:
Edit
@RonnyW, is it possible to add a similar flow card like the one in your HAC app?
I am having an issues which I assume is related to MQTT Hub. I posted all the details over here: [TUTORIAL][PRO] How to integrate Home Assistant with Homey Pro and v.v - #83 by chixxi1
Any hints would be very welcome, I really don’t know what to try next.
I will take a look at it, but it will take 3 weeks…
New test version 4.4.0:
- HomeyEnergy: Added device settings to define charged/discharged capabilities for home battery.
Thanks to martijnpieters for providing the PR
Please note:
This version needs Homey FW >= 12.4.5
2 Likes
Thanks a lot for your offer to help @RonnyW, and even more for the plugin itself!
No more help needed, got that figured out yesterday. My problem was cause by my homey devices not having unique names. Details over here: [TUTORIAL][PRO] How to integrate Home Assistant with Homey Pro and v.v - #91 by chixxi1
1 Like
Thanks for your feedback. Then it seems to depend on the HA autodiscovery where the device name is used to add a HA entity 
Good to know.
hi there,
can someone please help me?
i created a device with a picker to set charge modes.
but that gives me the next error.
and im using the following:
“thermostat_mode”: {
“capability”: “enum”,
“stateTopic”: “SmartEVSE-45242/Mode”,
“setTopic”: “SmartEVSE-45242/SetMode”,
“valueTemplate”: “”,
“outputTemplate”: “”,
“displayName”: “Mode”,
“values”:[ { “id”: “mode1”, “title”: “Off” }, { “id”: “mode2”, “title”: “Pause” }, { “id”: “mode3”, “title”: “Normal” }, { “id”: “mode4”, “title”: “Solar” }, { “id”: “mode5”, “title”: “Smart” } ]
cant find what im doing wrong.
greetings
