Zigbee2mqtt not displaying anything in web dashboard

[automaker]

I have just installed Z2M and its all working from MQTT manual commands but there is nothing detected or showing on the Z2M web dashboard.

For example under the Z2M webgui settings, there is no information about my Conbee2 dongle and I cant pair anything by pressing “Permit Join”. But if I use MQTT Explorer, I can see all the dongle data and if I publish a packet “zigbee2mqtt/bridge/request/permit_join” TRUE, I can join a device and it will show up as an entity in HA with all the correct data.
Any idea’s what could be causing the GUI to fail?
TIA

Home Assistant 2023.3.6
Supervisor 2023.03.2
Operating System 9.5
Frontend 20230309.1 - latest
MQTT Mosquitto - 6.2.0
Zigbee2MQTT - 1.30.2-1

[tom_l]

What do your Z2M addon logs say?

[nickrout]

Are you using the addon? Have you enabled the frontend by following the docs

Enable ingress to have the frontend available in your UI: Settings → Add-ons → Zigbee2MQTT → Show in sidebar . You can find more details about the feature on the Zigbee2MQTT documentation.

[automaker]

No issues that I can see

2023-03-28T04:12:11.570Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 116
2023-03-28T04:12:11.570Z zigbee-herdsman:deconz:adapter false, true, false
2023-03-28T04:12:11.573Z zigbee-herdsman:deconz:adapter resolve request
2023-03-28T04:12:11.582Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2023-03-28T04:12:11.585Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:11.587Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x2d03 request id: 24 confirm status: 0
2023-03-28T04:12:11.590Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:11.591Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 117
2023-03-28T04:12:11.591Z zigbee-herdsman:deconz:adapter false, true, false
2023-03-28T04:12:11.591Z zigbee-herdsman:deconz:adapter resolve request
2023-03-28T04:12:14.298Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2023-03-28T04:12:14.299Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:14.299Z zigbee-herdsman:deconz:driver query aps data indication
2023-03-28T04:12:14.299Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 248
2023-03-28T04:12:14.313Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 248 srcAddr: 0x9cdb destAddr: 0x0 profile id: 0x104 cluster id: 0xfc7d lqi: 255
2023-03-28T04:12:14.315Z zigbee-herdsman:deconz:frameParser response payload: 12,124,17,6,10,7,0,32,25
2023-03-28T04:12:14.327Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":6,"manufacturerCode":4476,"commandIdentifier":10},"Payload":[{"attrId":7,"dataType":32,"attrData":25}],"Command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}},"address":40155,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
Zigbee2MQTT:debug 2023-03-28 15:12:14: Received Zigbee message from '0x9035eafffe1a1de3', type 'attributeReport', cluster 'manuSpecificIkeaAirPurifier', data '{"fanSpeed":25}' from endpoint 1 with groupID null
2023-03-28T04:12:14.347Z zigbee-herdsman:controller:endpoint DefaultResponse 0x9035eafffe1a1de3/1 64637(10, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2023-03-28T04:12:14.359Z zigbee-herdsman:deconz:adapter no response expected
2023-03-28T04:12:14.365Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
Zigbee2MQTT:info  2023-03-28 15:12:14: MQTT publish: topic 'zigbee2mqtt/0x9035eafffe1a1de3', payload '{"air_quality":"excellent","child_lock":"UNLOCK","fan_mode":"auto","fan_speed":4,"fan_state":"ON","led_enable":true,"linkquality":255,"pm25":0,"replace_filter":false,"update":{"installed_version":69633,"latest_version":69633,"state":"idle"},"update_available":false}'
2023-03-28T04:12:14.394Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x9cdb EP:1 SeqNr. 249 request id: 25
2023-03-28T04:12:14.413Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 25 status: 0
2023-03-28T04:12:14.415Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:14.425Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2023-03-28T04:12:14.432Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:14.434Z zigbee-herdsman:deconz:driver query aps data confirm
2023-03-28T04:12:14.437Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 250
2023-03-28T04:12:14.449Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x9cdb request id: 25 confirm status: 0
2023-03-28T04:12:14.451Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:14.454Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 6
2023-03-28T04:12:14.457Z zigbee-herdsman:deconz:adapter false, true, false
2023-03-28T04:12:14.457Z zigbee-herdsman:deconz:adapter resolve request
2023-03-28T04:12:18.281Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 251
2023-03-28T04:12:18.297Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:12:18.301Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:28.281Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 252
2023-03-28T04:12:28.293Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:12:28.295Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:38.285Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 253
2023-03-28T04:12:38.295Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:12:38.298Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.077Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2023-03-28T04:12:44.079Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.081Z zigbee-herdsman:deconz:driver query aps data indication
2023-03-28T04:12:44.086Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 254
2023-03-28T04:12:44.097Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 254 srcAddr: 0x9cdb destAddr: 0x0 profile id: 0x104 cluster id: 0xfc7d lqi: 255
2023-03-28T04:12:44.099Z zigbee-herdsman:deconz:frameParser response payload: 12,124,17,7,10,4,0,33,0,0
2023-03-28T04:12:44.104Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":7,"manufacturerCode":4476,"commandIdentifier":10},"Payload":[{"attrId":4,"dataType":33,"attrData":0}],"Command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}},"address":40155,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
Zigbee2MQTT:debug 2023-03-28 15:12:44: Received Zigbee message from '0x9035eafffe1a1de3', type 'attributeReport', cluster 'manuSpecificIkeaAirPurifier', data '{"particulateMatter25Measurement":0}' from endpoint 1 with groupID null
2023-03-28T04:12:44.116Z zigbee-herdsman:controller:endpoint DefaultResponse 0x9035eafffe1a1de3/1 64637(10, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2023-03-28T04:12:44.118Z zigbee-herdsman:deconz:adapter no response expected
2023-03-28T04:12:44.120Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
Zigbee2MQTT:info  2023-03-28 15:12:44: MQTT publish: topic 'zigbee2mqtt/0x9035eafffe1a1de3', payload '{"air_quality":"excellent","child_lock":"UNLOCK","fan_mode":"auto","fan_speed":4,"fan_state":"ON","led_enable":true,"linkquality":255,"pm25":0,"replace_filter":false,"update":{"installed_version":69633,"latest_version":69633,"state":"idle"},"update_available":false}'
2023-03-28T04:12:44.151Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x9cdb EP:1 SeqNr. 1 request id: 26
2023-03-28T04:12:44.165Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 26 status: 0
2023-03-28T04:12:44.170Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.173Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2023-03-28T04:12:44.179Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.182Z zigbee-herdsman:deconz:driver query aps data confirm
2023-03-28T04:12:44.183Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 2
2023-03-28T04:12:44.192Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x9cdb request id: 26 confirm status: 0
2023-03-28T04:12:44.192Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.192Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 7
2023-03-28T04:12:44.192Z zigbee-herdsman:deconz:adapter false, true, false
2023-03-28T04:12:44.193Z zigbee-herdsman:deconz:adapter resolve request
2023-03-28T04:12:44.221Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10101010
2023-03-28T04:12:44.223Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 1 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.225Z zigbee-herdsman:deconz:driver query aps data indication
2023-03-28T04:12:44.227Z zigbee-herdsman:deconz:driver DATA_INDICATION - sending read data request - SeqNr. 3
2023-03-28T04:12:44.238Z zigbee-herdsman:deconz:frameParser DATA_INDICATION RESPONSE - seqNr. 3 srcAddr: 0x9cdb destAddr: 0x0 profile id: 0x104 cluster id: 0xfc7d lqi: 255
2023-03-28T04:12:44.241Z zigbee-herdsman:deconz:frameParser response payload: 12,124,17,8,10,7,0,32,20
2023-03-28T04:12:44.246Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":true,"direction":1,"disableDefaultResponse":false,"reservedBits":0},"transactionSequenceNumber":8,"manufacturerCode":4476,"commandIdentifier":10},"Payload":[{"attrId":7,"dataType":32,"attrData":20}],"Command":{"ID":10,"name":"report","parameters":[{"name":"attrId","type":33},{"name":"dataType","type":32},{"name":"attrData","type":1000}]}},"address":40155,"endpoint":1,"linkquality":255,"groupID":null,"wasBroadcast":false,"destinationEndpoint":1}'
Zigbee2MQTT:debug 2023-03-28 15:12:44: Received Zigbee message from '0x9035eafffe1a1de3', type 'attributeReport', cluster 'manuSpecificIkeaAirPurifier', data '{"fanSpeed":20}' from endpoint 1 with groupID null
2023-03-28T04:12:44.257Z zigbee-herdsman:controller:endpoint DefaultResponse 0x9035eafffe1a1de3/1 64637(10, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2023-03-28T04:12:44.261Z zigbee-herdsman:deconz:adapter no response expected
2023-03-28T04:12:44.263Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
Zigbee2MQTT:info  2023-03-28 15:12:44: MQTT publish: topic 'zigbee2mqtt/0x9035eafffe1a1de3', payload '{"air_quality":"excellent","child_lock":"UNLOCK","fan_mode":"auto","fan_speed":3,"fan_state":"ON","led_enable":true,"linkquality":255,"pm25":0,"replace_filter":false,"update":{"installed_version":69633,"latest_version":69633,"state":"idle"},"update_available":false}'
2023-03-28T04:12:44.297Z zigbee-herdsman:deconz:driver DATA_REQUEST - destAddr: 0x9cdb EP:1 SeqNr. 4 request id: 27
2023-03-28T04:12:44.315Z zigbee-herdsman:deconz:frameParser DATA_REQUEST RESPONSE - request id: 27 status: 0
2023-03-28T04:12:44.315Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.322Z zigbee-herdsman:deconz:frameParser DEVICE_STATE changed: 10100110
2023-03-28T04:12:44.322Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 1 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.340Z zigbee-herdsman:deconz:driver query aps data confirm
2023-03-28T04:12:44.345Z zigbee-herdsman:deconz:driver DATA_CONFIRM - sending data state request - SeqNr. 5
2023-03-28T04:12:44.352Z zigbee-herdsman:deconz:frameParser DATA_CONFIRM RESPONSE - destAddr: 0x9cdb request id: 27 confirm status: 0
2023-03-28T04:12:44.352Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:44.353Z zigbee-herdsman:deconz:adapter sendZclFrameToEndpoint - message send with transSeq Nr.: 8
2023-03-28T04:12:44.353Z zigbee-herdsman:deconz:adapter false, true, false
2023-03-28T04:12:44.353Z zigbee-herdsman:deconz:adapter resolve request
2023-03-28T04:12:48.283Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 6
2023-03-28T04:12:48.298Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:12:48.300Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:12:58.287Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 7
2023-03-28T04:12:58.297Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:12:58.297Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1
2023-03-28T04:13:08.285Z zigbee-herdsman:deconz:driver send read device state from queue. seqNr: 8
2023-03-28T04:13:08.297Z zigbee-herdsman:deconz:frameParser device state: 10100010
2023-03-28T04:13:08.300Z zigbee-herdsman:deconz:driver networkstate: 2 apsDataConfirm: 0 apsDataIndication: 0 configChanged: 0 apsRequestFreeSlots: 1

[automaker]

This is active, I can see the gui, its just not populated with data, even though I have at least two devices working via MQTT

[nickrout]

Perhaps try to clear your cache? (ctrl-f5).

[tom_l]

There’s another topic here with some advice at the end: Zigbee2mqtt not showing devices

[automaker]

good thought, but didnt work

[nickrout]

What browser?

Just to eliminate browser issues - try

• incognito window
• a different browser
• a different computer and/or OS if you have such things.

[automaker]

I had added a username and password for Z2M to auth against Mosquitto (added the same user and pass in Mosquitto) but just noticed the system has changed it to user: addons with a pass. I added that same user and pass (addons) to the MQTT server but no luck.
I also noticed I dont actually have an “addons” user under people/users. Is this an issue?

/config/zigbee2mqtt/configuration.yaml

homeassistant: true
mqtt:
  server: mqtt://core-mosquitto:1883
  user: addons
  password: aifaaqu0einahS5oPothxxxxxxxio6UKiephaileeN8oixxxxxxphah
serial:
  port: tcp://192.168.10.85:20108
  adapter: deconz
frontend:
  port: 8099
devices:
  '0x3425b4fffea07b36':
    friendly_name: '0x3425b4fffea07b36'
  '0x9035eafffe1a1de3':
    friendly_name: '0x9035eafffe1a1de3'

[nickrout]

The best way to use the mqtt addon is to create a user and password for HA in here

and then use that user and password in whatever is trying to connect to mqtt.

[automaker]

Just tried linux - Brave, chromium, firefox including incognito windows on two different Linux machines + Edge on a virt windows machine and they are all the same … not showing anything populated in the GUI.

[automaker]

I added a specific user to the users area and added it to Z2M but it didnt work. I checked my HA log and found this, which led me to find my root dir is full. Just dealing with that now and will report back. With a bit of luck, this will be the solution. Thank you both for your help so far.

Logger: aiohttp.server
Source: components/websocket_api/http.py:213
First occurred: 4:02:22 PM (1 occurrences)
Last logged: 4:02:22 PM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 67, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 234, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/http.py", line 53, in get
    return await WebSocketHandler(request.app["hass"], request).async_handle()
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/http.py", line 213, in async_handle
    await wsock.prepare(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_ws.py", line 138, in prepare
    payload_writer = await super().prepare(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 421, in prepare
    return await self._start(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 429, in _start
    await self._write_headers()
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py", line 502, in _write_headers
    await writer.write_headers(status_line, self._headers)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py", line 130, in write_headers
    self._write(buf)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py", line 75, in _write
    raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport

[nickrout]

That would stuff things up!

[automaker]

ok, so after much googling, the previous error is not related to disk space but rather something else that everyone seems to ignore. The /dev/root issue of 100% is also not an issue as its not actually a disk that we need to worry about.

I have made some progress in that I have a Nabu Casa account and if I use that URL in the browser rather than 192.168 etc, the web gui works.

If someone can explain why it works on the NC url and not on the local one, I would be grateful.

TIA

[tom_l]

Did i just find a bug in HA or PiOS when i try to access settings in HA

Make sure that external_url is configured in Home Assistant. See Setup basic information - Home Assistant Internal: http://<ip_address>:8123 External: Nabu Casa remote URL

I can definitely see devices in the dashboard using either my internal or external URL.

[automaker]

I did this from the GUI and rebooted, still no luck
I am sure it is going to be something simple, will persevere until I find the cause. Let me know if you have any other ideas.

Are your settings in the GUI or yaml?

[automaker]

Just tried the internal and external URL settings in YAML and no difference.

[ASCsk (ASC)]

I was having this problem and all I needed to do was to reconfigure the MQTT integration, I added the HA user/pw that I defined for the MQTT broker and voilà, the devices started appearing. The user was set as homeassistant and some random pw. Don’t really know why, mb default?