Yes, this should be fixed in the Awair app.
Are the two other fixes working now?
Yes, this should be fixed in the Awair app.
Are the two other fixes working now?
Hi @RonnyW
My MQTT Hub v4.5.4 crashes almost every day on my Early 2019 Homey Pro and i have to restart ist again.
The LOG is 4781ce0c-5721-4a81-9e7e-e088fcc06cf9
Maybe you can find out what is going on.
It’s a system error.
Maximum call stack size exceeded
Perhaps the app gets too many messages from your broker resulting in too many parallel processes/calls.
There is not much I can do ![]()
Hi, first of all, thanks for keeping this app going. I only recently found out this one replaced the older 3.x version.
What I’ve found in this 4.x version is that deleted devices are retained. Perhaps I’m overlooking something.
Whilst developing my own app I’m creating/deleting/recreating just one exactly the same device multiple times, the list of devices in MQTT-hub keeps growing, continuously adding this device again and again.
Can I prune this list without removing and reinstalling MQTT-hub?
New test version 4.6.0:
Homey lawn mowers will now be exported a lawn_mower entity via HomeAssistand discovery.
Hi Ronny,
After installing the test version v4.6.0:
It turns out my 2 Trust Smart Home lights now got published as lawn mower instead of light ![]()
Installing the stable MQTT Hub version solves it; it is shown as ‘light’ again, and ‘lawn_mower’ became unknown:
If there’s anything you want me to test, just shout.
Wow, that’s not as expected ![]()
It should only export a lawn mower if device class is “lawnmower” or capability “mower_state” exists.
Can you please check the Homey device details (class, capabilities)?
Edit
There’s more devices converted to lawn_mower, @RonnyW .
The common factor is ‘Class: Socket’ Maybe this rings a bell?
Device overview of one of the sensor onoff devices (being an AVD of Device Capabilities app)
The lamp mentioned below actually is a socket with dim functionality
(original post)
Ha I can imagine ![]()
Here’s the lamp details
Thanks, will check it as soon as possible. No time this weekend… NatureOne time ![]()
New test version 4.6.1
Thanks to @Peter_Kawa . I hope it’s ok now.
Thanks for your efforts, Ronny. The issues seems to be resolved ![]()
New test version 4.7.0
Thanks to Imperial-Guard for the PR ![]()