10 hours ago, spants said:

Maybe go into appdata folder and

chmod 777 nodered

 

Or whatever the directory name is.... Maybe not good on a site that has internet connected!

This is what i tried:

chmod 777 /mnt/user/appdata/nodered

Still get this error.

I'm wondering if its a palette issue, as NodeRed itself can save flows and new palette info to the directory!

Edited April 13, 20206 yr by bdydrp

There is an issue with MQTT docker. After the server is restarted, MQTT can't read the db file. You need to manually delete mosquitto.db and then it starts ok.

 

Maybe a variable could be added to docker so you have option to delete file on docker start.

I started running spants/mqtt as a broker for homeassistant/home-assistant and openzwave/ozwdaemon to communication between my home automation system and z-wave devices. I run all dockers on same network custom br0 where each has their own IP.

 

From the start I have struggled with clients disconnecting from mqtt quite frequently. I'm not sure how to troubleshoot this as I am not familiar with how the protocol works. I'm looking for suggestions on how to troubleshoot these disconnects.

 

What I have tried with no success is setting up a user for each client. I thought that there might be some conflict with multiple anonymous clients but I have not noticed any improvements.

 

I have attached a log from the docker where I filter on disconnects. I have also converted time from epoc to human readable.

# docker logs MQTT --tail 200000 2>&1 | grep disconnect
2020-05-22 14:52:35: Client 5927cacb-f79d-4041-8f19-4f7bd0264b08 has exceeded timeout, disconnecting.
2020-05-22 14:52:35: Socket error on client 5927cacb-f79d-4041-8f19-4f7bd0264b08, disconnecting.
2020-05-22 14:52:50: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-22 14:52:50: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.
2020-05-22 15:17:38: Client qt-openzwave-1 disconnected.
2020-05-22 15:17:38: Socket error on client qt-openzwave-1, disconnecting.
2020-05-22 15:18:16: Client fb0ab425-2281-40f1-820b-80d55d414fb1 has exceeded timeout, disconnecting.
2020-05-22 15:18:16: Socket error on client fb0ab425-2281-40f1-820b-80d55d414fb1, disconnecting.
2020-05-22 15:18:29: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-22 15:18:29: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.
2020-05-22 19:21:12: Client qt-openzwave-1 disconnected.
2020-05-22 19:21:12: Socket error on client qt-openzwave-1, disconnecting.
2020-05-22 19:21:51: Client ff1f7321-c154-438a-aeab-f58a3d9a582d has exceeded timeout, disconnecting.
2020-05-22 19:21:51: Socket error on client ff1f7321-c154-438a-aeab-f58a3d9a582d, disconnecting.
2020-05-22 19:22:12: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-22 19:22:12: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.
2020-05-23 04:55:21: Client 54b9a167-0813-4422-a97e-8768f5deeda1 has exceeded timeout, disconnecting.
2020-05-23 04:55:21: Socket error on client 54b9a167-0813-4422-a97e-8768f5deeda1, disconnecting.
2020-05-23 04:55:23: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-23 04:55:23: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.
2020-05-23 04:55:49: Client qt-openzwave-1 has exceeded timeout, disconnecting.
2020-05-23 04:55:49: Socket error on client qt-openzwave-1, disconnecting.
2020-05-23 06:30:29: Client qt-openzwave-1 disconnected.
2020-05-23 06:30:29: Socket error on client qt-openzwave-1, disconnecting.
2020-05-23 06:31:29: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-23 06:31:29: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.
2020-05-23 06:31:48: Client 465dcd1c-ccec-4b60-a9c5-a4aeb3a3baab has exceeded timeout, disconnecting.
2020-05-23 06:31:48: Socket error on client 465dcd1c-ccec-4b60-a9c5-a4aeb3a3baab, disconnecting.
2020-05-23 09:39:31: Client qt-openzwave-1 disconnected.
2020-05-23 09:39:31: Socket error on client qt-openzwave-1, disconnecting.
2020-05-23 09:40:24: Socket error on client 7bd74f74-0933-459c-9e95-26aa488f32f3, disconnecting.
2020-05-23 09:40:32: Client mqtt_9c73a1f4.c7455 has exceeded timeout, disconnecting.
2020-05-23 09:40:32: Socket error on client mqtt_9c73a1f4.c7455, disconnecting.

I have also attached log from ozwdaemon at one instance where it gets disconnected. This corresponds to the latest disconnect at 09.39 in mqtt log:

[20200523 11:39:30.491 CEST] [qt.mqtt.connection] [debug]: bool QMqttConnection::sendControlPingRequest()
[20200523 11:39:30.491 CEST] [qt.mqtt.connection.verbose] [debug]: bool QMqttConnection::writePacketToTransport(const QMqttControlPacket&)  DataSize: 2
[20200523 11:39:30.511 CEST] [qt.mqtt.connection] [debug]: void QMqttConnection::transportError(QAbstractSocket::SocketError) QAbstractSocket::RemoteHostClosedError
[20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [debug]: MQTT State Change 0
[20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [warning]: Exiting on Failure
[20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [debug]: Disconnnected
[20200523 11:39:30.511 CEST] [ozw.mqtt.publisher] [warning]: Broker Error 256

 

Is any one using node-red-contrib-nbrowser? If I try to use it my docker image crashes. Never mind went in a different direction.

Edited June 4, 20206 yr by Ultra-Humanite

Regarding OctoPrint - is there a command I can put in the Restart Server command setting?

Has anyone setup MQTT to work with LE docker? I've tried to find some how to's with no luck.

2 hours ago, H2O_King89 said:

Has anyone setup MQTT to work with LE docker? I've tried to find some how to's with no luck.

I made a post about how to accomplish this here: https://skylar.tech/installing-mqtt-under-docker/

 

I also have various other posts that utilize MQTT that you may find worth checking out.

I made a post about how to accomplish this here: https://skylar.tech/installing-mqtt-under-docker/
 
I also have various other posts that utilize MQTT that you may find worth checking out.

I don't see anything in the blog about using the let's encrypt docker to reverse proxy MQTT?

Sent from my Pixel 4 XL using Tapatalk

2 hours ago, H2O_King89 said:

I don't see anything in the blog about using the let's encrypt docker to reverse proxy MQTT?

Sent from my Pixel 4 XL using Tapatalk
 

Ah sorry I thought I had a section about proxying with NGINX.

 

So Lets Encrypt is just used to give the NGINX instance an SSL certificate. What is actually doing the fun proxy stuff is NGINX. A quick google search of "Proxy MQTT websocket with NGINX" reveals this helpful link:
https://community.openhab.org/t/reverse-proxy-mqtt-through-nginx/36026/2

 

I actually didn't like the idea of exposing my MQTT instance over the internet so I instead setup a VPN on my network that I set devices outside my network to connect to. This gives them secure access to my network from outside without the worry of securing my MQTT instance for the public internet.

Ah sorry I thought I had a section about proxying with NGINX.
 
So Lets Encrypt is just used to give the NGINX instance an SSL certificate. What is actually doing the fun proxy stuff is NGINX. A quick google search of "Proxy MQTT websocket with NGINX" reveals this helpful link:
https://community.openhab.org/t/reverse-proxy-mqtt-through-nginx/36026/2
 
I actually didn't like the idea of exposing my MQTT instance over the internet so I instead setup a VPN on my network that I set devices outside my network to connect to. This gives them secure access to my network from outside without the worry of securing my MQTT instance for the public internet.

I found that article and tried that config and couldn't get node-red to connect. I did use port 9001 that shows in our config file.

What I'm trying to accomplish is make a public available topic others can sub too. I'm a volunteer firefighter and have a paging system setup with a topic called "Fire-Page" and will publish a message with the fire department name.

This will let any firefighter setup hass.io with node-red and do what they want with it.

Here is what I've done with mine.

Sent from my Pixel 4 XL using Tapatalk

I get this now when I check for updates on my node red docker..

 

Is there a new docker for this or something?

 

Jim

27 minutes ago, jbuszkie said:

I get this now when I check for updates on my node red docker..

 

Is there a new docker for this or something?

 

Jim

Is your repository set to nodered/node-red? and docker hub to https://hub.docker.com/r/nodered/node-red-docker/

 

Edited October 2, 20205 yr by spants

5 minutes ago, spants said:

Is your repository set to nodered/node-red? and docker hub to https://hub.docker.com/r/nodered/node-red-docker/

 

I have not changed it ever as far as I know..  I'll check..

 

No...  It's set to that..

wait..  It's a little different..

Ok..  that was it..  It must have changed from when I first installed it.  I changed the repo and now it looks ok...

 

Thanks for the help.

Ok..  that was it..  It must have changed from when I first installed it.  I changed the repo and now it looks ok...

 
Thanks for the help.

I think the plugin fixed common things said there was a template update a while back

Sent from my Pixel 4 XL using Tapatalk

1 minute ago, H2O_King89 said:

I think the plugin fixed common things said there was a template update a while back

Sent from my Pixel 4 XL using Tapatalk
 

huh..  either I dismissed that warning..  or I never got it! :-)

Had the same issue just recently too.  Not sure what caused it as i just updated it a couple weeks back and it was fine.

The node red team changed their URL..... I changed the template but existing users of a template do not get automatically changed by community applications app to avoid overriding existing parameters

The node red team changed their URL..... I changed the template but existing users of a template do not get automatically changed by community applications app to avoid overriding existing parameters

What's the new URL?

Sent from my Pixel 4 XL using Tapatalk

My MQTT log file is huge and growing..  What (and how) do you guys have your log stuff set to?  I never messed with this so it's probably set to the default.

 

This is what is in the conf file.

 

log_dest stderr
log_type all
connection_messages true
log_timestamp true

 

 

 

Another question..  My MQTT log file is > 4GB!  how do I get rid of it?

2 hours ago, jbuszkie said:

Another question..  My MQTT log file is > 4GB!  how do I get rid of it?

I don't have an answer to your question, but how did you get that output?

20 minutes ago, Phoenix Down said:

I don't have an answer to your question, but how did you get that output?