[Experimental feature] Webbased frontend

[Koenkk]

This experimental feature allows to run a frontend straight from Zigbee2MQTT (so no additional setup is required).
This frontend is developed by @nurikk, the source code can be found here: https://github.com/nurikk/z2m-frontend

To enable this, switch to the dev branch and add the following to your configuration.yam.

frontend:
  port: 8080

In case you find any issues in the frontend, report them here: https://github.com/nurikk/z2m-frontend/issues

[sjorge]

Initial impressions using firefox on macOS

• the padding is a bit tight see the left side.
• some of my devices are at half or less battery %, perhaps the battery icon could also reflect this.
• device/info page could perhaps link to the online docs, as they usually have pairing notes or even configuration notes.
• (not really a frontend thing but) perhaps we should update the product images so they have a transparent background
• product images are hotlinked from the main site, if you proxy the interface over ssl, you get mixed content warnings at best or they don't load at all. ==> fetch these in the background and cache them locally?
• perhaps the 'action' menu should just be 2 right aligned buttons
• log tail with maybe some color highlighting would be nice to have eventually too
• would be nice to have device_options editable via the settings tab
• per-device options would also be nice to have editable somewhere
• large networkmaps are... euhm useless
  

The group view is absolutely amazing!

Very promising start!

[sjorge]

The bind tab also no longer show the devices friendly name, the network address is still in the URL though, but would be nice to also have that visible.

[Westcott1]

Does using port 8080 conflict with Domoticz, when it's on the same RPi as Z2M?

[nurikk]

Does using port 8080 conflict with Domoticz, when it's on the same RPi as Z2M?

You can specify any port in configuration

[sjorge]

Sorting is working great, except for the power colomn.

[SAOPP]

Guys, as I understand it, the map is saved only for the current session in the browser?

[nurikk]

Guys, as I understand it, the map is saved only for the current session in the browser?

Yes, refresh page and you lose your data

[nurikk]

Sorting is working great, except for the power colomn.

What wrong with it?

[nurikk]

How do you find this way of showing logs? (only data from bridge/logging is shown)

[sjorge]

It doesn’t do anything. I would have expected the battery and mains powered one to be grouped together. (Or ideally sort the battery ones on battery level) ~ sjorge

…

On 7 Sep 2020, at 05:12, John Doe ***@***.***> wrote:  Sorting is working great, except for the power colomn. What wrong with it? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[SAOPP]

Interesting... I don't have a logs menu. It's optional menu? And it can be turn on from configuration?

[nurikk]

Interesting... I don't have a logs menu. It's optional menu? And it can be turn on from configuration?

it's sneak peek from my dev environment, stay tuned :)

[nurikk]

It doesn’t do anything. I would have expected the battery and mains powered one to be grouped together. (Or ideally sort the battery ones on battery level) ~ sjorge
…
On 7 Sep 2020, at 05:12, John Doe @.***> wrote:  Sorting is working great, except for the power colomn. What wrong with it? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

You should update dependencies, yesterday I've released update. It adds sorting by battery level

[nurikk]

Also upcoming touchlink page

[sjorge]

Also upcoming touchlink page

Oh how do you get the devices it detected? I was not aware z2m exposed that information, well i guess if you open the network for joining before doing the request you could see which ones publish a deviceJoined event.

[nurikk]

Also upcoming touchlink page

Oh how do you get the devices it detected? I was not aware z2m exposed that information, well i guess if you open the network for joining before doing the request you could see which ones publish a deviceJoined event.

This feature yet to be implemented, but in general it's just splitting this code and exposing via z2m https://github.com/Koenkk/zigbee-herdsman/blob/33d13a2fba4cc306d11398bf608293c2a6c7aa63/src/controller/touchlink.ts#L16

[sjorge]

So after some changes it could be publish under the zigbee2mqtt/bridge/config/touchlink/+ topic, that be nice.

[sjorge]

@nurikk Given I have a large network map, would you be interested in the the output? real output to work off or create tests from is always useful IMHO.

[netweaver1970]

very nice work! Any chance of having a linkable/proxyable config page from within HomeAssistant to get to the new Z2M GUI? I have Z2M, letsencrypt(incl NGINX rev. proxy) in separate containers so maybe an HA ingress based solution is needed?
I prefer not to open up another endpoint straight via the NGINX reverse proxy, as the page doesn't have authentication. So using the authentication of HA would be nice/enough.

[netweaver1970]

I might have missed it but is there already an interface for binding/unbinding remotes to groups? That part of Z2M can also use some GUI love.

[sjorge]

Yes! If you view the remote’s details there is a binds tab, works pretty well. ~ sjorge

…

On 7 Sep 2020, at 17:10, netweaver1970 ***@***.***> wrote:  I might have missed it but is there already an interface for binding/unbinding remotes to groups? That part of Z2M can also use some GUI love. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[nurikk]

I've published next release of frontend. Mostly bug fixes

https://github.com/nurikk/z2m-frontend/blob/master/CHANGELOG.md#0148-2020-09-08

[nurikk]

@nurikk Given I have a large network map, would you be interested in the the output? real output to work off or create tests from is always useful IMHO.

Yes, please! you can send me contents of bridge/response/networkmap (raw) ?

[sjorge]

@nurikk Given I have a large network map, would you be interested in the the output? real output to work off or create tests from is always useful IMHO.

Yes, please! you can send me contents of bridge/response/networkmap (raw) ?

https://gist.github.com/sjorge/332f92e691a2475590bdebaf7501b0d6

[sjorge]

Been playing with the latest release, touchlink doesn't seem to work but I think it's missing the above mentioned changes to z2m.

For the logs page:

• would be nice to have a dropdown to change the level on runtime (thats the default anyway, so the options can be on hte log page I think)
• scroll bar for each long record is a bit odd, perhaps have a global one for the whole log tab? makes it easier to compare values in two long lines too.

on the devices page

• sorting on power still broken for me
• icons still show 100% while most devices are between 85-50% battery left

on map page

• broken on firefox now, no button to request the map (works fine on safari)

[netweaver1970]

Yes! If you view the remote’s details there is a binds tab, works pretty well. ~ sjorge
…
On 7 Sep 2020, at 17:10, netweaver1970 @.***> wrote:  I might have missed it but is there already an interface for binding/unbinding remotes to groups? That part of Z2M can also use some GUI love.

I made a new group with a single IKEA bulb (LED1732G11), that seems to work nicely.
But when trying to bind a Lumi/Aqara/Opple/Xiaomi WXKG06LM 1-gang wall switch to that new group, I'm not getting the OnOff cluster to select for binding.
I'm only getting these ones : genBasic, genGroups, genIdentify, Scenes, genOta, genMultistateInput. Which one can be used to simply toggle the lightbulb?
Or doesn't this switch allow direct binding?

Thanks.

[nurikk]

icons still show 100% while most devices are between 85-50% battery left

Hi, @sjorge ! Can you please send me your bridge/devices and bridge/+ (device statuses) dumps?

[sjorge]

icons still show 100% while most devices are between 85-50% battery left

Hi, @sjorge ! Can you please send me your bridge/devices and bridge/+ (device statuses) dumps?

I've updated the previous gist, not sure what oyu mean with device statuses dump though?

[Koenkk]

@kirelam see sonoff documentation: https://sonoff.tech/wp-content/uploads/2021/09/Zigbee-3.0-USB-dongle-plus-firmware-flashing-1-1.docx

@parshivets sorry looked at the wrong entry in the docker compose file, what happens when you remove the host from the z2m configuration.yaml and do a curl localhost:8887 on the system.

[parshivets]

@kirelam see sonoff documentation: https://sonoff.tech/wp-content/uploads/2021/09/Zigbee-3.0-USB-dongle-plus-firmware-flashing-1-1.docx

@parshivets sorry looked at the wrong entry in the docker compose file, what happens when you remove the host from the z2m configuration.yaml and do a curl localhost:8887 on the system.

This is from inside the container:
/app # curl localhost:8080
curl: (7) Failed to connect to localhost port 8080 after 0 ms: Connection refused

From host:
parshivets@parnas:~$ curl localhost:8887
curl: (56) Recv failure: Connection reset by peer

And this is just to show that other containers are ok:
parshivets@parnas:~$ curl localhost:8080

<title>qBittorrent Web UI</title>

[Koenkk]

@parshivets I believe the issue is that startup is blocked because it cannot to the MQTT server, please check your MQTT settings, you should see Connected to MQTT server in your logs

[parshivets]

@parshivets I believe the issue is that startup is blocked because it cannot to the MQTT server, please check your MQTT settings, you should see Connected to MQTT server in your logs

you were right. For some reason in configuration.yaml if I set ip:1883 - doesn't work even I was able to telnet from inside the container. Changed to Mosquitto_container_name:1883 - it works!

[mcmellow]

Thanks a lot for the Frontend page. This is great. At this moment it is at version and running on my Raspberry Pi 3B+ How can I update the Frondend page to a new version.

[Koenkk]

@mcmellow it is updated automatically when you update z2m

[jessegutkowski]

@parshivets I believe the issue is that startup is blocked because it cannot to the MQTT server, please check your MQTT settings, you should see Connected to MQTT server in your logs

you were right. For some reason in configuration.yaml if I set ip:1883 - doesn't work even I was able to telnet from inside the container. Changed to Mosquitto_container_name:1883 - it works!

I think that I'm having the same issue -- I cannot connect to my mqtt server. What do you mean by "changed to mosquitto_container_name:1883? Below is the details of my mosquitto container:

Any help would be greatly appreciated.

[parshivets]

@parshivets I believe the issue is that startup is blocked because it cannot to the MQTT server, please check your MQTT settings, you should see Connected to MQTT server in your logs

you were right. For some reason in configuration.yaml if I set ip:1883 - doesn't work even I was able to telnet from inside the container. Changed to Mosquitto_container_name:1883 - it works!

I think that I'm having the same issue -- I cannot connect to my mqtt server. What do you mean by "changed to mosquitto_container_name:1883? Below is the details of my mosquitto container:

Any help would be greatly appreciated.

in docker containers can ping each other by container name. check container name
docker ps --format "{{.Names}}"
use it instead of ip

[danielvandenberg95]

@parshivets I believe the issue is that startup is blocked because it cannot to the MQTT server, please check your MQTT settings, you should see Connected to MQTT server in your logs

I'm currently in a bit of a situation where this is actually a slight issue.
Due to some remodeling work, power to my MQTT server is turned off.
I want to replace the wall plug to my server with a different one.
I can reach my Pi running zigbee2mqtt. However, I can not pair my new plug, because the interface won't start, because the MQTT server is down.

So, I vote for starting the frontend before connecting to MQTT.

[wsw70]

@danielvandenberg95 I am not sure if I understand your problem correctly, but couldn't you pair the plug in another socket (if this is the kind of "intermediate smart plug"), or temporarily connect your server to another socket (of the new plug is a fixed one - I would be interested in the model on that case)

[danielvandenberg95]

Yeah I could have connected my server to another socket, but that would mean powering it up, down, up. That's what I was trying to prevent.

"If it's down now anyways I can just as well swap out the plug" - my thought process

[zachfi]

I've been using zigbee2mqtt for a while now, and it has been really great. More recently I've deployed into kubernetes and accidentally nuked the volume the configuration was on. It occurs to me, after enabling the frontend that a simple way to backup and restore would be really handy. I've spent a few years building up some xiaomi aqara, but after I broke the network, these devices didn't re-pair to the new network, so being able to backup before doing something dangerous is obvious, and perhaps the frontend could provide a simple way to do this.

[HDP13]

Quizás sea una tontería, pero como en el manual dice que por seguridad hay que cambiar la serie de números en vertical, así lo hice, y todo dejo de funcionar.
Después de darle mil vueltas lo único que hice fue desplazar todos los - ¿? un paso a la izquierda, quizás parezca una tontería pero así me apareció el panel después de reiniciar.

Un saludo

[zachfi]

What's confusing about the above, is that the config file seems to be read and written to by z2m, so a simple point in time backup could still result in missing devices if you don't get a recent backup of the config.

[Asc0tt]

Hi! I have installed z2m on my raspberry pi zero with Raspberry Pi OS. TI CC2531 USB stick.
Before i don't use frontend because don't know that it exists.
It was version 1.17.1 and now I have updated to lates (1.25.2).
After start z2m daemon i got error that nodejs too old.
After i update npm up to 8.12.1 and nodejs up to v18.3.0.
Start daemon and frontend still no available.
Server starts normally, and has connection to mqtt bus.
Port don't occupied by other services.
Home Assistant is not installed.
How can i check that all works well and how i can get reasons why frontend still not available?

configuration.yaml

homeassistant: false
permit_join: true
forntend: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://localhost'
  user: 'my_user'
  password: 'my_pass'
serial:
  port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CD6ED04-if00
advanced:
  network_key:
    - 211
    - ..... and so on

starting logs:

> [email protected] start
> node index.js

Zigbee2MQTT:info  2022-06-06 12:20:47: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2022-06-06.12-20-46' filename: log.txt
Zigbee2MQTT:info  2022-06-06 12:20:47: Starting Zigbee2MQTT version 1.25.2 (commit #a252914e)
Zigbee2MQTT:info  2022-06-06 12:20:48: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:info  2022-06-06 12:20:53: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-06-06 12:20:53: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"}'
Zigbee2MQTT:info  2022-06-06 12:20:53: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-06-06 12:20:53: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-06-06 12:20:53: Allowing new devices to join.
Zigbee2MQTT:warn  2022-06-06 12:20:53: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-06-06 12:20:53: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-06-06 12:20:53: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:info  2022-06-06 12:20:56: Connected to MQTT server
Zigbee2MQTT:info  2022-06-06 12:20:56: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2022-06-06 12:20:58: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"a252914e","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20201127,"transportrev":2},"type":"zStack12"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x00124b001cd6ed04","panID":6754},"permit_join":true,"version":"1.25.2"}'

curl

pi@smart-pie:/ $ sudo curl --get http://localhost:8080
curl: (7) Failed to connect to localhost port 8080: Connection refused

netstat output

pi@smart-pie:/ $ sudo netstat -tuplan | grep LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      455/sshd
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      448/mosquitto
tcp6       0      0 :::22                   :::*                    LISTEN      455/sshd
tcp6       0      0 :::1883                 :::*                    LISTEN      448/mosquitto

[wsw70]

It may be this line:

forntend: true

It has a typo (should be frontend)

[Asc0tt]

So stupid error. @wsw70 thanks so much!

[ls500h]

I have add the front end working well until after the updates today. Now I have z2m working correctly but no :8080 GUI available, both edge and chrome return ERR_CONNECTION_REFUSED and sudo curl --get http://localhost:8080 returns
curl: (7) Failed to connect to localhost port 8080: Connection refused.

Yaml is:
availability: true
homeassistant: false
frontend: true
port: 8080
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: mqtt://localhost
serial:
port: /dev/ttyACM0
devices:
'0x00124b00224145bb':
friendly_name: TempHum1
....etc

Any suggestion would be appreciated

[jbrepogmailcom]

Hello the frontend does not seem to work for me. I have added entry
frontend: true
port: 8080

to file /opt/zigbee2mqtt/data/configuration.yaml

then I restarted zigbee2mqtt service, but I am getting "This site can’t be reached". It looks like no web server is running.

[SyBeer]

This is wrong

frontend: true
port: 8080

It should be:

frontend:
port: 8080

[GernotHot]

Hi all,

I have two (I thought) identical (docker on raspian) installations. One with a working frontend, and the other not.

The only difference between the installations is: the one is running on a Raspberry 3 and the other an Raspberry 2:

root@xxx:/data_local# cat /sys/firmware/devicetree/base/model
Raspberry Pi 2 Model B Rev 1.1

and the other (working) is a

Raspberry Pi 3 Model B Rev 1.2

I call z2m with

docker run\
    --restart=always \
    -v /data_local/zigbee2mqtt:/app/data \
    -v /run/udev:/run/udev:ro \
    -e TZ=Europe/Vienna \
    --device=/dev/ttyAMA0 \
    --user 1000:1000 \
    --group-add dialout \
    -p 8080:8080 \
    koenkk/zigbee2mqtt

and the configuration.yaml is

homeassistant: true
permit_join: true
frontend:
  # Optional, default 8080
  port: 8080
  # Optional, default 0.0.0.0
  host: 0.0.0.0
availability:
  active:
    timeout: 10
  passive:
    timeout: 1500
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://docker0
serial:
  adapter: deconz
  port: /dev/ttyAMA0
advanced:
  log_level: debug

During startup, "frontend" is not mentioned anywhere:

Using '/app/data' as data directory
Zigbee2MQTT:debug 2022-12-23 20:45:04: Can't load state from file /app/data/state.json (doesn't exist)
Zigbee2MQTT:info  2022-12-23 20:45:04: Logging to console and directory: '/app/data/log/2022-12-23.20-45-03' filename: log.txt
Zigbee2MQTT:info  2022-12-23 20:45:04: Starting Zigbee2MQTT version 1.28.4 (commit #52e545f)
Zigbee2MQTT:info  2022-12-23 20:45:04: Starting zigbee-herdsman (0.14.76)
Zigbee2MQTT:debug 2022-12-23 20:45:04: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"deconz","path":"/dev/ttyAMA0"}}'
Zigbee2MQTT:info  2022-12-23 20:45:05: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-12-23 20:45:05: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":105,"product":0,"revision":"0x26690700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:debug 2022-12-23 20:45:05: Zigbee network parameters: {"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754}
Zigbee2MQTT:info  2022-12-23 20:45:05: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-12-23 20:45:05: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-12-23 20:45:05: Allowing new devices to join.
Zigbee2MQTT:warn  2022-12-23 20:45:05: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-12-23 20:45:05: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-12-23 20:45:06: Connecting to MQTT server at mqtt://docker0
Zigbee2MQTT:debug 2022-12-23 20:45:06: Using MQTT anonymous login
Zigbee2MQTT:debug 2022-12-23 20:50:04: Saving state to file /app/data/state.json
Zigbee2MQTT:debug 2022-12-23 20:55:04: Saving state to file /app/data/state.json

only, when the service is shut down, the "frontend" is mentioned:

Zigbee2MQTT:error 2022-12-23 20:57:37: Failed to call 'Frontend' 'stop' (TypeError: Cannot read properties of null (reading 'clients')
    at Frontend.stop (/app/lib/extension/frontend.ts:59:39)
    at Controller.callExtensions (/app/lib/controller.ts:316:40)
    at Controller.stop (/app/lib/controller.ts:193:9)
    at stop (/app/index.js:111:5)
    at process.handleQuit (/app/index.js:117:9))
Zigbee2MQTT:debug 2022-12-23 20:57:37: Saving state to file /app/data/state.json
Zigbee2MQTT:error 2022-12-23 20:57:37: Not connected to MQTT server!
Zigbee2MQTT:error 2022-12-23 20:57:37: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: 'offline
Zigbee2MQTT:info  2022-12-23 20:57:37: Disconnecting from MQTT server
Zigbee2MQTT:info  2022-12-23 20:57:37: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-12-23 20:57:38: Stopped zigbee-herdsman
Zigbee2MQTT:info  2022-12-23 20:57:38: Stopped Zigbee2MQTT

I checked within the container, if a service is listening on port 8080 - but no 8080/tcp

root@xxx:/data_local# docker exec -it 6ad604d0e2f7 /bin/netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
udp        0      0 0.0.0.0:58134           0.0.0.0:*                           
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node Path

Honestly, I have no clue anymore. Any ideas? Thanks in advance :)

[HDP13]

Buenas taews debfio a mi enfermedad se me pasan cosasz y quizas algunas grav3s, pro si me explca la solucion, lo que menos deseo es hacer las cosas mal. Gracoas `pr entenderp El vie, 23 dic 2022 a las 20:31, SyBeer (< ***@***.***>) escribió:

…

This is wrong frontend: true port: 8080 It should be: frontend: port: 8080 — Reply to this email directly, view it on GitHub <#4266 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYDCYXC4OPUZ6VTVIIPRQELWOX4X7ANCNFSM4QY4EBSQ> . You are receiving this because you commented.Message ID: ***@***.***>

--

[seventhsite]

Same issue on version 1.30.1 (commit #eb878d3) - frontend queitly not starting.
Config simply
frontend: true
No logs, no open port

debug 2023-02-18 02:41:46: Loaded state from file /app/data/state.json
info  2023-02-18 02:41:46: Logging to console and directory: 'data/log/' filename: z2m_2023-02-18.02-41-46.log
info  2023-02-18 02:41:46: Starting Zigbee2MQTT version 1.30.1 (commit #eb878d3)
info  2023-02-18 02:41:46: Starting zigbee-herdsman (0.14.89)
debug 2023-02-18 02:41:46: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app
/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[23],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"baudRat
e":115200,"path":"/dev/ttyAML2","rtscts":false}}'
info  2023-02-18 02:41:55: zigbee-herdsman started (resumed)
info  2023-02-18 02:41:55: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210218,"transportrev":2},"type":"zStack3x0"}'
debug 2023-02-18 02:41:55: Zigbee network parameters: {"channel":23,"extendedPanID":"0x00124b00215bac80","panID":6754}
info  2023-02-18 02:41:55: Currently 0 devices are joined:
info  2023-02-18 02:41:55: Zigbee: disabling joining new devices.
info  2023-02-18 02:41:56: Connecting to MQTT server at mqtt://192.168.7.3:1883
debug 2023-02-18 02:41:56: Using MQTT keepalive: 60
debug 2023-02-18 02:41:56: Using MQTT login with username: homeassistant
debug 2023-02-18 02:41:56: Using MQTT client ID: 'homeassistant'

seventh@jethub-j80:~/z2m$ ss -tulpn
Netid               State                Recv-Q               Send-Q                               Local Address:Port                                Peer Address:Port               Process               
udp                 UNCONN               0                    0                                    127.0.0.53%lo:53                                       0.0.0.0:*                                        
udp                 UNCONN               0                    0                                        127.0.0.1:323                                      0.0.0.0:*                                        
udp                 UNCONN               0                    0                                            [::1]:323                                         [::]:*                                        
tcp                 LISTEN               0                    4096                                 127.0.0.53%lo:53                                       0.0.0.0:*                                        
tcp                 LISTEN               0                    128                                        0.0.0.0:22                                       0.0.0.0:*                                        
tcp                 LISTEN               0                    100                                        0.0.0.0:1883                                     0.0.0.0:*                                                                          
tcp                 LISTEN               0                    128                                           [::]:22                                          [::]:*                                        
tcp                 LISTEN               0                    100                                           [::]:1883                                        [::]:*                                        

Any idea how to run frontend or get a more detailed logs?

[seventhsite]

Solve it - problem is that the z2m is not connected to mqtt. Connecting, but not connected. Before frontend it need to connect to mqtt.

[McMacaron]

I think that the problem is in configuration.yaml file. It will take set up for first time from the configuration.yaml. After that, it will not react to any change in that file. It will take always the first set-up from :/app/data inside of container. So there is no possibility to correct or change settings.

[junosuarez]

This issue is 3 years old. Please open a new issue if needed.

[ffries]

Syslogd remote configuration is wrong.
"hostname" is replaced with "localhost" in the web interface
Anyhow ... remote logging to syslogd does not work.