Hi everyone !
my homey has crashed yesterday, and it’s in the red breathing mode.
I’m very knew to it, and I’m sure it’s nothing but i cant figure out😞.
I try to connect with usb tool, but after entering the orange mode, homey is not detected by the computer.
I also. downloaded the driver for windows as recommended, and enabled USB recognition in google
Thank for u help🙏.
Ps I’ve tried to find the solution on the forum, but i didn’t succed, be kind to mee if there’s one🙃
Have you tried with another USB-C cable?
Yes,
You should probably contact Athom: https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request
Ok cheers!
I was looking for the adresse !
Great evening!
I’ve had the same problem. another usb-cable dit the trick.
Ever get this figured out? Having the same problem
Idk, but he wrote
So, try replacing the USB-C cable with a proper one, from a well known manufacturer or brand, and it should be a data cable (not a “charge only” cable).
#cablegate
I also had some trouble connecting my Homey Pro via USB Tool. I’ll add my solutions here in case it helps anyone else.
First issue, cables and ports: I was first trying to connect to my desktop computer which lacks native USB-C ports. It did not work at all using a known good USB-A to USB-C cable, it did not even register a device connected. Presumably the Homey Pro draws too much current for an USB-A port. Connecting to my laptop which does have native USB-C worked fine.
Second issue, Linux permissions: When trying to connect using USB Tool in the browser (Chromium), it would list the device but show an “Access denied” error. I use Linux Mint, and I suspect most distros won’t permit the connection by default.
This can be solved by adding an “udev rule”. I created a new file; /etc/udev/rules.d/50-homey.rules with the following contents:
SUBSYSTEMS=="usb", ATTR{idVendor}=="0a5c", ATTR{idProduct}=="2711", MODE:="0666"
This grants all users permissions to read and write to the device. I then rebooted the computer, and now the USB Tool connection worked great.
I realize an experienced Linux user might cringe at this. I’m not an expert, there are probably better ways of doing it. For example, I suspect best practice might be to grant more granular permissions, perhaps using user groups. And the reboot is probably unnecessary if you know the correct service to restart manually.
Additionally, if you use Ubuntu and a browser installed using the default “snap” package manager, the snap service may add another layer of sandboxing and permissions issues. If so, installing a Chromium-browser via apt should solve the problem.
I think Athom sees Homey users solely as Windos and Mac users 
I’m a linux user as well, but no Pro 2023 owner 
Hi, thanks, I experienced the same issue, no connection due to usb-c to usb-a cable using my older windows10 desktop PC. I have several of those but one did work.
