Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 18:49
    jmillerhyetech closed #349
  • 18:49
    jmillerhyetech commented #349
  • 18:38
    tagyoureit commented #349
  • 18:20
    tagyoureit commented #349
  • 18:00
    tagyoureit commented #344
  • 17:55
    jmillerhyetech opened #349
  • 17:15

    tagyoureit on master

    mqtt parses out both setPoint/h… (compare)

  • 13:16
    johnny2678 commented #348
  • 13:16
    johnny2678 commented #348
  • 13:15
    johnny2678 commented #348
  • 05:43
    MichelMoriniaux closed #341
  • 05:43
    MichelMoriniaux commented #341
  • 02:10

    tagyoureit on master

    rename expansion cards to modul… (compare)

  • 01:29
    vj950 commented #344
  • 00:34
    johnny2678 commented #348
  • Sep 27 22:35
    tagyoureit commented #344
  • Sep 27 22:28

    tagyoureit on master

    Recognize expansion modules on … 7.5 7.5.0 (compare)

  • Sep 27 20:03

    rstrouse on master

    Fixed node's lame 32 bit intege… (compare)

  • Sep 27 18:31
    DrJeff commented #348
  • Sep 27 17:33
    johnny2678 commented #348
miamijerry
@miamijerry
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}
my script keeps trying to send the command because it's not registering a change
johnny2678
@johnny2678
script was also error-ing out looking for the 'superChlorHours' field, which i guess has been renamed to 'superChlorRemaining' - but I've updated that and SWG setpoint still isn't taking. Anything else change with the PUT cmds?
9 replies
johnny2678
@johnny2678
some more interesting Chlorinator message marked as invalid messages after changing to Silly logging:
3|poolController  | [2/21/2021, 11:23:59 AM] info: [11:23:59 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | [2/21/2021, 11:23:59 AM] verbose: Wrote packet [255,0,255,165,56,16,33,153,10,1,15,0,0,0,0,0,0,0,0,1,193].  Retries remaining: 3
3|poolController  | [2/21/2021, 11:23:59 AM] verbose: Wrote packet [255,0,255,165,56,16,33,217,1,0,1,232].  Retries remaining: 3
3|poolController  | [2/21/2021, 11:24:08 AM] debug: Packet not processed: 255,255,0,255,165,56,16,34,215,1,1,1,232
3|poolController  | [2/21/2021, 11:24:08 AM] debug: Packet not processed: 255,255,255,255,255,255,255,255,0,255,165,56,15,16,23,16,1,0,0,0,1,245,8,52,0,0,0,0,0,1,0,128,2,215
3|poolController  | RS485 Stats:{"bytesReceived":385536,"success":13282,"failed":191,"bytesSent":10858,"collisions":0}
3|poolController  | [2/21/2021, 11:24:12 AM] debug: Chlorinator message marked as invalid after not finding 16,3 in payload after 26 bytes
3|poolController  | [2/21/2021, 11:24:12 AM] debug: Chlorinator message marked as invalid after not finding 16,3 in payload after 26 bytes
3|poolController  | [2/21/2021, 11:24:14 AM] info: [11:24:14 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 11:24:14 AM] info: [11:24:14 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 11:24:15 AM] info: [11:24:15 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 11:24:15 AM] info: [11:24:15 AM] 192.168.5.31 GET /state/pumps {}
3|poolController  | [2/21/2021, 11:24:15 AM] info: [11:24:15 AM] 192.168.5.31 GET /state/chlorinators {}
3|poolController  | [2/21/2021, 11:24:15 AM] info: [11:24:15 AM] 192.168.5.31 PUT /state/chlorinator {"id":1,"poolSetpoint":75}
3|poolController  | [2/21/2021, 11:24:15 AM] verbose: Wrote packet [255,0,255,165,56,16,33,153,10,1,15,0,0,0,0,0,0,0,0,1,193].  Retries remaining: 3
3|poolController  | [2/21/2021, 11:24:15 AM] verbose: Wrote packet [255,0,255,165,56,16,33,217,1,0,1,232].  Retries remaining: 3
3|poolController  | [2/21/2021, 11:24:16 AM] silly: Retrying outbound message after 1.007secs with 3 attempt(s) left. - 165,56,16,33,217,1,0,1,232
3|poolController  | [2/21/2021, 11:24:16 AM] verbose: Wrote packet [255,0,255,165,56,16,33,217,1,0,1,232].  Retries remaining: 2
3|poolController  | [2/21/2021, 11:24:17 AM] silly: Retrying outbound message after 1.08secs with 2 attempt(s) left. - 165,56,16,33,217,1,0,1,232
3|poolController  | [2/21/2021, 11:24:17 AM] verbose: Wrote packet [255,0,255,165,56,16,33,217,1,0,1,232].  Retries remaining: 1
3|poolController  | [2/21/2021, 11:24:32 AM] info: [11:24:32 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 11:24:32 AM] info: [11:24:32 AM] 192.168.5.31 GET /state/circuits {}
3|poolController  | [2/21/2021, 11:24:33 AM] info: [11:24:33 AM] 192.168.5.31 GET /state/pumps {}
11 replies
script and logic haven't changed since 6.x was released - update to 6.5 was only change to the environment
johnny2678
@johnny2678
ezgif.com-gif-maker.gif
^ animation showing SWG setPoint updates not taking in dashPanel either. (with my control script not running)
kurtifier
@kurtifier
I am having an issue with my serial port. Everything was working and then one day it stopped and the serial port keeps opening and closing.
3 replies
Capture.PNG
kreijnen
@kreijnen
Hi guys, first of all compliments on this project! looks great and I would love to use it on my IntelliPool system.
Is there support for this type of controller?
1 reply
johnny2678
@johnny2678

trying to decipher the Influx Bindings... how would I add a tag that would indicate if the measurement was taken in Pool or Spa mode?

      "points": [
        {
          "measurement": "chemControllersPh",
          "description": "Bind chemController emit and save pH",
          "tags": [
            {
              "name": "name",
              "value": "@bind=data.name;"
            },
            {
              "name": "id",
              "value": "@bind=data.id;"
            },
            {
              "name": "dosing status desc",
              "value": "@bind=data.ph.dosingStatus.desc;"
            },
            {
              "name": "dosing method desc",
              "value": "@bind=vars.cfg.ph.dosingMethod.desc;"
            }
          ],
          "fields": [
            {
              "name": "level",
              "value": "@bind=data.ph.level;",
              "type": "float"
            },

For me, Pool is Circuit1 and Spa is Circuit6 so is there a way to do a conditional in the binding? Sorry - just not sure what to try here 😂

30 replies
pseudocode would be something like
            {
              "name": "mode",
              "value": "@bind=if(circuit1 isOn == true), "pool" else "spa";"
            }
DrJeff
@DrJeff
Ok do I have a Bad RS485? The com is seen when plugged in but all messages aborted after 2 attempts
[3/8/2021, 12:39:41 AM] error: Message aborted after 2 attempt(s): 165,0,96,33,4,1,255,2,42
[3/8/2021, 12:39:43 AM] warn: Message aborted after 2 attempt(s): 165,0,96,33,4,1,255,2,42
[3/8/2021, 12:39:43 AM] error: Message aborted after 2 attempt(s): 165,0,96,33,4,1,255,2,42
[3/8/2021, 12:39:46 AM] warn: Message aborted after 2 attempt(s): 165,0,96,33,4,1,255,2,42
[3/8/2021, 12:39:46 AM] error: Message aborted after 2 attempt(s): 165,0,96,33,4,1,255,2,42
2 replies
Was funtional with IntellifloVS and IC60 but not any more
DrJeff
@DrJeff
@tagyoureit ^ This is a virtual Controller using 6.5.1 Looks like I lost pump control? probably a dumb mistake but any idea what to check?
DrJeff
@DrJeff
Does REM work with virtual pump and chlorinated. I would like to add all controls to this instead of running esphome for orp, ph, temps, pressure, valves, and lights
2 replies
When I set the pump in the config (GUI) settings my controller loses track of time it just stops updating and no pump or ic60 control.
18 replies
DrJeff
@DrJeff
I was using both but stopped the webclient to use dashpanel.
woobins
@woobins
How do I use pm2 to send the npm run start:cached command instead of just start? I'm on a rpi zero so it takes forever to start if it has to build first.
editing the args in ecosystem.config.js doesn't seem to do it
1 reply
DrJeff
@DrJeff
can the Intelliflo VS virtual controller be feed the GPM from external flow sensor into MQTT just for display like in homebridge?
virtual-controller/state/pumps/1/intelliflovs/flow
{
  "flow": 60

}
2delarosa
@2delarosa
I'm trying to upgrade to the latest version but it says I have unmerged files
openhabian@casajuarez:~/nodejs-poolController $ git pull
error: Pulling is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
openhabian@casajuarez:~/nodejs-poolController $ git branch --list
  list
  master
* next
22 replies
Which branch should I point to?
2delarosa
@2delarosa
image.png
Here is image of some of the git pull output. I definitely did not modify those files
2delarosa
@2delarosa
@rstrouse, I'm getting a blank white page when I launch the webpage. I made sure to enter the IP address where the application lives since it will be accessed remotely. I launched another browser and it pops up but with the old view. I don't know if I have the right version
> nodejs-poolcontroller-dashpanel@0.0.1 start /home/openhabian/nodejs-poolController-dashPanel
> npm run build && node dist/app.js


> nodejs-poolcontroller-dashpanel@0.0.1 build /home/openhabian/nodejs-poolController-dashPanel
> tsc

info: Server is now listening on 192.168.100.39:5150
image.png