nodejs-poolController/Lobby

Welcome to the nodejs-poolController lobby.

MaxVonEvil

@MaxVonEvil

(it should be said that all the RPM switches are deliberate. Those were 'Features' which I created in the PoolController web interface.

tagyoureit

@tagyoureit

Does the webclient match what you see in hubitat? You can also look in the ./data/pool*.json files.

MaxVonEvil

@MaxVonEvil

Well, it only matches as far as the mentioned features go and the general pool controller, as you can see:

Lemme check the json files if there's anything interesting... brb

MaxVonEvil

@MaxVonEvil

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?

tagyoureit

@tagyoureit

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

MaxVonEvil

@MaxVonEvil

Okay, cool that clarifies it. I was planning on adding another ESP-12 device in the backyard anyway, so there's worthy cause! :) Thanks for the help gents - season greetings here from Sin City!

1 reply

MaxVonEvil

@MaxVonEvil

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

n0xd

@n0xd

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

n0xd

@n0xd

I have had no luck with the pi initializing the pump. Is there a command I can send with my notebook out at the pump just to see if it's working. Then I can go from there.

n0xd

@n0xd

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.

rstrouse

@rstrouse

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.

n0xd

@n0xd

Thanks. what would be a good message to send? I may have problems with the comm on the pump. Not sure at this point.

n0xd

@n0xd

16,2,80,17,10,0,125,16,3 something like this?

rstrouse

@rstrouse

No that is a chlorinator message to set the output to 10%. A pump message to ask for its status would look more like this.
255, 0, 255,165, 0, 96, 16, 7, 0,1, 28 where the 96 represents a pump that has address 1 and an action of 7 get status.

3 replies

If you open an issue I will walk you through sending this message and watching the reply.

n0xd

@n0xd

n0xd

@n0xd

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

MaxVonEvil

@MaxVonEvil

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

MaxVonEvil

@MaxVonEvil

Hi again, so I enabled MQTT in the config.json and was expecting a root topic to appear in MQTT Explorer after restarting njsPC. I've verified that both Mosquitto and njsPC are running. Currently mosquitto is enabled for anonymous access. Not seeing any indications of MQTT postings in the poolcontroller console log (should I?) Any tips on how to troubleshoot this?

This is all she wrote. As you can see I've got an Ozwdaemon already talking to the MQTT broker

rstrouse

@rstrouse

You won't see any indications in the poolController console unless you have the logging level set to silly. To be sure you are running next. Is that correct?

MaxVonEvil

@MaxVonEvil

@rstrouse - not entirely sure I understood your question? running next?, btw I think I spoke too soon about not seeing anything on the pool controller side. It looks like it's trying to post something to the MQTT broker:

I'll have to check the Mosquitto logs and see what's going on there, brb

rstrouse

@rstrouse

There are two repos. One is the active development repo which we call next and the other is one that contains only fully baked code in master. The messages you are seeing is the rest service being called to toggle the state of circuit 7 and 8 from an external app on 192.168.0.19.

MaxVonEvil

@MaxVonEvil

Thanks for clarifying both items. It looks like I'm running the master repo, not next. That said, the default config.json of the master repo contained the mqtt section already, i.e. one could presume it was part of that build. Am I to understand I need to be running the next build for MQTT to work?

38 replies

rstrouse

@rstrouse

Yes that is correct.

rchalloner

@rchalloner

Question regarding Hubitat/ST integration--I noticed that the Pentair interface to poolController updates data about every second. The Hubitat hub can get bogged down with too many automation routines and data traffic. Is the integration pumping data as fast to the Hubitat or Smartthings hub and can the refresh rate be slowed on the poolController side? Things like temperature and chemical readings do not need to be updated but once a minute or so.

23 replies

Brad Sileo

@bsileo

I am sure I missed it here at some point - what is the right way to fix this warning"lat:undefined lon:undefined Not enough information to calculate Heliotrope."

3 replies

Graham Knights

@baudfather

Curious: is it possible to show the njspc version number in the webclient UI? Either bottom of page or when you click the hamburger icon. One of my winter projects is migrating to a SSD on my RPi for long term reliability, but don't remember what the last version I installed was. :)

tagyoureit

@tagyoureit

If you are on the next build and hover over the text in the upper right next to the hamburger menu it will tell you that. (I can't remember which version I added that in, specifically.). If you don't have the text, it will be the 6.0.0 release.

iotarho

@iotarho

I've got everything 90% working in Home Assistant: MQTT messages controlling "on/off" switches are working great and updating perfectly.

However the pool heater control doesn't seem to be working for me. I tried posting to the Home Assistant forums with no luck yet, so thought I might ask if anyone here has any insight. Here's the snippet of code, which shows up great in Home Assistant, but toggling the heat mode from "off" to "heat" has no effect, and I don't see anything messages show up in MQTT Explorer when I toggle.

Any hints or suggestions on what I might look at?

climate:
platform: mqtt
name: "Pool Heat"
min_temp: 40
max_temp: 104
modes:
"off"
"heat"
current_temperature_topic: easytouch2-8/state/temps/bodies/1/pool/temp
value_template: "{{ value_json.temp }}"
mode_state_topic: easytouch2-8/state/temps/bodies/1/pool/heatMode
mode_state_template: "{{ value_json['heatMode']['val'] }}"

13 replies

Exit2Studios

@Exit2Studios

I've got a standalone pump, and I have everything installed and seemingly working on the pi. On some occasions, when I cut and resume power to the Intelliflow, I get "display" on the display, which disables local control and means the pi is connected. However, this doesn't happen often and I can't for the life of me figure out the chain of events to get this working reliably. Otherwise, njspc can not connect. I've tried npm start& before/after/during power ups, I've tried disconnecting at the pi. Any ideas where I'm going wrong?

6 replies

2delarosa

@2delarosa

Has anyone tried remotely installing the nodejs-poolcontroller-webClient using VNC Connect? I lost the VNC connection in the middle of the npm install process. The WebClient is on port 8080 and the default values for httpPort is 5800, VNC well-known port are 5900, and the VNC linux server port is 5999. I really don't see there would be an issue but the raspberry pi is no longer listening for VNC connections. I'm working remotely so I can't do anything until I get on site. Wondering if anyone else experienced something similar.

5 replies

William Sutton

@zombielinux

has any work been done to integrate a TCP RS485 adapter, as opposed to a directly connected USB-RS485 adapter?

I've got some example code of my ethernet-rs485 adapter interacting with my ic-40. I wrote it in javascript if anyone is interested.

9 replies

2delarosa

@2delarosa

I installed PM2, added the ecosystem.config.js, and started it. Apologize for the multiple screenshots. Anyways, the virtual controller is up but the pump is now missing. What can I do to recover?

18 replies

2delarosa

@2delarosa

I had nodejs-poolController and nodejs-poolController-WebClient running based on the wiki. It was slow starting up so I tried tagyoureit suggestions but now I can't get any nodejs apps running. In the wiki, the NODE_ENV variable is null but tagyoureit had it set to production. I tried both ways without success.

`module.exports = {
apps: [
{
"name": "poolController",
"script": "dist/app.js",
"args": [
],
"cwd": "/home/openhabian/nodejs-poolController",
"autorestart": false,
"restart_delay": 10000,
"env": {
"NODE_ENV": ""
},
"watch": true,
"ignore_watch": ["data", "config.json", "node_modules", "logs", "dist", "replay", ".cache"],
"listen_timeout": 60000

     },
     {
         "name": "poolController-webClient",
         "script": "dist/Server.js",
         "args": [
         ],
         "cwd": "/home/openhabian/nodejs-poolController-webClient",
         "autorestart": false,
         "restart_delay": 10000,
         "env": {
             "NODE_ENV": ""
         },
         "watch": true,
         "ignore_watch": ["node_modules", "config.json", "src", "dist", ".cache"]
     }
 ],

deploy : {
production : {
user : 'SSH_USERNAME',
host : 'SSH_HOSTMACHINE',
ref : 'origin/master',
repo : 'GIT_REPOSITORY',
path : 'DESTINATION_PATH',
'pre-deploy-local': '',
'post-deploy' : 'npm install && pm2 reload ecosystem.config.js --env production',
'pre-setup': ''
}
}
};`

7 replies

William Sutton

@zombielinux

I think I found part of my issue. Does nodejs-poolController require a centralized controller? Or can I just stick random devices on the RS485 bus and it'll handle them without a controller?

45 replies

Where communities thrive

People

Repo info

Activity