I having a problem with the integration of my Sonoff dongle
Zigbee2MQTT keeps indicating 502: Bad Gateway
Hardware:
Unraid server 6.9.2
Sonoff Zigbee 3.0 Dongle Plus (ZBDongle-P)
Conbee II
Software
Home Assistant 2022.8.1 (as VM in Unraid)
Supervisor 2022.07.0
Operating System 8.4
Mosquitto broker 6.1.2
Zigbee2MQTT 1.27.0-1
Mosquitto broker LOG
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] mosquitto.sh: executing…
[11:36:51] INFO: SSL is not enabled
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[11:36:51] INFO: Starting NGINX for authentication handling…
[services.d] done.
[11:36:52] INFO: Starting mosquitto MQTT broker…
1659778612: Warning: Mosquitto should not be run as root/administrator.
[11:36:53] INFO: Successfully send discovery information to Home Assistant.
[11:36:53] INFO: Successfully send service information to the Supervisor.
Trying to apply integration to my existing Home Assistant environment
Trying to apply integration to a complete new installation of Home Assistant
Put the Sonoff dongle into various USB ports (Dongle is always visible under the hardware tab in Home Assistant)
Used with an USB extension cable
Used without an USB extension cable
It looks like there is an issue with the Sonoff dongle.
When I replace the Sonoff dongle for my ConBee II (and adjust the port settings) Zigbee2MQTT starts up immediately without any error.
Probably I’m going to overlook something simple, but don’t get anywhere with it after 2 days…
The easiest way is to install Samba share through supervisor Add-on Store
Then browser with Windows Explorer to IP-address-HA\config\zigbee2mqtt
Open the configuration.yaml file (with notepad or notepad++) to change the pan_id and network_key.
Hit save
Delete coordinator_backup.json in the \config\zigbee2mqtt folder
Delete database.db.backup in the \config\zigbee2mqtt folder
What did you do? Just replace the network key and the PanID with some random figures? Have tried that and had no success. I am a total newbie I have to say.
After updating to HA OS 10.0 I got the error 502 bad gateway with zigbee2mqtt.
Luckily I could ‘restore’ this issue by replace a back up, but this is not a solution.
Is it really necessary to do add a new pan_id and network_key like post #5 ?
Hi there had this problem for a couple of days now after rebuilding my proxmox server to version 8…i can browse to the network share from windows but what creds do i use…the one for HA doesnt work…
Old post, but I wonder if it might have been solved by simply reflashing the stick. Blowing away a 60 node zigbee network is not a solution that is sensible.
This helped me.
But I also deleted the whole configuration.yaml inside the Z2M folder.
My problem was that I changed from one coordinator to another and it would keep trying the old port configuration.
After deleting that file and restarting the addon, it worked with the new coordinator.
Hi there, I’m also a total Newbie and have no experience in Notepad++. Thank you very much for proposed solution, I’m trying to follow your steps.
First I downloaded and startet Smaba share Add On.
Then I opened the IP-address-HA\config\zigbee2mqtt page, but it only shows me a blank page in home assistant with just “Settings” marked in the sidebar.
How do I open the configuration.yaml of Zigbee2MQTT? How do I get to open in N++/ create a link?
Is it just opening the Add On, going to configuration and selecting to work in yaml?
Have also experienced this as of the last week. Will also confirm that state.json deletion was the fix. A few extra details for what its worth:
Relocated my RPI and added a ethernet USB extension, everything worked fine for a few days. Then started receiving this error. Strangely, the problem went away on its own (or possibly due to an update that temporarily reset something), but then returned and was persistent no matter what, even with restoring zigbee and other components to recent previous versions.
I did not attempt the original solution as it seemed overkill, but a deleting state.json and then waiting a few minutes, then restart, did seem to solve it for me, and is currently still working.