Playing with Homey to see if I have any interest in paying for it. If I was to continue I would have paid the subscription to keep i ton TrueNas and bought one or more bridge units. BUT Other than Sonos and Ring I have been unable to detect any of my TP-Link, Sonoff or other devices. I have them on Ewelink but the Homey app can’t see them.
I set up a flow to sound my Ring doorbell on multiple Sonos speakers, so I can hear it in the workshop as well as the house, tested it twice, was impressed, then next day it didn’t work at all, luckily I had not disabled the reliable Alexa system.
Reading the forums it seems that it this is a flakey product with an apparently easy front end.
Before I give up and never look back, does anyone have any advice that may make me continue and possibly spend money on Homey?
Sounds typical for either a double NAT or an incorrect VLAN (isolated/“guest”/“IoT network”) setup.
Thank you Robert,
No VLAN here, WiFi is a mesh system the onboard WiFi of the router is turned off, single SID for both 2.5 and 5. Don’t have a double NAT as far as I can see, any suggestions on how I could look for that possibility?
Double NAT is typically caused by having a WiFi access point configured as a router (as opposed to a bridge) behind an existing (telco) router. In that case, WiFi devices are often NAT’d by the WiFi router, and any LAN devices on the other end (plugged into the telco router, either directly or through a switch) will have a hard time being able to discover those WiFi devices.
Thanks for that, I do have an assortment of networking gear but the only Wifi up and running is a 3 point Mesh so Double NAT is probably not an issue. Thing is all the devices are discovered, they are all registered onto my WiFi and exist in EWelink Alexa etc. the only system that can’t see them is Homey.
I assume you followed all instructions documented here? Especially the mDNS settings.
Is the SHS instance also connected to the mesh system’s Ethernet port? The mesh system (f.e. Deco) usually creates its own network in its own subnet.
Yes the MDNS was set and I followed all instructions, I have been through and double checked the installation it is right.
I use the BT disks, and have turned off DHCP on the WiFi so that all comes from the central (wired) switch. This is a home system if I get close to 200 devices then I will have to admit to having a problem!
So you have a mesh network and the IPs come from the switch’s DHCP server? So the mesh system is in AP mode, is that what you mean?
When you connect to your network and use Fing to run a network scan, do you see both the SHS and the devices that you want to connect?
I have not used Fing, but yes I can see all the devices on my network, and they are all usable from Alexa many are Sonoff and listed in Ewelink but the Ewelink app on Homey says no devices.
Edit, and I have just updated the firmware on them all no difference
The eWeLink app uses the cloud, so network issues shouldn’t matter. You should contact the eWeLink Homey app developer
I have run into similar issues with certain products including TP-Link Kasa. I am running Home Assistant along with homey. Home Assistant Community app exposes TP-Link and other devices into Homey to control them. Not ideal. But with limited support from Homey. This solution for me seems to work for the time being.
Which TP-Link products? TP-Link Kasa, TP-Link Tapo, TP-Link Deco, TP-Link Router or TP-Link Omada?
So you mean that this app doesn’t work?
What error message do you get?
Only works on certain switches. Interestingly works with HS210 showed up in TPLINK Kasa Smart right away. HS-200 & HS220 still does not show up.
In that case, it’s not the same issue as @Pete_Ravensccroft . You should contact Athom here:
Yup. I did. It went on for couple months as the responses take a while. They were not able to help as they no longer have support from TP-Link itself which does not make sense in this day and age…
