Added setting to choose a capability naming variant (old: device name + capability name; new: capability name) to get compatible with HomeAssistant discovery since version 2023.8
Added restart flow action and restart button in app settings view. This restarts the whole Hub including device registry, HA discovery and device/state broadcast. You can now use this flow to update HA discovery after Homey restart. An app restart is not needed.
Changed settings view: Instead of saving settings and starting a broadcast for every change (checkboxes, input fields), there is a new “Save settings” button now to save settings and restart the Hub (to broadcast all states incl. HA discovery and device registry). Some settings needed an app restart before to take effect which should not happen now with a complete sync after saving settings.
I’ve tried all kinds of settings and made many comparisons, but devices still appear with double device names in HA, regardless of having selected “Capability name” to Capability name or to Device name - Capability name
It crossed my mind, but I’ve no clue how different ‘homie’ is from my custom settings.
All I know, I only use these custom settings because with the default ‘homie’ setting, Homey devices were unresponsive when operated using HA.
Today I changed the custom settings to ‘homie convention’,
Then I disabed and re-enabled some devices, and enabled some never enabled devices in MQTT Hub, but the device names still appear twice in HA
Fixes a bug on app restart (settings/flow) where a MQTT topic “undefined” is created.
If you have such a topic, you can remove it with MqttExplorer 4.x. With version 4.x you can remove more than 50 topics at once (the limit of MqttExporer 3.x).
This issue should only appear if you have restarted the Hub from settings/flow or saved settings (wich also restarts).
Is there anyway to update the old version to the community version?
If I delete the old one and install the new one I guess that I loose all devices in HA which I paired via the old MQTT hub, so a lot of dead devices in HA is this correct?
A simple update is not possible. The app has a new ID and you have to install it again. Please deactivate the old app before installing The new one.
The HA enties won’t chang. The entity name is built using the Homey device title.
You only have to ‘screenshot’ app settings to set then again.
Only devices you can loose are Mqtt devices created for this app. But for them you also can save device settings (JSON).
Hi, awesome App, thanks for that!
I’ve created a mqtt device. Is there a way to change the unit for energy?
In addition to kWh, I also need Wh for energy.
There’s not too much documented about the virtual device feature of MQTT Hub («Advanced» field under settings). Though it’s very easy to use I still have 4 questions:
Are there really not any other «capabilities» than the «speaker_» media fields for text? The «musical note» tab selector and non-existant album art feels awkward and unnecessary for other kinds of strings. I know I could rather use the AVD/Device Capabilities app for this but I really like the simplicity of a virtual device that directly subscribes and publishes to my existing MQTT broker.
Is there any way to change the list items of an «enumerated» list capability like how the Homey API (and AVD) allows when choosing to add such a capability?
How can I activate or toggle one of several stateful button capabilities on the same device from a flow? The generic flow card for giving any capability a new value either doesn’t seem to reach eg. «button.2» etc., or «true» and «1» don’t work as values.
Also, when manually activating one of several such similar stateful buttons in the UI of one device I get an error about «missing capability listener». Probably because I use a dot separator in the IDs of the buttons (as per Homey SDK) ? Is this a bug?
EDIT: No. 4 seems to have got fixed by restarting the app, and/or possibly by using numerical labels instead of letters after the dot(?).
