mqtt explorer crashes when clicking on host name, search box, settings, ... #710
Comments
|
Any update? For an add-on in hassio running on a Pi4 really not a good version or implementation. Buggy and not working.... Installed the windows version on my laptop and connected to the mqtt broker without any issue. Unfortunately I don't have always access to my windows based laptop and prefer to use it from within my Homeassistant app running on my iPhone or iPad... |
|
To narrow down the problem, connecting with a remote browser from my laptop I can launch and use the MQTT Explorer... However when using my iPad with the Homeassistant app or Google Chrome or Safari the app doesn't show any data and crashes when clicking left and right.... |
|
@wbruninx : the author has not been updating since some year.. keep that in mind if you expect a reply :) |
Thank you for the update. So probably no update to expect and as mentioned in the add-on documentation under the section troubleshooting : no workaround for iOS/safari issue... |
|
As the addon author, I must mention that the addon isn't using an official version of MQTTExplorer. The official one doesn't work in browsers but does use webviews. However this does also relate to methods used to append data and react to changes in real time such as required in #60. |
|
Hi, @wbruninx I would invite you to try MQTTX (https://mqttx.app/), an open-source MQTT client. If you encounter any problems with MQTTX, please raise the issue at https://github.com/emqx/MQTTX/issues. 😁 |
Don't see any data. Explorer crashes when clicking in interface on hostname or changing settings... Fresh install in Homeassistant running on a PI4 with latest version HASS OS.
Oooooops!
I hoped that you would never see this window, but MQTT-Explorer had an unexpected error.
cleanup@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/3.bundle.js:25338:38
@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15158:251
@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15274:468
Ki@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15158:174
Mi@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15165:223
Sj@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15197:75
Sj@[native code]
@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15274:468
Jj@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15192:372
yj@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15183:378
yj@[native code]
@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15067:116
@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15274:468
fg@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15067:63
gg@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15066:498
Ga@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15231:97
gd@http:https://192.168.0.140:8123/api/hassio_ingress/fbpjgxsvFPAzVCPOz-Dz4RyTFGyaXSOV0mz9O620UUY/vendors.bundle.js:15012:373
gd@[native code]
Please report this issue with a short description of what happened to https://github.com/thomasnordquist/MQTT-Explorer/issues
The text was updated successfully, but these errors were encountered: