spants Posted May 14, 2021 Author Share Posted May 14, 2021 maybe you can add a variable TZ to the template = America/Chicago (I haven't tried it) Quote Link to comment
carltonwb Posted June 8, 2021 Share Posted June 8, 2021 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. Quote Link to comment
spants Posted June 15, 2021 Author Share Posted June 15, 2021 Node Red v2 Beta Template added. Quote Link to comment
OsoPolar Posted June 24, 2021 Share Posted June 24, 2021 (edited) 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? Edited June 24, 2021 by OsoPolar update Quote Link to comment
spants Posted June 25, 2021 Author Share Posted June 25, 2021 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. Quote Link to comment
spants Posted July 4, 2021 Author Share Posted July 4, 2021 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. Quote Link to comment
vyreks Posted July 30, 2021 Share Posted July 30, 2021 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. Quote Link to comment
spants Posted July 30, 2021 Author Share Posted July 30, 2021 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! Quote Link to comment
MrChip Posted August 15, 2021 Share Posted August 15, 2021 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 Quote Link to comment
spants Posted August 16, 2021 Author Share Posted August 16, 2021 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? Quote Link to comment
MrChip Posted August 16, 2021 Share Posted August 16, 2021 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. 😎 Quote Link to comment
Brandonb1987 Posted August 18, 2021 Share Posted August 18, 2021 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 [email protected] 2021-08-18T03:05:56.881Z [err] npm 2021-08-18T03:05:56.881Z [err] WARN deprecated [email protected]: 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 [email protected]: 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? Quote Link to comment
spants Posted August 23, 2021 Author Share Posted August 23, 2021 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 Quote Link to comment
Brandonb1987 Posted September 1, 2021 Share Posted September 1, 2021 I tried again from the dockers console. No go. Tried it in the unraid console using chown -R 1000:1000 /mnt/user/Appdata/Nodered/.npm This fixed the issue and allowed me to update the palletes. 2 Quote Link to comment
FreeMan Posted October 2, 2021 Share Posted October 2, 2021 Sorry if this has been addressed - I was lazy and didn't read all 18 pages... Is anyone aware of this issue https://github.com/Koenkk/zigbee2mqtt/issues/8663 that is apparently a driver bug and requires a kernel update to fix? It seems to cause various ZigBee related issues, though not specifically related to MQTT... Quote Link to comment
Mizz141 Posted October 11, 2021 Share Posted October 11, 2021 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. Quote Link to comment
spants Posted October 12, 2021 Author Share Posted October 12, 2021 (edited) 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 October 12, 2021 by spants Quote Link to comment
Mizz141 Posted October 13, 2021 Share Posted October 13, 2021 (edited) 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 October 13, 2021 by Mizz141 Quote Link to comment
spants Posted October 15, 2021 Author Share Posted October 15, 2021 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: Quote Link to comment
lucidnx Posted November 15, 2021 Share Posted November 15, 2021 I want to re-open issue with database.. I am getting these errors: 1636996078: Error saving in-memory database, unable to open /config/data/mosquitto.db.new for writing. 1636996078: Error: Permission denied. I'v tried chmod 777, chown nobody:users, root:root... whatever... Can you help me please? Quote Link to comment
mikey6283 Posted November 21, 2021 Share Posted November 21, 2021 I have just downloaded Spants /MQTT again after mqtt and frigate container stoped and will not start. I have no idea why this is happened . I would be grateful for any advice on how to solve this. Tried the web etc without any luck. Quote Link to comment
lockedinbasement Posted December 7, 2021 Share Posted December 7, 2021 (edited) On 11/21/2021 at 5:42 PM, mikey6283 said: I have just downloaded Spants /MQTT again after mqtt and frigate container stoped and will not start. I have no idea why this is happened . I would be grateful for any advice on how to solve this. Tried the web etc without any luck. I am getting the following errors. I have run two or three methods of premission repairs with no luck. I would also appriciate any help. cp: can't create directory '/config/ca_certificates': No medium found cp: can't create directory '/config/certs': No medium found cp: can't create directory '/config/conf.d': No medium found cp: can't create '/config/mosquitto.conf': No medium found cp: can't create '/config/passwords.README': No medium found Edited December 7, 2021 by lockedinbasement Quote Link to comment
mikey6283 Posted December 24, 2021 Share Posted December 24, 2021 Hi Newbie here , just installed Node Red using the app, inserted the HA token and deployed, however i receive error in debug Invalid URL for Home Assistant Core, which gives the same ip address except for the port number. If i check if devices have been discovered they have been populated. Is there any way to correct i have removed the container and cleared any files but still same issue. Could it be because i am using HA Core ? Any advise would be appreciated. Quote Link to comment
killeriq Posted December 26, 2021 Share Posted December 26, 2021 On 8/18/2021 at 5: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? I was getting, but command wasnt working, so i removed NodeRed Docker. removed folder in Appdata and after installed it again, but now it doesnt want to even start and giving me this error: Quote > [email protected] start /usr/src/node-red > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" internal/fs/utils.js:332 throw err; ^ Error: EACCES: permission denied, copyfile '/usr/src/node-red/node_modules/node-red/settings.js' -> '/data/settings.js' at Object.copyFileSync (fs.js:2061:3) at copyFile (/usr/src/node-red/node_modules/fs-extra/lib/copy-sync/copy-sync.js:70:6) at onFile (/usr/src/node-red/node_modules/fs-extra/lib/copy-sync/copy-sync.js:56:25) at getStats (/usr/src/node-red/node_modules/fs-extra/lib/copy-sync/copy-sync.js:48:44) at handleFilterAndCopy (/usr/src/node-red/node_modules/fs-extra/lib/copy-sync/copy-sync.js:33:10) at Object.copySync (/usr/src/node-red/node_modules/fs-extra/lib/copy-sync/copy-sync.js:26:10) at Object.<anonymous> (/usr/src/node-red/node_modules/node-red/red.js:125:20) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) { errno: -13, syscall: 'copyfile', code: 'EACCES', path: '/usr/src/node-red/node_modules/node-red/settings.js', dest: '/data/settings.js' } npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"` npm ERR! Exit status 1 npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. Quote Link to comment
spants Posted December 28, 2021 Author Share Posted December 28, 2021 try setting the permissions of the appdata directory for node red chmod 755 /mnt/appdata/node-red (or whatever you have called it) Quote Link to comment
Recommended Posts
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.