-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
502 bad gateway with zigbee CC2652R stick #543
Comments
i just installed the add on and get this error too |
I have the same issue, anyone who knows how to solve? |
The fix for me was flashing my zigbee stick with the last firmware. |
ok interesting, I am pretty new to this. Lets find out how to flash the stick.. |
what kind of zigbee stick do you have? |
i have flash it with a program, you can follow this link: https://electrolama.com/radio-docs/flash-ti-flash-prog/ |
I have the same problem here with the slae.sh CC2652 stick |
My solution was to send this fucking stick back to the guy who does not a fuck on any requests from his customers and returning my money back from PayPal. After that I bought a sonoff stick which hast much more power, is professionally produced and costs only 1/5. |
I fixed it! Problem was that Zigbee Home Automation (ZHA) was installed as an integration by default. I didn't do that myself. I deleted this and restarted Zigbee2MQTT and it worked!
I have no experience with support from slae.sh, so I can't comment on that. |
I tried to do a clean install of HA 2022.4 with a newly flashed sonoff usb 3.0 dongle (CC1352/CC2652, Z-Stack 3.30+ (build 20220219) and even after removing ZHA I was getting this error (10 times I tried). Got so annoyed I switch to ZHA oput of needing things back up for the WAF. That is not going well (changes in this release of ZHA seem to have been lacking in rigor) so the sooner I can confirm this is fixed the better. Getting a new host v soon so will retry clean install then and provide more info if still an issue. |
I get an error after installing it:
The text was updated successfully, but these errors were encountered: