Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:14
    rstrouse commented #358
  • 02:06
    snagytx commented #358
  • 02:05
    snagytx commented #358
  • 00:55
    rstrouse commented #358
  • 00:41
    rstrouse commented #358
  • 00:37
    rstrouse commented #358
  • 00:30
    snagytx commented #358
  • 00:04
    rstrouse commented #358
  • Oct 20 23:57
    snagytx commented #358
  • Oct 20 23:52
    snagytx commented #358
  • Oct 20 23:49
    snagytx commented #358
  • Oct 20 23:43
    rstrouse commented #358
  • Oct 20 23:32
    snagytx commented #358
  • Oct 20 23:17
    rstrouse commented #358
  • Oct 20 23:16

    rstrouse on master

    Added troubleshooting messages … (compare)

  • Oct 20 22:37
    snagytx commented #358
  • Oct 20 22:34
    snagytx commented #358
  • Oct 20 21:49
    rstrouse commented #358
  • Oct 20 19:32
    snagytx commented #358
  • Oct 20 19:28
    snagytx commented #358
miamijerry
@miamijerry
8 replies
Michael McSharry has completed a Homeseer plugin, which brings all the functions into Homeseer by MQTT
miamijerry
@miamijerry
tagyoureit
@tagyoureit
Announcement: 6.5.0 pushed to main branch.
ckurlinski
@ckurlinski
Nice
antamy
@antamy
Many thanks to @tagyoureit and @rstrouse for their persistence in tracking down a protocol bug that was causing seemingly simple heating status and temperature display errors. It appears that I have a unique dialect on my system, but all is being understood now!
1 reply
tagyoureit
@tagyoureit
2021-02-19_22-01-13.png

Hey everyone... with the release of 6.5.0 we did a TON of work on integrating njsPC with REM (Relay Equipment Manager). If you have any ancillary devices you want to control (pH, ORP, pumps, temp sensors, flow sensors, etc then this is the project for you.

The backend changes needed to be accompanied with front-end changes as well and we've been working really hard on dashPanel. At this time, I'm recommending that everyone using the -webClient switch over to -dashPanel. DashPanel recently received a bootstrap theme which is pretty dang close to what you've been used to with webClient. Please give it a try. If there is anything that you really liked about webClient that isn't showing up in dashPanel (or any bugs) let us know!

I've previously recommended webClient as being more compatible with EasyTouch/IntelliTouch for njsPC but that's no longer the case as we've made a ton of updates/fixes to make dashPanel 100% compatible with *Touch controllers. dashPanel also loads up much faster, takes much less memory and is responsive to different devices.

http://github.com/rstrouse/nodejs-poolcontroller-dashPanel/

johnny2678
@johnny2678
oh man, you guys are innovating too quickly
ckurlinski
@ckurlinski
sweet
Brad Sileo
@bsileo
Cool stuff - I better jump back in and update my local environment! Hard to think about the pool when there is a bunch of snow and 15 degrees out!
ckurlinski
@ckurlinski
Ummm, shorts and flops here.....
; )
johnny2678
@johnny2678
that TX cold snap made it across the gulf and dropped us into the 50s last night. back up to 71 today
Brad Sileo
@bsileo
well I am in PA so no surprise here...we are enjoying it! 6" of fresh powder to ski today!
johnny2678
@johnny2678
ok, all I need to know @bsileo is... Penguins? or Flyers?
Brad Sileo
@bsileo
All Penguins! We live just outside Pittsburgh!
johnny2678
@johnny2678
Black and Gold baby
I'm from Sewickley
in FL now
ckurlinski
@ckurlinski
IMG_7579.jpeg
Have to run the AC here...
Brad Sileo
@bsileo
Very nice! All the best people are from the 'burgh!
Botched1
@Botched1
OK. Got dash panel installed. I don't see "Freeze Protection" status anywhere. Is that available? It is pretty important to us that leave our pool in service year-round.
rstrouse
@rstrouse
When freeze protection is engaged it should look like this.
image
Botched1
@Botched1
Ahh... OK. Cool - thanks!
Botched1
@Botched1
This has probably been asked a million times - so I apologize in advance. I'm currently running 6.1.0, what is the easiest/quickest way to update to 6.5.0? I always get it done in the end, but I'm sure how I do it is likely the hardest way possible. lol.
miamijerry
@miamijerry
in terminal paste
cd ~pi/nodejs-poolController enter then git pull enter
Botched1
@Botched1
did that, got an error. I likely installed it via ZIP the last time, not git clone.
But I'm getting an error on my clean 6.5 install anyway... Apparently on MQTT. I'll just roll back to 6.1.0 for now until I have more time to fight with it.
Botched1
@Botched1
OK, not that anyone cares, but I thought I put a bow around this. Was able to git clone the https address. Install, copy back my config.json and get it going.
tagyoureit
@tagyoureit
Always run ‘npm i’ as well to update dependencies.
Botched1
@Botched1
I did that the second time thinking that might have been why I had mqtt errors. AKA - RTFM. ;) 6.5.0 is working fine for me now.
johnny2678
@johnny2678
up and running on 6.5 with dashPanel - always fun trying to figure out my node environment. Was on 10. needed 12. had repo version installed. Ended up blowing away all things node & npm and using n. pretty nifty - https://github.com/mklement0/n-install
question on schedules - I went to change a schedule and got the message that Display is required...
Screen Shot 2021-02-21 at 8.15.05 AM.png
clicked the dropdown for display and there's nothing to choose from - so seems like I can't edit schedules
Screen Shot 2021-02-21 at 8.15.09 AM.png
can log an issue - just let me know
not a big deal
btw, what is "Display"
Botched1
@Botched1
@rstrouse Same here, can't edit or add schedules with dashPanel. Same issue as above - when saving a new or edited schedule it asks for a "display" but there is no display in the drop down. EasyTouch2 8.
2 replies
johnny2678
@johnny2678
^^ EasyTouch 2 4 here
I'll log an issue
johnny2678
@johnny2678
ok, pre 6.5 I was able to pass a # into this sub and it would change my SWG setpoint. The command still runs but the setpoint doesn't seem to change. Any ideas what's wrong?
def swg_Chlor_on():

  swg_dosingOutput = config['auto_swg'].getint('swg_dosingOutput')

  url = 'http://192.168.5.205:4200/state/chlorinator'
  data = '{"id":1,"poolSetpoint":' + str(swg_dosingOutput) + '}'
  headers = {'accept' : 'application/json', 'Content-Type':'application/json'}

  try:
    r = sess.put(url, data=data, headers=headers)

  except:
    raise
    logging.error("Cannot connect to the Pool Controller (Node.js - swg_Chlor_on)... exiting.")
    exit()
RTFM replies are welcome if I missed a change somewhere
johnny2678
@johnny2678
from the njspc logs - looks like the command is being received successfully:
3|poolController  | [2/21/2021, 10:48:59 AM] info: [10:48:59 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:48:59 AM] info: [10:48:59 AM] 192.168.5.31 GET /state/chlorinators {}
3|poolController  | [2/21/2021, 10:49:00 AM] info: [10:49:00 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | [2/21/2021, 10:49:15 AM] info: [10:49:15 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:15 AM] info: [10:49:15 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:15 AM] info: [10:49:15 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:15 AM] info: [10:49:15 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:15 AM] info: [10:49:15 AM] 192.168.5.31 GET /state/chlorinators {}
3|poolController  | [2/21/2021, 10:49:16 AM] info: [10:49:16 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | RS485 Stats:{"bytesReceived":300384,"success":10351,"failed":149,"bytesSent":7249,"collisions":0}
3|poolController  | [2/21/2021, 10:49:31 AM] info: [10:49:31 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:31 AM] info: [10:49:31 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:31 AM] info: [10:49:31 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:31 AM] info: [10:49:31 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:31 AM] info: [10:49:31 AM] 192.168.5.31 GET /state/chlorinators {}
3|poolController  | [2/21/2021, 10:49:32 AM] info: [10:49:32 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | [2/21/2021, 10:49:47 AM] info: [10:49:47 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:47 AM] info: [10:49:47 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 10:49:47 AM] info: [10:49:47 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:48 AM] info: [10:49:48 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 10:49:48 AM] info: [10:49:48 AM] 192.168.5.31 GET /state/chlorinators {}
3|poolController  | [2/21/2021, 10:49:48 AM] info: [10:49:48 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | RS485 Stats:{"bytesReceived":301641,"success":10390,"failed":150,"bytesSent":7315,"collisions":0}