Hi all, I've got the pool controller package installed and running in one directory /home/pi/controller and the web clieent in another /home/pi/webclient. I'm trying to get the two started with PM2 which I've got installed. Saw How to get PM2 installed and running poolController on RPi or Linux further back.
Runnng the following from /home/pi/controller to start the pool controller: pm2 start dist/app.js --name "Ctl" --watch to start the pool controller. It does start as an app inside pm2 but I get no logs with pm2 monit, which is telling me it's constantly restarting? Not sure I'm I'm using pm2 right? I'm launching the webclient from its own folder with pm2 start dist/Server.js --name "Web" --watch -- my goal is to get PM2 to launch them both using the json file config option, but can't seem to get it working by hand. It should be mentioned that regular 'npm start' for both controller and web client in each it's own SSH session works nicely. Any help would be appreciated
pm2 start /home/pi/controller/dist/app.js /home/pi/controller/config.json --name CTL
You need to declare the Config path
In 5.x you needed to specify the config.json. That isn't needed in 6.x. More likely is that the watch is the problem. We write to the config.json, logs directory, and data directory. Try to start the pm2 process without the watch and see if it succeeds. If it does, than exclude the files/directories that get written to as it will trigger a restart.
@MaxVonEvil There is also a wiki page for PM2, but lots of ppl seem to have issue with the template. You can use it as a guide, however.
{
"apps": [
{
"name": "PoolController",
"script": "./dist/app.js",
"instances": 1,
"cwd": "/home/pi/controller"
},
{
"name": "PoolWebClient",
"script": "./dist/Server.js",
"instances": 1,
"cwd": "/home/pi/webclient"
}
]
}
"apps": [
{
"name": "PoolController",
"script": "./dist/app.js",
"instances": 1,
"cwd": "/home/pi/controller"
},
{
"name": "PoolWebClient",
"script": "./dist/Server.js",
"instances": 1,
"cwd": "/home/pi/webclient"
}
]
}
It seems to do what I want. My only concern is that the webclient instance does not seem to be providing any logs
pm2 monit is a bit funky. If you just try pm2 logs web it should show you the last 15 lines and give you the location of the full logs... eg:pi@poolcontroller:~ $ pm2 logs 2
[TAILING] Tailing last 15 lines for [2] process (change the value with --lines option)
/home/pi/.pm2/logs/poolController-webClient-error.log last 15 lines:
/home/pi/.pm2/logs/poolController-webClient-out.log last 15 lines:
2|poolCont | GET /app.747e1315.css
...
Or, if you use the monitor, you should be able to see logs if you load up the browser. There isn't anything really to log unless you make an actual connection to it.
@tagyoureit - Schweet, that did the trick! About the json example in the PM2 wiki, you're right, it was a bit much. I created mine from this example instead: https://futurestud.io/tutorials/pm2-use-npm-to-start-your-app
8|PoolWebC | "USN": "uuid:x.x.x.x::urn:schemas-upnp-org:device:PoolController:1",
8|PoolWebC | "CACHE-CONTROL": "max-age=1800",
8|PoolWebC | "DATE": "Tue, 15 Dec 2020 06:50:54 GMT",
8|PoolWebC | "SERVER": "node.js/12.20.0 UPnP/1.1 node-ssdp/4.0.0",
8|PoolWebC | "EXT": "",
8|PoolWebC | "LOCATION": "http://192.168.0.19:4200/device"
8|PoolWebC | }
8|PoolWebC | {
8|PoolWebC | "address": "x.x.x.x",
8|PoolWebC | "family": "IPv4",
8|PoolWebC | "port": 1900,
8|PoolWebC | "size": 334
8|PoolWebC | }
8|PoolWebC | IN SEARCH --- http://x.x.x:4200
8|PoolWebC | ✨ Built in 22.23s.
8|PoolWebC | "CACHE-CONTROL": "max-age=1800",
8|PoolWebC | "DATE": "Tue, 15 Dec 2020 06:50:54 GMT",
8|PoolWebC | "SERVER": "node.js/12.20.0 UPnP/1.1 node-ssdp/4.0.0",
8|PoolWebC | "EXT": "",
8|PoolWebC | "LOCATION": "http://192.168.0.19:4200/device"
8|PoolWebC | }
8|PoolWebC | {
8|PoolWebC | "address": "x.x.x.x",
8|PoolWebC | "family": "IPv4",
8|PoolWebC | "port": 1900,
8|PoolWebC | "size": 334
8|PoolWebC | }
8|PoolWebC | IN SEARCH --- http://x.x.x:4200
8|PoolWebC | ✨ Built in 22.23s.
Oh, you'll want to set the environment variable for production with webclient. That will avoid compiling the code every single time. The command from package.json is
env NODE_ENV=production node dist/Server.js. That will save about 22s on your startup time, not to mention CPU overhead.
@tagyoureit, btw not sure if this is within your code or it's @bsileo hubitat driver: I only have a Intelliflo VS pump and the Rpi. I do not own a chlorinator or any of the other pentair stuff. Still when I add the pool controller to Hubitat it adds a few other items as shown above
Specifically, I get two temperature sensors (air and solar) which returns no values, i.e. I'd like to get rid of them, however I'm not sure if they're coming from the HE driver or it's the poolcontroller telling the HE driver they exist?
(it should be said that all the RPM switches are deliberate. Those were 'Features' which I created in the PoolController web interface.
Lemme check the json files if there's anything interesting... brb
So, no - tbh I don't see any reference to the above two temperature items. I did check the pump manual (https://www.pentair.com/content/dam/extranet/pentair-pool/residential/manuals/pumps/intelliflo-vs/intelliflo-vs-pump-manual-english.pdf) and it appears there should be at least an air temperature sensor in the pump to enable "thermal-mode" (think it means run pump if near freezing). So at least the Air temp needs to be there. However I'm getting no data on the HE side from the driver? Is there a good way to test this value is being read correctly from the pump by the pool controller?
The pumps don't have any temp sensors that send data externally. You would need a separate air/water sensor but you don't have those with a virtual controller. Likely it's that hubitat shouldn't be creating those drivers. You can just delete/ignore them but I wouldn't expect to get any data with your current setup.
1 reply
Very cool. I've got BerryIO running in parallel for basic relay operations at the momet using Webcore to fire off Webrequests to the Pi to flip GPIO's on/off. Looks like relayEquipmentManager can do much more than that. If we later on can get upwards HE/ST integration with a native driver like Brad's driver for poolcontroler, that would be stellar!
6 replies
Hello, I have been trying to get the pi to talk to my intelliflo VSP with no luck. So I took my netbook with the JBTEK USB>RS485 out to the pump. Tried sending some commands but never seen anything back from the pump. Is there a command to check basic comm from the pump? I'm afraid my port on the pump is bad. I even went in and soldered the 2 wires to the board to eliminate the socket which didn't have the cap on and I'm sure water was in there, Any ideas greatly appreciated.
1 reply
Can someone look at this and see if I'm ok so far. I still can't talk to the pump. I did reverse the wires.
Actually there is but lets see what traffic you have going so far. Open an issue on the main page then lets do a capture replay and upload it. Let's see what njspc is sending out and if there is any response from items on the bus. Also, if you go to the address http://192.168.1.70:5150/messageManager.html you can watch the messages in real time. Click the icon on the upper far right hand corner of the message list and it will start showing all the messages on the RS485 bus.
From the messageManager you will be able to send a message to the pump to see if it gives a response.
If you open an issue I will walk you through sending this message and watching the reply.
Not sure how to open a issue. I did know that was a chlorinator message but I didn't know the first cmd to check comm. To be honest I only started playing with the pi a week or so ago. And not the best with Linux but I keep trying. There is a lot of stuff going on here. Till I get that first reply from the pump I'm in limbo.
1 reply
Hi all and happy new year in advance. Quick question; does anyone know of development being done with Home Assistant / MQTT integration for the 6.0 version of njsPC? I know of https://github.com/crsherman/nodejs-poolController-mqtt however that seems only to work with v5.
3 replies