Little strange to be honest. the way I understand it, there are 2 native capability, one for fan speed and one for heat mode.
In homey, to get a drop down widget, the list of values must be known in advance, meaning implemented! Not so hard to add a new list, but stil require an app update.
However, the flow trigger/condition should propose the list of values, not just “Empty”.
Sorry but I don’t have time to investigate, I was just quickly checking if any developper requested to take over the app.
Little update on my issue. It seems that not only can the ESP device not change access point but also not the homey. I had my device roaming randomly and this caused ESPhome to lose connection. I now set it to only connect to one access point specifically so it stopped roaming and stopped losing connection.
I see, it could explain why many have disconnect issues.
However, the reconnection feature should be able to handle it, and I don’t understand why it doesn’t.
Homey’s networking has a lot of weird quirks, I literally get dozens of crash reports for my apps (in particular HomeKitty) related to network issues that fall beyond the control of my app.
yeah, I spent lot of time trying to make the reconnection feature work out as expected, even made sure to clean up everything … (which is a big waste of resources)
as a developper, end up with such broken situation still leave me with a bad taste
Homey is much more userfriendly to be honest, but HA is more “open”.
Also Homey require an internet connection to authentificate, which end up with me leaving Homey world. I cannot accept my house to get broken just because I lost internet …
Question, how can i change the selected one of this “control functions”?
Always “Fan mode” is selected when opening, but I want it to be “Mode”.
Is that possible?
that’s homey behaviour … maybe you can cheat it by registring the capability in the order you want, or maybe through the index, like name them 1 2 3 4 in the order you want. the manager allow you to modify the index
Hi all,
I cannot add an esp32 relay.
It’s connected to the network and i can control it via web interface.
But when i try to add it via the esp wizard and after input of my bearer key, the wizard cannot find it and i get the time out message.
Hello everyone, I wonder if the Apollo Plant sensors also work on Homey? I saw them advertised with “works with homey” (see product picture) but cannot find any documentation or review of this working with homey?
I am talking about these sensors:
Ow nice! Where can i keep track when it is added, does this mean it will be fully and officially supported?
Strange though how they promote it like it is already working with Homey right now…
You can find the test version of the app here! Once it’s certified, it will automatically update to the stable release. Please note that breaking changes may still occur while the app is in testing.
SITUATION SUMMARY:
I’m trying to connect to a Konnected alarm panel to HP23 using ESPHome. The alarm panel has ESPHome FW installed and completely visible on the network with a static IP address and no password. Reading the ESPHome app info, I think the panel is added as a physical device and then the alarm capabilities (doors, motion sensor, siren, etc) are added as virtual devices.
PROBLEM STATEMENT:
Can’t add the alarm panel in the ESPHome app.
The system times out trying to add the device without Ian encryption key. Attempting to add the device using an encryption key following the user guide instructions (Mac OS with Chrome) results in "Encryption Key must be a 32-byte base64 encoded string.
Progress! I connected to the alarm panel console. The logs showed no encryption or password used. I then used the “friendly_name” exactly as shown from the log over on the Homey Pro ESPhome app and was able to connect! I’m now on the way creating the virtual devices for the alarm panel capabilities.
Thanks Peter for suggesting to check out the alarm panel console log to see what I could learn.
