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


Recommended Posts

  • 4 weeks later...

After a house fire and losing my unraid server (but not my offsite backup) I rebuilt the system.

I did change from a supervised version to the home assistant core version.

I have been able to use a lot of the docker containers, but MQTT has me perplexed.

I have read through almost all of this thread but can not find something similar.

 

MQTT is set as shown below. My server is at 192.168.1.90. I have created the password file. As suggested in other posts I made chmod the directory to 777, also chown to nobody:user.

 

There is nothing in my log file.

Home assistant allows me to add the MQTT integration but it does not discover my test devices.

Can someone point me in a direction.

Thanks.

 

Screenshot from 2021-06-08 13-02-29.jpg

Link to comment
  • 2 weeks later...

HI Guys i setup a Node Red Docker last night on main PC and added an additional port to get access for my Alexa Pluging with a local IP http://192.168.23.100:3456/ and i could get to page and login to authenticate alexa cookie

 

It keeps kept confirming with Alexa the cookie was saved.

But NR kept reporting i needed to do it again it would not connect?

 

 

 

 

 

 

 

 

Dell - Screenshot 24-06-2021 - 07.png

Dell - Screenshot 24-06-2021 - 03.png

Dell - Screenshot 24-06-2021 - 08.png

Dell - Screenshot 24-06-2021 - 09.png

Edited by OsoPolar
update
Link to comment
On 6/24/2021 at 9:24 AM, OsoPolar said:

HI Guys i setup a Node Red Docker last night on main PC and added an additional port to get access for my Alexa Pluging with a local IP http://192.168.23.100:3456/ and i could get to page and login to authenticate alexa cookie

 

It keeps kept confirming with Alexa the cookie was saved.

But NR kept reporting i needed to do it again it would not connect?

 

 

 

Please use a location for the cookie to be something like this:

 

/data/AlexaAuthFile.txt

 

It will then save it in your appdata directly and not the container.

Link to comment
  • 2 weeks later...

For ther NodeRedv2 Beta docker -= please change the repositiory tag to nodered/node-red-dev:v2.0.0-beta.2 to get the latest.

The NodeRed team have just changed their build process and it is not using the beta tag.

Link to comment
  • 4 weeks later...

As other people mentioned, the issues with permissions for MQTT stem from this line in run.sh:

chmod -R 666 /config

After i commented it out and applied 777 over MQTT folder in appdata, everything works.

Link to comment
1 hour ago, vyreks said:

As other people mentioned, the issues with permissions for MQTT stem from this line in run.sh:

chmod -R 666 /config

After i commented it out and applied 777 over MQTT folder in appdata, everything works.

Thanks!

Link to comment
  • 3 weeks later...

Will there be any updates to the MQTT version? I'm getting an error trying to configure the log timestamp format:

Error: Unknown configuration variable "log_timestamp_format".

 

It appears this variable applies to newer versions of the Mosquitto MQTT broker. Current version is now 2.0 on mosquitto.org.

 

Bob

 

Link to comment
16 hours ago, MrChip said:

Will there be any updates to the MQTT version? I'm getting an error trying to configure the log timestamp format:

Error: Unknown configuration variable "log_timestamp_format".

 

It appears this variable applies to newer versions of the Mosquitto MQTT broker. Current version is now 2.0 on mosquitto.org.

 

Bob

 

 

Hi Bob

 

I originally made this for my home automation system which works well and found no need to update (one of the later updates broke it). I will probably change to a Hive AMQP with MQTT plugin as it allows web based user management  - would that suit you too?

Link to comment
11 hours ago, spants said:

would that suit you too?

AMQP looks like overkill for my needs, but the MQTT plugin would be fine. It's not a big deal for me using the current version I guess. My only problem has been that date format, and I can work around that.

 

So, do what suits you. 😎

Link to comment

getting an npm error in the nodered docker. When i try to update a pallet it gives me the following:

 

Quote

-----------------------------------------------------------
2021-08-18T03:07:49.117Z Install : node-red-node-openweathermap 0.5.0

2021-08-18T03:05:55.088Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-node-openweathermap@0.5.0
2021-08-18T03:05:56.881Z [err] npm
2021-08-18T03:05:56.881Z [err]  WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
2021-08-18T03:05:57.142Z [err] npm
2021-08-18T03:05:57.142Z [err]  WARN deprecated har-validator@5.1.5: this library is no longer supported
2021-08-18T03:05:58.379Z [err] npm 
2021-08-18T03:05:58.379Z [err] WARN locking Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
2021-08-18T03:05:58.379Z [err] npm WARN locking  /data/.npm/_locks/staging-accc372ed0ccb0d8.lock failed [Error: EACCES: permission denied, open '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'] {
2021-08-18T03:05:58.379Z [err] npm WARN locking   errno: -13,
2021-08-18T03:05:58.379Z [err] npm WARN locking   code: 'EACCES',
2021-08-18T03:05:58.379Z [err] npm WARN locking   syscall: 'open',
2021-08-18T03:05:58.379Z [err] npm 
2021-08-18T03:05:58.380Z [err] WARN locking   path: '/data/.npm/_locks/staging-accc372ed0ccb0d8.lock'
2021-08-18T03:05:58.380Z [err] npm WARN locking }
2021-08-18T03:05:58.442Z [err] npm ERR!
2021-08-18T03:05:58.442Z [err]  code EACCES
2021-08-18T03:05:58.442Z [err] npm ERR! syscall open
2021-08-18T03:05:58.442Z [err] npm ERR! path /data/.npm/_locks/staging-accc372ed0ccb0d8.lock
2021-08-18T03:05:58.442Z [err] npm ERR! errno -13
2021-08-18T03:05:58.444Z [err] npm ERR! 
2021-08-18T03:05:58.444Z [err] npm ERR! Your cache folder contains root-owned files, due to a bug in
2021-08-18T03:05:58.444Z [err] npm ERR! previous versions of npm which has since been addressed.
2021-08-18T03:05:58.444Z [err] npm ERR! 
2021-08-18T03:05:58.444Z [err] npm ERR! To permanently fix this problem, please run:
2021-08-18T03:05:58.444Z [err] npm 
2021-08-18T03:05:58.444Z [err] ERR!   sudo chown -R 1000:1000 "/data/.npm"
2021-08-18T03:05:58.452Z [err] 
2021-08-18T03:05:58.452Z [err] npm ERR! A complete log of this run can be found in:
2021-08-18T03:05:58.452Z [err] npm ERR!     /data/.npm/_logs/2021-08-18T03_05_58_445Z-debug.log
2021-08-18T03:05:58.463Z rc=243

 I tried running the command in the console and just denies me.

 

Any suggetions?

Link to comment
On 8/18/2021 at 4:12 AM, Brandonb1987 said:

getting an npm error in the nodered docker. When i try to update a pallet it gives me the following:

 

 I tried running the command in the console and just denies me.

 

Any suggetions?

1) You can try it from the console in the nodered template (I think that you did)

2) or do it on the unraid console and substitute "/data" to "/mnt/user/appdata/nodered" or whatever you used....
Let me know how you get on

Link to comment
  • 2 weeks later...
  • 1 month later...
  • 2 weeks later...
14 hours ago, Mizz141 said:

So I've been using the Octoprint-Docker for quite some time now, but the docker wasn't updated in a long time, when will new updates be pushed to it? Octoprint version 1.7.0 has just been released.

 

I see that nunofgs hasnt updated his docker - I will try and use a different base docker - stay tuned!.
 

(I stopped using the docker after a long print was ruined by the backup routine tuning off the docker after 8 hours of printing!. My fault - I should have excluded that docker from switching off. I will investigate a solution) 

 

@Mizz141 *** I see that Mearman already has a template using the official docker - have you tried that? ***

Edited by spants
Link to comment
On 10/12/2021 at 11:31 AM, spants said:

 

@Mizz141 *** I see that Mearman already has a template using the official docker - have you tried that? ***

I know of Mearman's docker, however it doesn't contain the mjpg streamer which I need for webcam control, I have tried manual set-up but bricked the container way too many times for it to work. (or I'm just an idiot who can't figure out what settings to use, which probably is the more accurate term to describe my issues)

I also ran into the same issue when Backups shut-down the docker, you're not alone lol

Edited by Mizz141
Link to comment
On 10/13/2021 at 11:02 AM, Mizz141 said:

I know of Mearman's docker, however it doesn't contain the mjpg streamer which I need for webcam control, I have tried manual set-up but bricked the container way too many times for it to work. (or I'm just an idiot who can't figure out what settings to use, which probably is the more accurate term to describe my issues)

I also ran into the same issue when Backups shut-down the docker, you're not alone lol

 

see here: 

 

Link to comment

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.