[support] Spants - NodeRed, MQTT, Dashing, couchDB


433 posts in this topic Last Reply

Recommended Posts

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.

image.png.282578f4e719b434265847196dd06dac.png

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

Edited by bdydrp
Link to post
  • Replies 432
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Ya....just go into the Node-Red Docker template and change the repository as I said above and hit apply.......That's all I had to do. Love it

This is where I will be hosting some dockers that I find useful, built on a Phusion or Linuxserver base. Add to your templates if you wish.   https://github.com/spants/unraidtemplates/

Does anyone here know how to update node.js version in the Node-Red Docker Container?   docker exec -it NodeRed-OfficialDocker /bin/bash node -V The command above shows I'm on v

Posted Images

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.

Link to post
  • 1 month later...

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

 

Link to post
  • 2 weeks later...
  • 4 weeks later...
  • 1 month later...
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.

Link to post
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

Link to post
  • 1 month later...
Ok..  that was it..  It must have changed from when I first installed it.  I changed the repo and now it looks ok...
image.png.0662c66753ff5a52e3a16dd8ff564592.png
 
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

Link to post
  • 2 weeks later...

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

 

 

 

Link to post
  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.