I recently decided to purchase a Homey Pro. I was excited by the promises of the device. As a long-time Jeedom user, I had grown tired of spending hours configuring things for mediocre results. I thought I had found a simpler, more user-friendly tool—especially one that would be accepted by my wife.
After a few days of testing, I’m quite disappointed. There are many bugs and malfunctions that already make me regret Jeedom. Here’s a non-exhaustive list of some of the issues I’ve encountered:
Starting with a Wi-Fi connection. Then, I plugged in the Ethernet cable and in the settings I saw: “Wi-Fi – yes”, “Ethernet – yes”. Which one am I actually connected to? A few days later, “Ethernet” switched to “no”. Why?
My first very simple automation flow (when the cooktop is on, the hood turns on) worked twice and then stopped. I had to recreate the flow, it worked again twice, and then stopped again.
I’ve had no luck with the Z-Wave protocol: the first device I tried to connect (Everspring light sensor) wasn’t recognized.
I can’t access the web interface. I get the message “Websocket error”.
In short! I’m back to tinkering again, trying to find solutions. I imagine I’ll find help on the forum, but it’s already a lot to deal with in just a few days. And this isn’t exactly helping me convince my wife that spending over €400 on this (with the Ethernet dongle) was worth it. Disappointed!
I’m sorry you’re having some problems with Homey Pro, but I’m afraid you won’t get any help from other users this way…
I think many would be able to help you, but you will have to ask and above all provide more information.
I switched to Homey Pro about 3 years ago and don’t regret it for a second. But I also had to learn a lot about the new techniques and peculiarities at the beginning. Not everything always works as it should, but you have to be open to accepting help and asking questions.
Z-Wave, for example, has a few peculiarities that need to be taken into account, otherwise it won’t work or will only work partially.
A strong Z-Wave mesh network is the biggest requirement.
Regarding the error “Websocket error” you will find some entries and solutions in the forum. Just search for it in the forum…
Hello Asterix,
Thank you for your reply.
I have no doubt that I’ll find support from the forum users. Your kind response confirms it.
I was just a bit disappointed by the number of issues in such a short time.
I’m ready to roll up my sleeves. Coming from Jeedom, I’m used to it
Thanks again!
There is a kind of a learning curve and reading the help articles from Athom is also very helpful.
Homey Pro 2023 has some drawbacks but I managed to work around them, mainly by the help of many users here in this forum.
1,5 year later I do love it very much. I can use and control my equipment if apps are available (or, the other way around, I only buy stuff which is supported by Homey apps, created by volonteers).
The advanced flows are great. No need to program in a difficult language but “in spaghetty”.
You need to give it another try. I’ve used several platforms, and my Homey Pro has consistently performed the best. Regarding WiFi, it must be your WiFi. Mine has worked flawlessly on WiFi, Zigbee, Bluetooth, and other protocols. The flows are easy to set up, and troubleshooting is a breeze. So far, it’s the best home automation system I’ve ever owned.
Homey is known to have issues with WiFi networks that are more modern than the ones we had back in 2009: it has problems dealing with 5Ghz, it has problems dealing with band steering, it has problems dealing with mesh network, it has problems dealing with IPv6.
It’s often also only Homey that’s causing problems, and many people have dumbed down their network to get Homey to work properly with it.
My wifi comes from a modern modem: FritzBox 6690 Cable modem (far later than 2009 ….)
I connect Homey Pro over 5 GHz (it switches sometimes to another AP, connected as mesh).
I use IPv6.
It works perfect.
private
Hi Theo,
Stop met dit forum. Zeg je abonnement hier op en ga lekker genieten van de dingen die je wel blij maken. Hier blijven mopperen maakt niemand blij.
/private
My Homey Pro also says ‘no’ for ethernet. My ethernet switch confirms the dongle is connected but is not passing any traffic. I have never noticed this before.
I don’t know if this is relevant, apologies if not. I just got notified that local accounts now work. I.e. the connection is directly to an IP address of the Homey Pro. I wonder if this would help with the websocket error.
