jerrytCould someone be so kind as to give an overview of the MQTT support, and provide a recommendation of a Homeseer MQTT broker ?
Thanks and yea, getting a write-up on the MQTT integration with HomeSeer would be great. The information and your experiences that you can provide / share, will no doubt help others regarding that platform. The more the better when it comes to alternative pool control/automation.Thanks for this incredibly well presented and thoroughly informative writeup, @MyAZPool ! I've got things working with HomeSeer, and when I get a bit of free time I'm going to put together a writeup on the MQTT integration for that automation platform - I'll likely link to this post since I doubt I'd be able to cover the initial setup as thoroughly.
Yea, there should have been a space between the L and h. When I copy/pasted some of the commands originally, the bb code/software munged up some of the commands with http in them. I thought I got them all fixed, but guess I missed one.Well I did not get far, get the error below on the CLI of the command in bold...
(5) # At the next command prompt, type or copy/paste: bash <(curl -sLhttps://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) #Tap the Enter/Return key.
[email protected]:~ $ bash <(curl -sLhttps://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
/dev/fd/63: line 1: syntax error near unexpected token `newline'
/dev/fd/63: line 1: `Usage: curl [options...] <url>'
SOLVED Correct command is;
bash <(curl -s https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
Remove the L
Open a CLI window and at the command prompt, type or copy/ pasteType or copy/paste: sudo nano /etc/rc.local #Tap the Enter/Return key. This command will open a GNU text editor on the RPi desktop.
(3) # Arrow down to between the “exit 0” and the “fi”, Type or copy/paste the following script within the GNU text editing field, between the “exit 0” and the “fi”:
These "npm start&" commands never run. I can open a terminal and run the commands manually and everything works fine, just not automatically on boot or login
I also tried;
sudo nano /home/pi/.bashrc
editing the file by adding;
echo Running at boot
this also does not run, but when I open a terminal it show errors on finding the directories; nodejs-poolController & nodejs-poolController-dashPanel
I am of the understanding from information gained from other sources (it was mentioned in the guide) that as long as you have a ScreenLogic protocol adapter (wired or wireless to your OCP), that it will allow for the correct RS485 connection to the IntelliTouch RS485 bus.I have an Intellitouch I5+3, it has communication to my network via the wireless Screenlogic wireless protocol adapter. I assume since it was not mentioned that this is not a substitute for running a hardwire.
Not necessarily. I know of a lot of people who "double up" connections to a COM Port. I am unaware of any negative effects of this practice. However, that being said, do I think it's the best operating practice? Not really sure. I can only say that I don't do it (that's just me. I use a COM Port Expansion Board). I don't really think you will have an issue doing so.I assume I will also have to buy the communication port expander board - i.e. you can't "double up" wires in an existing com port? I would like to keep the stock Screenlogic interface available for our pool service people, can these two co-exist?
I don't know the answer to that question. I did a bit of looking around on the internet (coz you piqued my curiosity ), but I don't want to give you any false information. Certainly, looks as though you can (see link below) Those two that I gave a "shout-out" to above can certainly answer this question along with @Katodude, @cmc0619 or @mcqwerty. They will see the tags here and I know that they can help you with more specific information regarding this question.And finally, is there any option to run these services in a docker rather than on a rasp pi? I have a pi, but I've migrated almost everything to docker containers running from my Synology NAS.
@PpriorAnd finally, is there any option to run these services in a docker rather than on a rasp pi? I have a pi, but I've migrated almost everything to docker containers running from my Synology NAS.
I've created a docker/kube configuration that will allow for hosting the api, the web client, and an ssh tunnel to a pool-connected-raspberrypigithub.com
Candurin@MyAZPool How practical is it to always run the RPi using virtual desktop? My dilemma is that I can run a Cat5e cable (to use as the physical RS485 COM connection) between the physical intellicenter and the RPi. However, I have two options:
1. Run a 100' Cat5e cable to the IC and keep the RPi in my home office where I can connect to it and also connect it to my network switch in my office. This way it is in the house and on my desk.
2. Keep the RPi in the garage and then run a smaller Cat5e (again, acting as the RS485 COM cable) from the RPi to the IC, about 20', and then connect the RPi to the AP router in my garage.
No matter what, I am hardwired LAN for networking. No Wifi needed.
Basically both do the same, but, how often do I need to make the physical connection to the RPi instead of using virtual desktop connection? I hope this makes sense? If I keep the Pi in the garage, it is less cables, but then I'll need the mini monitor and keyboard to actually access it outside of the virtual desktop. If I keep the Pi in my office, I can simply connect it to my existing keyboard and mouse and connect it to my existing monitor.
I hope that makes sense. I'm thinking option #1 may work out best in the long run and it it just the simple matter of running a longer Cat5e cable (RS485).
el duderinoThis is incredible. Thank you for taking the time to document all of this. I’m running 5.3 but am going to upgrade. This detailed play by play would have saved me a ton of time my first go round!