Search results

If you have not updated dashPanel and have updated chrome. It will pop up block the the overlays. Update dashPanel.

Get a replay so I can see what njsPC is sending it and what it is responding with. Probably easier to submit an issue on the njsPC repo.

Ok so it should be purple. Are you connected to it via wifi? Also, make sure the pump address is correct for the setting you have in dashPanel. I too have an IntelliFlo3 so getting a replay would be grand for what njsPC is sending and what we are seeing from pump responses.

Do you have a purple/magenta light on the pump?

Yep the Building Automation V4 card was what I was referring to. The WhiteBox labs carrier board and EZO circuits round out all of the replacement for IXIAN.

Yes you do not want 64 bit. There is no advantage and a whole lot of warts.

If you decide to get rid of the IXIAN then you should get the BAS. It is a much more versatile card. Unfortunately, it does not have 4-20ma capability but you may no longer need it without the IXIAN. You won't miss anything without the IXIAN.

@Katodude I would copy the data directories for njsPC and REM. ~/nodejs-poolController/data ~/relayEquipmentManager/data If you have njsPC set up to regularly back up your files you will be able to find these files in ~/nodejs-poolController/backups I would first try to image a new SD card and...

You can monitor pressure using a less expensive 5v pressure transducer. While the atlas works fine it requires an I2c connection all the way to the filter.

IntelliCenter or any of the Hayward, Jandy, and others do not use modbus. They use a protocol on RS485 that has no corollary. NjsPC speaks this language.

Open an issue on the repo and include that capture.

Double check to make sure Pentair didn't just push an update at you.

No matter what you do the rpm range on the pump is 450-3450rpm and the flow rate is between 15-130gpm. njsPC should be able to handle this though. I need to have that replay to see where the reporting units are being reset.

I'll have a look. But if you could post a replay on the repo that would be great. It looks like it is trying to switch all the speeds to RPM when only the first one is RPM. In that instance the minimum speed is being applied because you cannot run the motor at 30rpm.

Which IC firmware version are you running?

@MyAZPool you know that chlorinator label is mis-aligned. I didn't want to say anything but it has been bugging me. :D

Please pull the latest dashPanel. Recent chrome releases seem to have triggered off some of our CSS class names.

This only works with the intake and return valves. But I have not tested it to see if it is broken since the early firmwares. It should shut down the pump that has an assigned pool circuit when switching from pool to spa.

You can also turn on valve delay. This is actually to ensure you don't run cold water into your warm spa but it works if you have goofy valve configurations as well. You will find this setting under the general settings.

Yes you can set up a workflow in the rule processor. It is simply a javascript that is called whenever the body event is emitted. If the isCovered flag is true get the chlorinator and set its output to whatever you want. You can even persist the old value to restore it when the isCovered flag...

The covered state is set by the card. It is simply a dry contact that when it switches will indicate in njsPC whether it is covered or not. I don't have one but to my knowledge it is fully supported in njsPC and will show as covered.

My recommendation is to use PM2. Honestly, it does a much better job at starting/stopping/ and monitoring processes. Is there a reason for the rc.local setup over PM2?

Open a discussion or an issue on the repository. I would like to see a replay when the pump should be running. This will tell us all about the communications.

Double check your ecosystem.config.js file and ensure njsPC is included in it. https://github.com/tagyoureit/nodejs-poolController/wiki/Automatically-start-at-boot---PM2-&-Systemd#pm2

Open a discussion or issue (either one will do) on the Github repo. We need to look at the logs to see what is failing to start on the njsPC side. We will have an easier time attaching images and responses over there to troubleshoot it.

Stop all the processes then start njsPC and dashPanel outside of pm2. Use npm start. This should run the typescript compiler.

No but run the following command if you are using nvm. If you are not I would suggest you use the node version manager (nvm). nvm alias default 18 This will update pm2 to use the node 18. Then restart.

Pooltone lighting is supported by njsPC but you will need to control them with an external relay. There are a number of home automation platforms including Homebridge that have been created by the community but I don't think anyone created a Control4 connector. However I do believe there is an...

In the future if you get a package-lock.json error just run the command git reset --hard

No worries. It seems daunting but think of it as texting your raspberry pi. The first thing we will do is install nvm. It is by far the easiest way to manage node versions on the pi. Step 1: Open a console on the pi. Step 2: Run the following commands one at a time by copying each line to...