Zigbee2Mqtt gives me 502: Bad Gateway

Configuration Zigbee
,
1

I’ve got a CC2531 chip that I flashed with the correct firmware and it’s tuning on and in the zigbee2mqtt logs I can see that it finds it. Before I had flashed the CC2531 chip Zigbee2Mqtt gave me error so I assume the chip is working fine.

When I try to open the Zigbee2Mqtt interface I get a 502: Bad Gateway and in the supervisor log I get this message:

21-10-21 11:05:39 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.5:8099 ssl:default [Connect call failed ('172.30.33.5', 8099)]

Zigbee2mqtt
Current version: 1.21.2-1

image
image1325×473 44.3 KB 

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://localhost:1883
  user: mqtt
  password: xxxxx
serial:
  port: /dev/ttyACM0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false
2

What does the Zigbee2MQTT log say ?

3

image
image1072×643 77.6 KB

4

According to that screenshot, Zigbee2MQTT is not fully started yet. So wait a little bit before you try again.

5

I’ts been like this for a whole day…
I guess something in the actual addon is broken?

6

There definitely should be more text after

> [email protected] start
> node index.js
7

You haven’t added everything in your configuration to enable the frontend.
Read the documentation tab in the addon it has what you need to copy into your configuration.

8

if you’re referring to I’ve already done that…

frontend:
 port: 8099
experimental:
 new_api: true

I get this:

21-10-21 13:11:21 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (45df7312_zigbee2mqtt)
9

Yes, the documentation on the add-on is wrong.

experimental:
 new_api: true

has been removed a log time ago.

10

Yeah… so is there something else I should do instead of “new_api: true”?

11

Your config seems fine, it just seems Zigbee2MQTT does not start fully as it never gets beyond

> [email protected] start
> node index.js

and I don’t have an idea why.

12

Hmm alright :frowning:

Do you have an idea why I get this when I try to open the Zigbee2Mqtt UI?

21-10-21 13:57:31 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.5:8099 ssl:default [Connect call failed ('172.30.33.5', 8099)]
21-10-21 13:59:22 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.5:8099 ssl:default [Connect call failed ('172.30.33.5', 8099)]
13

Yes, Zigbee2MQTT is not yet started fully, so the webinterface is not running.

14

Alright… running netstat I get this:
image
is the 172.30.33.2 a local IP?

btw I should’ve mentioned this in the start. I’m running my home-assitant through duckdns.org and opened the port 443. Maybe this has anything to do with the Zigbee2MQTT?

15

Setting permit_join gives me these log, does this indicate that it’s running? (Still getting Bad gateway…)

image
image1078×615 93.8 KB

16

Yes, seems to be running

Try (without ingress) http://ip-of-ha:8099 and see if you get something.

17

Getting ERR_CONNECTION_REFUSED

18

And the same with https://ip-of-ha:8099 ?
oh, I see someone clicked the link http://ip-of-ha:8099 in my previous post. Be sure to replace ip-of-ha with the ip-address of your home assistant instance.

19

Yes same result. And yeah hahaha I accidentally clicked the link…

20

Is there any other zigbee2mqtt alternative I can try?