Repository navigation
Replies: 1 comment
|
These are in testing and haven't been merged yet. You need to pull both:
It will be merged into master after some more testing, so please test and report any issues. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I’m trying to use
nodejs-poolControllerwith a brand-new Pentair IntelliCenter that appears to expose only the newer local WebSocket API on port6680.The WebSocket connection works directly, and njsPC logs that it connects to the IntelliCenter WebSocket, but njsPC then falls back to / initializes as
Nixie Single Bodyinstead of importing the real IntelliCenter object model.Environment
Port behavior
From the Pi:
So this panel appears to support the newer WebSocket path on
6680, not the older raw TCP / telnet-style path on6681.njsPC config
Relevant
config.jsonsection:{ "controller": { "comms": { "type": "ocpws", "portId": 0, "enabled": true, "mock": false, "netConnect": false, "ocpws": { "host": "10.0.1.158", "port": 6680, "alias": "ICT", "reconnectMs": 5000, "messageTimeoutMs": 10000 } } }, "web": { "servers": { "http": { "enabled": true, "ip": "0.0.0.0", "port": 4200, "authentication": "none" } } } }njsPC logs
On startup with the above config:
/state/allthen reports:{ "equipment": { "controllerType": "nixie", "model": "Nixie Single Body" } }dashPanel connects to njsPC at
10.0.1.101:4200, but only shows the fake/default Nixie model rather than the real IntelliCenter equipment.Direct WebSocket probe works
I tested the IntelliCenter directly with a small Node script using
ws.Connection:
Request:
{ "command": "GetParamList", "messageID": "probe-ver", "objectList": [ { "objnam": "_5451", "keys": ["VER"] } ] }Response:
{ "command": "SendParamList", "messageID": "probe-ver", "response": "200", "objectList": [ { "objnam": "_5451", "params": { "VER": "IC: 3.008 , ICWEB:2025-09-05 3.008" } } ] }Then I sent:
{ "command": "GetParamList", "messageID": "probe-all", "objectList": [ { "objnam": "ALL", "keys": ["OBJNAM", "OBJTYP", "SNAME", "SUBTYP", "VER"] } ] }That returned real IntelliCenter objects, including:
So the IntelliCenter local WebSocket API itself appears to be working and returning the real object model.
dashPanel observation
dashPanel connects to njsPC correctly when configured as:
However, the Controller → Comms dropdown only shows:
It does not show
IntelliCenter Network.I also checked dashPanel source:
That returned nothing.
Question
Is
controller.comms.type = "ocpws"currently expected to fully populate njsPC Equipment/State from the IntelliCenter WebSocket object model?The README/documentation appears to describe IntelliCenter v3 WebSocket support on port
6680, includingGetParamList objnam:"ALL"behavior. But my runtime behavior is:Nixie Single Body.IntelliCenter Networkcomms option.Is this a config issue on my side, or is the current
IntelliCenterWSimplementation only a transport scaffold that does not yet import/mutate Equipment/State?What I’m trying to achieve
I want njsPC to import the real IntelliCenter model and expose it at:
so I can then connect
homebridge-poolcontrollerto it.All reactions