live4soccer7

Thanks! Well that may just be it. I installed the one by spants probably 2 yrs ago and then haven't started it in the last year until a few days ago to start using it for some functionality that would save me some sleep by autostarting a device that I typically would have to wake up for each day during the colder months.

I did that and i was able to create a flow that actually worked, simply input in to debug. My old flows are not there anymore (kept a backup). It seems that nodered created another flow.json even when I changed it to flows.json. I have also taken a screenshot of the import area and what it does.

Here is a screenshot of the files I have in my NodeRed folder BTW, anyone know what forum platform this is, I like it?

Thanks. Any idea on what I can do to get this thing back up and running? I loved node red and used it to interface with all of my devices before rendering information to a UI. The flow of my setup: Hardware ---> MQTT ---> NodeRed ---> OpenHab Should I nuke the docker and start from scratch? Can I save the flow*.json files to keep my flows?

I just decided to open up nodered again on my unraid install. I had used it for a few home automation things in my previous home and I moved about a year ago and haven't opened it back up because I just haven't had time to get anything setup hardware wise. I decided to try something today and opened up nodered and it autoupdated upon starting and now it seems like nothing works. The import option just shows a black bar with no options for importing. My previously imported libraries are gone When I hit deploy it says that it has deployed, but then I go to inject into a debug msg.payload and it says the node is not deployed. Clearly, something has gone completely wrong here. Any ideas/input? I really don't want to lose my work flows/nodes that I've created and hopefully this won't be an issue in the future as I like things to be stable so I can count on them to work all the time.

I'm trying to run a bash post processing script with SAB (docker) and $1 variable that is suppose to be set up with SAB does not return anything, not even a blank space. It should return the final directory path of the download. I have confirmed this by simply doing an echo of $1 in the script. The script runs, but does nothing really because of the invalid path. I'm guessing this is because of the alias path that has to be created for the docker to have access to a specific place on the unraid machine and the script is running globally and sab just watches for the outputs on the script rather than it running within SAB. Perhaps I'm way off, but it just seems it has something to do with this. Any ideas?

Thanks! I've been having a lot of fun with node-red. It has been great and very easy to keep track of things. It's easy to get lost in openhab between all the different things ones needs to create if you don't do it very often. Has anyone tried mi-light in node-red? I gotten the flow from here: http://flows.nodered.org/flow/b2cb3bdc5a81ac881d4b I'm having a tough time getting it to work. I've correctly passed the mqtt topics through and it parses them, however the second function simply returns 0000 when outputting to debug. I do have the milights being controlled through openhab, but would like to be able to start with all functionality in mqtt/nodered, if possible. I hope you don't mind me conversing about the dockers like this in here. If you do, please let me know and I can start a thread. Maybe one of you guys would know why 0000 is being returned. Command: "on" and value "6" is being passed as shown by the debugger. I can replace the hex string with something else and it will show up for that particular case. var commandCode = []; switch ( msg.payload.command ) { case "on": commandCode = [[0x42,0x45,0x47,0x49,0x4B][msg.payload.value],0x00]; break; case "off": commandCode = [[0x41,0x46,0x48,0x4A,0x4C][msg.payload.value],0x00]; break; case "hue": //0-255 var hex = msg.payload.value.toString(16); hex = (hex.length < 2) ? '0x0'+hex : '0x'+hex; commandCode = [0x40,hex]; break; case "whiteMode": commandCode = [[0xC2,0xC5,0xC7,0xC9,0xCB][msg.payload.value],0x00]; break; case "brightness": //1-100 => 2 to 27 var hex = Math.max(2,(Math.ceil((msg.payload.value-1)/99*25))+2).toString(16); hex = (hex.length < 2) ? '0x0'+hex : '0x'+hex; commandCode= [0x4E,hex]; break; case "discoMode": commandCode = [0x4D,0x00]; break; case "discoSpeedUp": commandCode = [0x44,0x00]; break; case "discoSpeedDown": commandCode = [0x43,0x00]; break; } //commandCode[2]=0x55; msg.payload = new Buffer(commandCode); return msg; any ideas? Is it converting it in the output window and actually passing the correct values to msg or is it simply not liking the input for var? That's about all I can think of since the values that are being passed are actually corresponding the the correct case.

Are you guys that are using node red doing something like this: sensors --> mqtt/mosquitto --> node-red --> openhab I'm quite curious as I'm doing most of this as a hobby and find it quite interesting. I've gotten a few individual things hooked up to open hab through mi-light and philips bulbs, but am wanting to expand to mqtt and find a good set of items to integrate with it and it seems node-red has a really good way of working with those items.

I'm still not able to connect the mqtt/mosquitto. I've got the docker running, installed MQTT.fx on another computer on the network that I use all the time to control the unraid server. MQTT docker is set to bridge, left the guid/puid values in variables to what they are when they come with the docker 99/100. I even tried to create a user/password in the password file. I have tried leaving the docker install 100% alone as far as conf. files etc... and then connecting and still nothing. I'm defining my broker as 192.168.1.150, port 1883, tried with and without user/pass. It simply says Mqttexception: Unable to connect to server Here is the log file from MQTT.fx org.eclipse.paho.client.mqttv3.MqttException: Unable to connect to server at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:79) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:590) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66] Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_66] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_66] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_66] at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] ... 2 more 2016-02-08 14:38:08,743 INFO --- ScriptsController : Clear console. 2016-02-08 14:38:08,744 ERROR --- BrokerConnectService : MqttException: Unable to connect to server 2016-02-08 14:39:00,964 INFO --- BrokerConnectorController : onConnect 2016-02-08 14:39:00,967 INFO --- ScriptsController : Clear console. 2016-02-08 14:39:00,969 INFO --- MqttFX ClientModel : MqttClient with ID MQTT_FX_Client assigned. 2016-02-08 14:39:00,998 ERROR --- MqttFX ClientModel : Error when connecting org.eclipse.paho.client.mqttv3.MqttException: Unable to connect to server at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:79) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:590) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_66] Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_66] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_66] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_66] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_66] at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70) ~[org.eclipse.paho.client.mqttv3-1.0.2.jar:?] ... 2 more 2016-02-08 14:39:01,026 INFO --- ScriptsController : Clear console. 2016-02-08 14:39:01,027 ERROR --- BrokerConnectService : MqttException: Unable to connect to server I'm obviously still missing something and I'm sure it is extremely simple. I was able to get connected. I had the password file incorrect. So it seems that you must have a user/pass in order to connect. Thanks for the great docker!

Thanks. I'm definitely reading through that thread now.

I have adjusted the .conf file a little and I now have better results when reading it. root@4ca7b725ceaa:/# mosquitto -c /config/mosquitto.conf 1454745023: mosquitto version 1.4.7 (build date Tue, 22 Dec 2015 12:47:28 +0000) starting 1454745023: Config loaded from /config/mosquitto.conf. 1454745023: Opening websockets listen socket on port 9001. I still am unable to run a mosquitto_sub command or really anything besides the mosquitto -c command. Any ideas? Is there something in the .conf file I'm missing? I simply get a command not found return.

Quick question. I've install mqtt and when I run something like like this: mosquitto_sub -d -t hello/world or mosquitto_pub bash: mosquitto_sub: command not found I am in the docker container. I am able to run the following with good results mosquitto -c /config/mosquitto.conf Warning: Default listener port specified multiple times. Only the latest will be used. 1454733095: mosquitto version 1.4.7 (build date Tue, 22 Dec 2015 12:47:28 +0000) starting 1454733095: Config loaded from /config/mosquitto.conf. 1454733095: Opening websockets listen socket on port 9001. What am I missing? I have also navigated to usr/bin/ and was not able to locate the command there. Is the location different from that? I am simply trying to make sure everything is up and running by using this command so I can move on to integrating within openhab.

Yes, I think this would be a good option. I believe all of my dockers were hanging at: waiting for "apt" this could take a while This is what I saw when I viewed the log. Perhaps they were not able to get through to the destination where it checks and therefore none of the linuxserver.io dockers would start. I usually am not a huge proponent of updating software all the time either unless there is a real good reason to do so. I think at the least, if that is what was causing the hang for about a day then there should be a timeout so that it will start up without having to contact a site for checking updates or whatever it does.

I have a strange issue with linuxserver's dockers. Starting a couple days back I can no longer access via webgui. I simply get "no server found" in the browser when attempting. It is only linuxserver dockers though. I have all other dockers that aren't linux server running and I can access them (several different creators). I have rebooted router, unraid, access point, computer i'm accessing from etc... I have started just one docker before anything else and still can't access it and it is only the linuxserver dockers. I have not updated the unraid version, have not updated the dockers, have not added any dockers or VMs etc.... The system is exactly the same as it was a few days ago minus having a new drive added to the array and pre-clear was running for the last 4-5 days to get the disk prepared. Other than that nothing has changed on the server. Any ideas? Let me know if I can provide something that may help determine what is going on. It actually somewhat appears the linuxserver.io dockers aren't even starting up. It says they are started (the green play arrow), however I don't think they are starting all the way. Edit: A few hours have gone by since this post and now they have all started up. Any idea why this would be?