Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:10

    tagyoureit on NixiePumps

    MQTT fixes Merge branch 'NixiePumps' of ht… (compare)

  • 01:24
    rstrouse commented #290
  • May 16 22:54
    556duckvader commented #293
  • May 16 21:30
    Tegguy commented #290
  • May 16 19:43
    rstrouse commented #290
  • May 16 12:05
    Tegguy commented #290
  • May 15 18:37

    rstrouse on master

    Added processing for RTS signal… (compare)

  • May 15 15:46
    556duckvader commented #293
  • May 15 01:33
    acronce commented #294
  • May 14 20:18
    tagyoureit commented #294
  • May 14 17:30
    556duckvader commented #293
  • May 14 16:27
    rstrouse closed #292
  • May 14 16:27
    rstrouse commented #292
  • May 14 16:22
    rstrouse commented #290
  • May 14 16:17
    Telemachus1977 commented #292
  • May 14 15:37

    rstrouse on master

    Fix Issue #292 - Added signatur… (compare)

  • May 14 10:35
    Tegguy commented #290
  • May 14 00:39
    rstrouse commented #290
  • May 13 23:59
    acronce commented #294
  • May 13 23:53
    acronce commented #294
kurtifier
@kurtifier
pi.PNG
rstrouse
@rstrouse
You have a syntax error in your config.json. If you copy and paste it to jsonlint.com it will show you the error.
kurtifier
@kurtifier
Thank you! I was able to get it to work now! I now have a new issue where on reboot both homebridge and the pool controller startup on reboot but the homebridge starts up before the pool controller can finish compiling. This makes it so that I cannot control my pool via homekit until I reboot homebridge. Is it possible to delay the homebridge startup so the poolcontroller can finish compiling?
DrJeff
@DrJeff
Screen Shot 2021-03-26 at 11.22.40 PM.png

Edit nano /etc/systemd/system/homebridge.serviceand add these lines

TimeoutStartSec=infinity
ExecStartPre=/bin/sleep 30

this will delay the service how ever many seconds you put

But this will delay every reboot of homebridge by the time you put here!!
DrJeff
@DrJeff
Oh and forgot you need to sudo systemctl daemon-reload to reload the service
nicdive
@nicdive
Hello, in release 6 I can’t find the new url command which replace « "pumpCommand/off/pump/1" to OFF
and "pumpCommand/run/pump/1/rpm/1600" to run with any chosen RPM »
My home automation was using this for a long time. Thanks for your help.
Jay Slabotsky
@JSlabotsky_twitter
It doesn't look like that exists in the new API. I'm running a virtual controller for a stand-alone pump and I really miss these simple commands. I can't get MQTT working with Home Assistant to save my life.
2 replies
DrJeff
@DrJeff
Screen Shot 2021-03-28 at 8.40.00 PM.png
spilote
@spilote
Hey guys, I'm trying to understand something. I currently don't have a salt system and planning on purchasing one. Would I simply need the Salt Cell (let's say from Hayward) and a Raspberry to control or I also need the controller from Hayward?
4 replies
zbrozek
@zbrozek:matrix.org
[m]
I just recently added in IC40 to my pool. So far I've had to run it at very very low duty cycles to avoid over-chlorinating. Also I find it very annoying that they don't actually sense the chlorine level when real cl- sensors exist, and that they don't use a switching power supply (so it wastes a good deal of energy).
2 replies
*an
Very nice not to have to keep tossing bottles of bleach in though. So on balance I'm glad to have done it, but I'm irritated that the product feels incomplete / under-engineered.
zbrozek
@zbrozek:matrix.org
[m]
Friend of mine and I are building our own controller that incorporates them. Retail price of such a sensor is around $500-1000 depending on what you get. Price to manufacturer is typically 10-40x lower on components.
20 replies
(I'm an electrical engineer and design industrial products for a living, so I see the pricing delta between distribution and direct-contract for a wide range of parts)
Not using a switching supply is inexcusable. The big transformer is probably more expensive than the switching supply, and certainly less efficient.
DrJeff
@DrJeff
@johnny2678 new thread?
You auto dosing Acid with your SWG you find high acid usage? SWG always raise pH in cement pools for me. Where is you pH at with how much dosing and mixing
28 replies
id-redacted
@id-redacted

Ok, I'm rather confused. I have njspc running on my rpi ubuntu installation. The server is running on port 4200 and log messages show it has successfully found the pool equipment.

I am running dashboard on port 80 (which I have set to allow).
I can reach the dashboard, but it shows disconnected from the server.

When I search for the server, it finds the server running on port 4200.

But after applying the setting, it still shows disconnected.

Once I managed to get it to show the pool and control it, but now it consistently does not work after a reboot.

Any thoughts?

ckurlinski
@ckurlinski
Use the external ip, if config
in the dashboard setup
I never used the loopback address
id-redacted
@id-redacted
Yes, I am using the direct ip(in this case 192.168.1.170)
ckurlinski
@ckurlinski
192.168.1.170:4200
id-redacted
@id-redacted
image.png
image.png
ckurlinski
@ckurlinski
restart the njpc
leaving dashboard running
id-redacted
@id-redacted
Ok. Nevermind. I have found the problem. Somehow my firewall rule to allow 4200 was lost.
I just re-added 4200 and its working fine.
Thanks
ckurlinski
@ckurlinski
ahhh, that will do it
No problem...
ufw
id-redacted
@id-redacted
So - now the question is: How do I get these to start on boot?
ckurlinski
@ckurlinski
from njpc wiki
systemd service would be the easiest
and do a similar service for dashboard
just verify your njpc and dashboard install folder
then verify node command - which node
ckurlinski
@ckurlinski
_service_dir=`find ~ -type d -name nodejs-poolController`
_node_cmd=`which node`
_node_user=`whoami`
_service_file="poolController.service"
_service_descr="NodeJS Pool Controller"
_service_doc="https://github.com/tagyoureit/nodejs-poolController/"
cat <<EOF > ${_service_file}
[Unit]
Description=${_service_descr}
Documentation=${_service_doc}
After=network.target

[Service]
Environment=NODE_ENV=production
Type=simple
User=${_node_user}
WorkingDirectory=${_service_dir}
ExecStart=${_node_cmd}
Restart=on-failure
RestartSec=15s

[Install]
WantedBy=multi-user.target
EOF

sudo cp ${_service_file} /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable `echo ${_service_file} | awk -F . '{print$1}'`
sudo systemctl start `echo ${_service_file} | awk -F . '{print$1}'`
sudo -n journalctl -o cat -n 2500 -f -u `echo ${_service_file} | awk -F . '{print$1}'`
adjust the vars for dashboard to create that one
tagyoureit
@tagyoureit

Hi all... PSA!
We pushed up 7.0.0 to the master branch. REM/dashPanel have also been updated to 7.0.0. Moving forward, we will be making all commits directly to the master branch and no longer doing development in the next branch. If you have been on the next branch now is the time to switch over to master.

You'll also notice that webClient is missing from that list. It hasn't gotten any love in the past ~7 months and I've previously hinted that it's going away. It's now officially deprecated so if you are still on webClient now is the time to move over to dashPanel.

Version 7 brings much improved connectivity between REM and njsPC. Setup has been streamlined between the two and there have been significant improvements in using njsPC + REM as a standalone controller/replacement for a commercial OCP (outdoor control panel).

20 replies
johnny2678
@johnny2678
image.png
Michael Smith
@emes
If anyone wants Docker images, these are built daily.
1 reply
DrJeff
@DrJeff

Version 7 brings much improved connectivity between REM and njsPC. Setup has been streamlined between the two and there have been significant improvements in using njsPC + REM as a standalone controller/replacement for a commercial OCP (outdoor control panel).

YES! Thanks

1 reply