Apparent failed install of controller and panel

[mzuniga51]

Hello folks. I am a noob in all things Raspberry Pi but gave it a try to install the Pool Controller following the very detailed instructions MyAZPool provided in TFP. Installation of both applications got hung after some errors and when launching the web interface I find several strange behaviors, maybe consistent with a failed installation. For instance, my pool appear off when it is actually on, and the pump is actually running. I can control light, circuits, pumps and I can see chemistry.

I've tried installation a few times, one fixing npm audit errors (I realize I should not do that now) but the errors persists in either cases.

Per tagyoureit instruction I'm attaching the packet capture plus the applications installation logs.

Any help will be much appreciated!

2021-10-10T01_51_47_875Z-debug.log 2021-10-10T01_58_16_401Z-debug.log replay.zip

Pool Equipment

• Intellicenter i10D (dual pool and spa equipment)
• Controller Firmware Version 1.047
• Pump(s) manufacturer and model: 2x IntelliFlow 2 VST 011056
• Chlorinator: IntelliChlor-40 (pool) IntelliChlor-20 (spa)
• Heater(s): 2x Master
• Chemical controller: 2x Intellichem
• 2x CO2 feeders
• Jandy Valves with two actuators (pool bubbler and spa jets)

Raspberry Pi Raspberry Pi 3 B+ Raspberry Pi OS 5.10 USB to RS485 adapter https://www.amazon.com/dp/B081MB6PN2?psc=1&ref=ppx_yo2_dt_b_product_details connected with Cat5e shielded cable to Intellicenter Com port

Desktop:

• OS: macOS Big Sur 11.6
• Browser: Safari
• Version 15

Smartphone:

• Device: Iphone 11 Max
• OS: iOS 15.0.1
• Browser: Safari

[rstrouse]

When you switch to service mode do you see Service displayed in the header of dashPanel? Please capture a replay while switching between service and auto modes.

[mzuniga51]

Yes. Service Mode is displayed replay 5.zip

[rstrouse]

I know it is displayed there. Is it displayed in dashPanel?

[mzuniga51]

Ohh, I see what you are getting at. It does not appear in dashPanel!

[mzuniga51]

Hi @rstrouse. Any progress so far? Many thanks!

[rstrouse]

Pull njsPC. I worked through the Service Mode. Please note when the controller is is service mode you should not be able to control the pool from anywhere but the OCP. With the i10PS it rejects any command sent to the OCP from any external controller including njsPC.

Please verify that when the panel is in Service Mode the header on dashPanel shows that it is in service mode.

After this test I would like you to create a capture where it is not controlling the pool after coming out of service mode to auto.

[mzuniga51]

Great. Did it. Now the panel shows Service Mode and i can confirm that i cannot get out of it from the panel.

Here is the capture. You will see that after pressing Service mode and then Auto on the OCP i pressed Pool on on the panel a few times. There the button gets green and then immediately gets gray again.

By the way, what is your name? My name is Manuel Zuniga and I live in Costa Rica.

replay 6.zip

[rstrouse]

Manuel, hi I am Robert from Northern California. Please pull njsPC and lets see if the byte setting changes I made make a difference with an i10D.

[mzuniga51]

Hi Robert. Im afraid there was no change yet.

[rstrouse]

Are the other circuits working? Is this just the pool circuit?

[mzuniga51]

Yes, everything works except for the pool as far as i can tell

On Fri, Oct 22, 2021 at 8:27 PM rstrouse @.***> wrote:

Are the other circuits working? Is this just the pool circuit?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950042999, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSSZV6VM3R7LZ6V2WQVDUIIMS3ANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mzuniga51]

Actually, now if Pool is on on the OCP I can turn it off on the dashpanel but i cannot turn it off if OCP is on. In either case, Pool button remains off or gets on momentarily and then off on the panel.

On Fri, Oct 22, 2021 at 8:27 PM rstrouse @.***> wrote:

Are the other circuits working? Is this just the pool circuit?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950042999, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSSZV6VM3R7LZ6V2WQVDUIIMS3ANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

So if you turned on the pool from the OCP not in service mode. Does it show as on in dashPanel? If it does are you saying you cannot turn it off?

[mzuniga51]

Ok so now either If i am coming back from Service then Pool button in the dashboard flashes green and then gets greyed out. So I thin dashboards knows Pool got on in the OCP but is not able to kind of keep that knowledge Same behavior now of I just turn Pool off and on again on the OCP If Pool is off on the OCP i can turn it on from the dashboard, but 1) it doesnt "take" it the first press so I have to do it twice, and again dashboard flashes green and then goes to grey (Pool on OCP remains on however) This is different than before as you have noticed.

On Fri, Oct 22, 2021 at 8:48 PM rstrouse @.***> wrote:

So if you turned on the pool from the OCP not in service mode. Does it show as on in dashPanel? If it does are you saying you cannot turn it off?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950045148, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS6O5PJ3VHCE4F62ZXLUIIO73ANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

I am going to be out until the end of next week so I wanted to get some things going for when I get back. I am having a bit of trouble visualizing what is going on on your end so I am going to give you some questions that give some definite answers for what is actually happening.

For now do not switch the panel back and forth between Service and Auto. This will only confuse the issues we are having since Service mode is really localized to the OCP. Service Mode is intended to be used by personnel working on the pool who do not have access to the automation system. Putting the panel in Service mode is designed to allow the operator to turn things on and of as well as disable external control panels. Imagine opening up the pump basket then having someone in the house turn on the pump. So put the OCP in Auto and leave it there.

First I want to make sure we are seeing the states reflected properly from the controller. If you have an Indoor Control Panel (ICP) or a Wireless Control Panel (WCP) then I would prefer you use them to perform the tests. If you have none of these then please use the IntelliCenter web to perform the following tasks. Start with everything turned off.

1. Turn on the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns green.
   • Did the Pool button turn green and stay green?
2. Turn off the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns grey.
   • Did the Pool button return to grey and stay grey?

For the next set of tests I want to make sure nothing else is on for the pool or spa. This is important since this can be confusing when looking at the messages. Please set the heat modes for both pool and spa to Off as well. I want to make sure we are not seeing delays related to the heaters or valves.

1. From dashPanel start a replay by clicking on the Capture Replay button.
2. Turn on the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize.
3. Turn off the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize.
4. Turn on the pool using dashPanel. If the pool does not come on wait 3 seconds and click it again. Physically check to see whether the pool circuit came on by checking the equipment on the pad. If it doesn't come on then use the selected IntelliCenter controller to turn on the pool. Bear in mind if the first tests are not successful then this test will not be successful.
   • Did the pool turn on and the dashPanel button stay green?
5. At this point the dashPanel button should be green. If it is not you won't be able to turn it off using dashPanel. If it is green, turn off the pool using dashPanel. If it does not turn off wait 3 seconds then click the button again.
6. Go back into the dashPanel settings menu and press the Cancel Capture button. Then upload that capture here.

[mzuniga51]

Thanks for the detailed instructions. I will do this later today.

On Sat, Oct 23, 2021 at 10:50 AM rstrouse @.***> wrote:

I am going to be out until the end of next week so I wanted to get some things going for when I get back. I am having a bit of trouble visualizing what is going on on your end so I am going to give you some questions that give some definite answers for what is actually happening.

For now do not switch the panel back and forth between Service and Auto. This will only confuse the issues we are having since Service mode is really localized to the OCP. Service Mode is intended to be used by personnel working on the pool who do not have access to the automation system. Putting the panel in Service mode is designed to allow the operator to turn things on and of as well as disable external control panels. Imagine opening up the pump basket then having someone in the house turn on the pump. So put the OCP in Auto and leave it there.

First I want to make sure we are seeing the states reflected properly from the controller. If you have an Indoor Control Panel (ICP) or a Wireless Control Panel (WCP) then I would prefer you use them to perform the tests. If you have none of these then please use the IntelliCenter web to perform the following tasks. Start with everything turned off.

1. Turn on the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns green.
   • Did the Pool button turn green and stay green?
2. Turn off the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns grey.
   • Did the Pool button return to grey and stay grey?

For the next set of tests I want to make sure nothing else is on for the pool or spa. This is important since this can be confusing when looking at the messages. Please set the heat modes for both pool and spa to Off as well. I want to make sure we are not seeing delays related to the heaters or valves.

1. From dashPanel start a replay by clicking on the Capture Replay button.
2. Turn on the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize.
3. Turn off the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize.
4. Turn on the pool using dashPanel. If the pool does not come on wait 3 seconds and click it again. Physically check to see whether the pool circuit came on by checking the equipment on the pad. If it doesn't come on then use the selected IntelliCenter controller to turn on the pool. Bear in mind if the first tests are not successful then this test will not be successful.
   • Did the pool turn on and the dashPanel button stay green?
5. At this point the dashPanel button should be green. If it is not you won't be able to turn it off using dashPanel. If it is green, turn off the pool using dashPanel. If it does not turn off wait 3 seconds then click the button again.
6. Go back into the dashPanel settings menu and press the Cancel Capture button. Then upload that capture here.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950179969, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS6WTB62RKNSEGL3VZTUILRVZANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mzuniga51]

See my answers below Robert. If the OCP does not intervene everything works flawlessly.

There might be a huge bug in the firmware as I also discovered the following:
-If you turn Pool off from OCP then any programmed schedules are kept active the whole time while Pool is off (schedule buttons are green on in Schedules in IntelliCenter web page). When you turn Pool on, schedules are kept active.
-If you do the same from the Intellicenter web and turn Pool off, then any programmed schedules active at the time are deactivated (gray buttons on Schedules in IntelliCenter web page) and will not turn on when Pool is on again from the web.
-Furthermore, programmed Schedules will also not turn on even if you turn Pool on from the OCP -When that happens, the only way to get schedules back on track is by putting OCP in service mode or reseting the panel

replay.zip

On Sat, Oct 23, 2021 at 10:50 AM rstrouse @.***> wrote:

I am going to be out until the end of next week so I wanted to get some things going for when I get back. I am having a bit of trouble visualizing what is going on on your end so I am going to give you some questions that give some definite answers for what is actually happening.

For now do not switch the panel back and forth between Service and Auto. DONE. I´M STARTING WITH THE PANEL IN AUTO

First I want to make sure we are seeing the states reflected properly from the controller. If you have an Indoor Control Panel (ICP) or a Wireless Control Panel (WCP) then I would prefer you use them to perform the tests. If you have none of these then please use the IntelliCenter web to perform the following tasks. I DON'T HAVE AN ICP OR WCP. I´LL DO IT FROM THE INTELLICENTER WEB

Start with everything turned off. I HAVE TURNED EVERYTHIN OFF

1. Turn on the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns green.
   • Did the Pool button turn green and stay green? YES IT DOES
2. Turn off the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns grey.
   • Did the Pool button return to grey and stay grey? YES IT DOES

For the next set of tests I want to make sure nothing else is on for the pool or spa. EVERYTHING IS OFF

Please set the heat modes for both pool and spa to Off as well. I want to make sure we are not seeing delays related to the heaters or valves. NO CIRCUIT NOR DEVICE IS ON INCLUDING HEATERS, INTELLICHLORS , INTELLICHEMS OR VALVES

1. From dashPanel start a replay by clicking on the Capture Replay button. DONE
2. Turn on the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize. DONE
3. Turn off the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize. DONE
4. Turn on the pool using dashPanel. If the pool does not come on wait 3 seconds and click it again. Physically check to see whether the pool circuit came on by checking the equipment on the pad. If it doesn't come on then use the selected IntelliCenter controller to turn on the pool. Bear in mind if the first tests are not successful then this test will not be successful.
   • Did the pool turn on and the dashPanel button stay green? YES. I HAD TO WAIT 3 SECONDS AND DO A SECOND PRESS BUT BUTTON GREEN AND STAYS GREEN. EQUIPMENTS PHYSICALLY ON
5. At this point the dashPanel button should be green. If it is not you won't be able to turn it off using dashPanel. If it is green, turn off the pool using dashPanel. If it does not turn off wait 3 seconds then click the button again. DONE. BUTTON TURNS GRAY AT FIRST PRESS AND EQUIPMENT PHYSICALLY OFF
6. Go back into the dashPanel settings menu and press the Cancel Capture button. Then upload that capture here. DONE

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950179969, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS6WTB62RKNSEGL3VZTUILRVZANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mzuniga51]

Hey Robert. Did the last capture give you some additional insights? Thanks

On Sat, Oct 23, 2021 at 1:49 PM Manuel Zuniga @.***> wrote:

See my answers below Robert. If the OCP does not intervene everything works flawlessly. The problem is that schedules, as well as coming in and out from service mode, seem to reside in the OCP so when they start I immediately loose control. So the issue is whenever the OCP acts, it seems.

On Sat, Oct 23, 2021 at 10:50 AM rstrouse @.***> wrote:

I am going to be out until the end of next week so I wanted to get some things going for when I get back. I am having a bit of trouble visualizing what is going on on your end so I am going to give you some questions that give some definite answers for what is actually happening.

For now do not switch the panel back and forth between Service and Auto. DONE. I´M STARTING WITH THE PANEL IN AUTO

First I want to make sure we are seeing the states reflected properly from the controller. If you have an Indoor Control Panel (ICP) or a Wireless Control Panel (WCP) then I would prefer you use them to perform the tests. If you have none of these then please use the IntelliCenter web to perform the following tasks. I DON'T HAVE AN ICP OR WCP. I´LL DO IT FROM THE INTELLICENTER WEB

Start with everything turned off. I HAVE TURNED EVERYTHIN OFF

1. Turn on the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns green.
   • Did the Pool button turn green and stay green? YES IT DOES
2. Turn off the Pool circuit using the selected IntelliCenter controller while watching dashPanel. The result should be that the pool button turns grey.
   • Did the Pool button return to grey and stay grey? YES IT DOES

For the next set of tests I want to make sure nothing else is on for the pool or spa. EVERYTHING IS OFF

Please set the heat modes for both pool and spa to Off as well. I want to make sure we are not seeing delays related to the heaters or valves. NO CIRCUIT NOR DEVICE IS ON INCLUDING HEATERS, INTELLICHLORS , INTELLICHEMS OR VALVES

1. From dashPanel start a replay by clicking on the Capture Replay button. DONE
2. Turn on the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize. DONE
3. Turn off the pool using the selected IntelliCenter controller. Wait at least 1 minute for the pumps to spin up and stabilize. DONE
4. Turn on the pool using dashPanel. If the pool does not come on wait 3 seconds and click it again. Physically check to see whether the pool circuit came on by checking the equipment on the pad. If it doesn't come on then use the selected IntelliCenter controller to turn on the pool. Bear in mind if the first tests are not successful then this test will not be successful.
   • Did the pool turn on and the dashPanel button stay green? YES. I HAD TO WAIT 3 SECONDS AND DO A SECOND PRESS BUT BUTTON GREEN AND STAYS GREEN. EQUIPMENTS PHYSICALLY ON
5. At this point the dashPanel button should be green. If it is not you won't be able to turn it off using dashPanel. If it is green, turn off the pool using dashPanel. If it does not turn off wait 3 seconds then click the button again. DONE. BUTTON TURNS GRAY AT FIRST PRESS AND EQUIPMENT PHYSICALLY OFF
6. Go back into the dashPanel settings menu and press the Cancel Capture button. Then upload that capture here. DONE

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-950179969, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS6WTB62RKNSEGL3VZTUILRVZANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

I have been a bit busy but I did take some time to look at the replay. Here is what I am seeing happening.

Given the message sequence below.

1. The line with the black arrow and the poo icon is where you pressed the button to turn on the pool circuit.
2. Message number 35234 is njsPC requesting the circuit to be turned on. The 32 on the 4th position of the payload indicates this.
3. Message number 35235 is the response from the OCP indicating that it received the message and is processing it.
4. Message number 35236 is njsPC asking the OCP which circuits are currently on.
5. Message number 35237 is the OCP responding with the current circuit status. Notice the 32 on the 3rd position.
6. Message number 35238 is njsPC responding that it successfully got the message
7. Message number 35239 is the OCP turning the circuit back off again. Notice that message 35239 and 35234 are the same command except the byte at the 4th position is 0 not 32. At the end of this sequence is also a pattern 0,1,1,0 instead of the 0,0,1,0 which that byte that is 1 typically indicates that the circuit change is due to a schedule.

If when it does this can you hit the button again in dashPanel to get the pool circuit to stay on?

[mzuniga51]

Hi Robert. Hmmm, can you rephrase the question? Im not sure i’m following. Thanks

On Tue, Nov 9, 2021 at 12:08 PM rstrouse @.***> wrote:

I have been a bit busy but I did take some time to look at the replay. Here is what I am seeing happening.

Given the message sequence below. [image: image] https://user-images.githubusercontent.com/47839015/140977444-5c04bbdd-77cf-4af8-b1f2-20798b375057.png

1. The line with the black arrow and the poo icon is where you pressed the button to turn on the pool circuit.
2. Message number 35234 is njsPC requesting the circuit to be turned on. The 32 on the 4th position of the payload indicates this.
3. Message number 35235 is the response from the OCP indicating that it received the message and is processing it.
4. Message number 35236 is njsPC asking the OCP which circuits are currently on.
5. Message number 35237 is the OCP responding with the current circuit status. Notice the 32 on the 3rd position.
6. Message number 35238 is njsPC responding that it successfully got the message
7. Message number 35239 is the OCP turning the circuit back off again. Notice that message 35239 and 35234 are the same command except the byte at the 4th position is 0 not 32. At the end of this sequence is also a pattern 0,1,1,0 instead of the 0,0,1,0 which that byte that is 1 typically indicates that the circuit change is due to a schedule.

If when it does this can you hit the button again in dashPanel to get the pool circuit to stay on?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-964404670, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS3ASYATTOXNCKGQ3PTULFPTPANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

Using dashPanel I would like you to turn the pool circuit on. When the OCP turns it back off again, hit the button again waiting 3 seconds between each attempt. Do this at least 5 times. I want to know if your OCP is persistent at refusing to turn on the pool. It is so odd that it is only the pool circuit that will not remain on even after the OCP responds that it is turning it on.

[mzuniga51]

Robert, remember that when Pool is off in the OCP I have no problem turning on and off dashPanel. See replay.zip

The problem is when Pool is on because a schedule has activated it. Then the on button on dashPanel appears gray while Pool is actually on. Then I have no control from dashPanel, presumably because dashPanel thinks Pool is off when it is actually on. So OCP and dashPanel seem to fall out of sync for some reason. See replay-2.zip

[rstrouse]

So replay.zip works fine and replay-2.zip does not?

[mzuniga51]

Correct

On Sat, Nov 13, 2021 at 12:48 PM rstrouse @.***> wrote:

So replay.zip works fine and replay-2.zip does not?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-968116791, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSSZ4F5TDD7PNICEP52LUL2XHPANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

Hmmm.... there is something different here because the initial setup was not setting the bits correctly on the status message. Now it appears that all this information is correct and it operates just like every other IntelliCenter model that I have seen. Did you change anything in the configuration since we started looking into this?

[mzuniga51]

No. Nothing Robert. Sometimes it seems as there are almost random things happening with this system. Hope Pentair get his s@*t together with an upcoming (?) firmware update.

On Sat, Nov 13, 2021 at 1:15 PM rstrouse @.***> wrote:

Hmmm.... there is something different here because the initial setup was not setting the bits correctly on the status message. Now it appears that all this information is correct and it operates just like every other IntelliCenter model that I have seen. Did you change anything in the configuration since we started looking into this?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-968120953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS3DEOXYG6YB6LFIYC3UL22N5ANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

Are you operating the OCP by switching to Service Mode? If you are I think I may have been chasing the wrong thing. Service mode is pretty much a legacy holdout from the older Pentair panels. While it still has the benefit of disabling external controllers, it is not required for normal operation on an IntelliCenter panel. In IntelliTouch you could not operate the relays at the OCP without service mode but that it no longer the case with IntelliCenter since it contains a localized control panel.

[mzuniga51]

No. I stopped using service mode when you instructed me a while back. But schedule activation in OCP (without user intervention) seem to have the same effect as coming out of service mode to auto.

On Sat, Nov 13, 2021 at 1:30 PM rstrouse @.***> wrote:

Are you operating the OCP by switching to Service Mode? If you are I think I may have been chasing the wrong thing. Service mode is pretty much a legacy holdout from the older Pentair panels. While it still has the benefit of disabling external controllers, it is not required for normal operation on an IntelliCenter panel. In IntelliTouch you could not operate the relays at the OCP without service mode but that it no longer the case with IntelliCenter since it contains a localized control panel.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-968123194, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS5L6JL4VFEU76GPZELUL24GRANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

Do you have Manual OP Priority turned on?

[mzuniga51]

No I dont. Should I?

On Sat, Nov 13, 2021 at 1:40 PM rstrouse @.***> wrote:

Do you have Manual OP Priority turned on?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-968125665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSSYNPWZSMB4DTFMPDZ3UL25MVANCNFSM5FWZCE5Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rstrouse]

No it doesn't work like they have it documented so I don't know if they have a bug with this or not. Bear in mind that the other OCPs out there are also not bug free. The main difference with IntelliCenter is that you can update the firmware without sending the panel off to have it updated. I was a long time IntelliTouch user and lived with some vexing issues that would cause me to have to completely reprogram the system over and over again.

I changed everything back so that i10D looks at the status messages just like every other IntelliCenter panel. Given the last two sets of replays this is how IntelliCenter operates for every other panel we have seen. Including another i10D.

So pull njsPC and dashPanel then restart both server applications. After you have done that lets make sure the state is reflecting the state when you use the IntelliCenter web. Then lets try it by using the control panel on the OCP (not service mode) making sure it shows the proper state in dashPanel. Then the final thing will be to try to turn it off after it kicks on during a schedule then back on again.

[mzuniga51]

So, Robert, I was about to pull njsPC and try to access dashPanel only to find this. Nothing to do with the problem we were dealing with? I havent changed a thing. Any idea what could have happened?

Things I’ve tried: raspberry reboot, intellicenter reboot, verify physical conection cable continuity, all lights in adapter working, intellicenter factory reset, Raspberry factory reset and package reinstall. Nothing works!!

I

[mzuniga51]

Only additional things that occcur to me could be causing this is a busted usb adapter or some corruption to the Intellicenter firmware 🤦🏻‍♂️🤷🏻‍♂️

[rstrouse]

The things that can cause this are in the following order. Some of these you have already verified to not be the case.

1. Verify that there is nothing else accessing the adapter. This includes more than one running instance of njsPC or terminal programs.
2. Wiring between the adapter and the comm port.
3. The transceiver on the RS485 adapter is set to TTY and not RS485.

I have some questions for you Which adapter do you have?
How are you launching njsPC? Are you running any terminal programs? Do you have bluetooth turned on on the Pi?

You should open dashPanel and navigate to the RS485 tab. If the adapter is receiving successfully you should see the Received bytes incrementing as well as the successful numbers increasing.

[mzuniga51]

So, in the same order.

1. Only one version running
2. Seem to be ok. Black to ground, green to B-, yellow to A+. Same cable and connected to the same COM port as before
3. Where do you check on this?

This is my adapter https://www.amazon.com/gp/product/B081MB6PN2/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 I'm currently launching manually (npm start) Only things running is dashPanel and poolController. VNC is also activated Bluetooth is turned on

Adapter is receiving well with 0% failure rate

[mzuniga51]

Hey, please ignore if it is too much of an imposition but you can log into my Pi directly and roam around if you want. Please feel free to make any changes or tests you want as I have not much to loose and I can always resort to my backup. I'm sending my credentials in a pm in TFP.

[mzuniga51]

Robert, see you tried to get in and VNC blocked you based on your location. I have authorized you now. Sorry about that.

[rstrouse]

So I looked at your pi and njsPC is opening the serial port successfully. However, there is no traffic on it whatsoever. The only bytes received are the ones that are part of the open for the port that are read from the buffer on the RS485 chip which points to the adapter not receiving information over the wire or the adapter is bad. However, before we rule the adapter dead there are some other things to try.

I have disabled the remote GPIO and serial console on the pi. These sometimes interfere with serial devices depending on the OS build. I also tried to pull from the repository. However, I am not sure how you installed the repository. Did you do a git clone to install njsPC or did you load the software in another way? git clone https://github.com/tagyoureit/nodejs-poolController.git

[mzuniga51]

First, thanks a lot. You are the best. My buddy reinstall my pi and the packages for me so I´ll as him how he do it and will get back to you. What adapter you use? I'm thinking to buy one now and have it as backup even if we somehow manage to get the current one working.

On Mon, Nov 15, 2021 at 11:31 AM rstrouse @.***> wrote:

So I looked at your pi and njsPC is opening the serial port successfully. However, there is no traffic on it whatsoever. The only bytes received are the ones that are part of the open for the port that are read from the buffer on the RS485 chip which points to the adapter not receiving information over the wire or the adapter is bad. However, before we rule the adapter dead there are some other things to try.

I have disabled the remote GPIO and serial console on the pi. These sometimes interfere with serial devices depending on the OS build. I also tried to pull from the repository. However, I am not sure how you installed the repository. Did you do a git clone to install njsPC or did you load the software in another way? git clone https://github.com/tagyoureit/nodejs-poolController.git

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-969144494, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS4QEFG5AI4RFODWVLLUME7YZANCNFSM5FWZCE5Q .

[rstrouse]

I have quite a few but I do not recommend the standalone adapter that I currently use in my production as there have been tons of report that the quality has waned on them and even getting one that works initially is questionable. JBtek When I get some time I am going to switch over to the Sequent MEGA-IND board that is already installed on my system. I use that board as a power supply and input device and finally got around to creating the support functions to enable the RS485 port on that board.

Honestly, it almost looks like the yellow and green wires are reversed on your adapter because any bytes that are getting loaded into the buffer appear to be scrambled, but you said it was working before. If there is a chance that the wires got reversed reverse them at the adapter and see if that changes anything. It won't hurt because yellow/green do not have a polarity by themselves.

Also here is an install guide that is a bit more descriptive. From what I see of your install all you need are the prerequisites, njsPC, and dashPanel https://github.com/tagyoureit/nodejs-poolController/wiki/DIY-Standalone-Nixie-Pool-Controller#install-software-prerequisites

[mzuniga51]

So, good news is that I have managed to reconnect by changing the adapter. Apparently the old one was busted.

No, not so good news is that things are a bit worse with dashPanel. I'll make some more comprehensive tests tomorrow and get back to you.

On Mon, Nov 15, 2021 at 11:31 AM rstrouse @.***> wrote:

So I looked at your pi and njsPC is opening the serial port successfully. However, there is no traffic on it whatsoever. The only bytes received are the ones that are part of the open for the port that are read from the buffer on the RS485 chip which points to the adapter not receiving information over the wire or the adapter is bad. However, before we rule the adapter dead there are some other things to try.

I have disabled the remote GPIO and serial console on the pi. These sometimes interfere with serial devices depending on the OS build. I also tried to pull from the repository. However, I am not sure how you installed the repository. Did you do a git clone to install njsPC or did you load the software in another way? git clone https://github.com/tagyoureit/nodejs-poolController.git

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-969144494, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS4QEFG5AI4RFODWVLLUME7YZANCNFSM5FWZCE5Q .

[mzuniga51]

Robert, I have prepared a video that might be helpful explaining what I'm seen now. There is a capture I made during the filming on the video so you can trace what I was doing step by step. As you see, I think we backtracked a bit. Again, manual priority is off and I'm not touching the service button at all. Thanks

[rstrouse]

Your video never finished uploading. However, I made some changes so lets see where we are after you pull njsPC.

[mzuniga51]

Sorry abt the video. Anyway with the latest changes things are back at where we were before the adapter meltdown so, better than this afternoon. I'd say the only issue is still schedules. This capture shows the exact moment a schedule starts. At this precise moment Pool gets and stays green in OCP, web and app. On the other hand, dashPanel gets momentarily green and then gray in dashPanel. I don't get any response from that moment on by pressing the Pool button at the dashPanel no matter how many times I do it. replay (3).zip

[rstrouse]

Ok so here is the craziness with this. The panel does not report that it it turned anything on when the schedule kicks in.

Strangely, it does not report on the status message or the heartbeat like all other OCPs we have witnessed and the only circuit which it ignores is circuit 6 (your pool circuit). It does however report on another byte when the pool circuit is manually turned on and occasionally on the status message (where all other OCPs report their relay status). Interestingly, it always reports correctly when njsPC asks for the state information. This is why it momentarily sets the correct state only to have the OCP incorrectly report. It could be that the Pentair controllers do not see this because they simply ignore the state for body circuits.

So what I have done is completely ignore the heartbeat and status messages when it comes to the pool circuit and only rely on the requests made by njsPC or requests by other controllers to change the state. Please pull njsPC and lets see if we slayed this dragon.

[mzuniga51]

This seem to be a hydra rather than a dragon. One head cut and another pops out. Believe it or not, now Pool works fine BUT, wait for it, Spa is doing now exactly what Pool was doing before. Can you believe it? I will have to send you a very nice bottle of scotch if you solve this one.

On Wed, Nov 17, 2021 at 12:32 PM rstrouse @.***> wrote:

Ok so here is the craziness with this. The panel does not report that it it turned anything on when the schedule kicks in.

Strangely, it does not report on the status message or the heartbeat like all other OCPs we have witnessed and the only circuit which it ignores is circuit 6 (your pool circuit). It does however report on another byte when the pool circuit is manually turned on and occasionally on the status message (where all other OCPs report their relay status). Interestingly, it always reports correctly when njsPC asks for the state information. This is why it momentarily sets the correct state only to have the OCP incorrectly report. It could be that the Pentair controllers do not see this because they simply ignore the state for body circuits.

So what I have done is completely ignore the heartbeat and status messages when it comes to the pool circuit and only rely on the requests made by njsPC or requests by other controllers to change the state. Please pull njsPC and lets see if we slayed this dragon.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-971855054, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS2XFX55NSQMCWEYWLDUMPYNTANCNFSM5FWZCE5Q .

[mzuniga51]

Oh, and in a bit of good news, today my second Intellichlor for my spa was installed. I can correctly read chemistry from both Intellichlors in dashPanel!!

[rstrouse]

That is crazy. So far in all of this we have had the OCP reporting the pool circuit correctly on the status message. Then it reported on the heartbeat message. And finally, it reported only when a schedule did not turn it on. All this time all other circuits and features reported just like every other panel out there including the other body circuit 1(spa). Now it appears the spa is acting like the pool circuit.

The good news is that I have a pretty good idea how to fix it in short order. So pull njsPC and lets see if our spa circuit works as it should.

[mzuniga51]

Well Robert, dragon duly slayed! Everything seem to be finally in working order. I don't quite understand how you pull this off but I'm glad to have had your help.

As a general note, It seem to me that Dual Body is not really ready for prime time. For example yesterday that I installed the second intellichem suddenly the OCP got all confused and Pool circuit started to control Spa's relay and Spa circuit got kind of stuck. Very weird. Resetting and power off the whole thing did nothing so I had to factory reset the OCP and now things are back to normal (I'm quite expert at configuring the whole thing from scratch now). Particularly Schedules is something that seem to throw the whole system a bit out of whack. Hopefully new firmware from Pentair would solve some of the issues. Anyways, just venting I guess.

Two questions: 1) Is there an Amazon locker close where I can send a little but well deserved token of appreciation? and 2) I have other minor observations about dashPanel that I would like to pass to you as well as a couple feature requests. What is the best way to pass those to you?

I`ll keep monitoring the system and get back to you in case I have any other issues. I really appreciate all the effort and help so many many thanks!

Manuel,

On Thu, Nov 18, 2021 at 12:27 PM rstrouse @.***> wrote:

That is crazy. So far in all of this we have had the OCP reporting the pool circuit correctly on the status message. Then it reported on the heartbeat message. And finally, it reported only when a schedule did not turn it on. All this time all other circuits and features reported just like every other panel out there including the other body circuit 1(spa). Now it appears the spa is acting like the pool circuit.

The good news is that I have a pretty good idea how to fix it in short order. So pull njsPC and lets see if our spa circuit works as it should.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tagyoureit/nodejs-poolController/issues/353#issuecomment-973141627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2HSS6N7N5JTEJWD3C7GZLUMVAPVANCNFSM5FWZCE5Q .

[rstrouse]

Yeah your panel is a bit of a mystery. The reason why I say that is because the i5P is the base for all IntelliCenter systems. All the software and programming logic exists on that board and every IntelliCenter system has one. This means that an i10D is an i5P with some additional relays and sensors. All the other personality cards including the i10D do not contain any programming logic. The micro-controller, firmware, and base equipment control is the same on every system. The way the base controller knows which personality card is attached is simply by checking a circuit that has a different R value for each card.

Given all of the peripherals on the RS485 bus are universal no matter which personality card is attached so the communication over RS485 must be consistent or they will not work. So there are only 2 potential things that could be causing weirdness.

1. Pentair doesn't honor its own status outputs and is acquiring the relay status from the other 2 message outputs. This is likely given the fact that indoor and wireless control panels would not work properly on an i10D if they didn't. It might also explain why the wireless controller loses the configuration sometimes when it sleeps and the wakeup process takes a bit of time to get its poop in a group. It has to ask for all the information that it didn't have when it was in slumber.
2. There is a different hardware version of the i5P motherboard for your region. I do find it odd that on my IntelliCenter, I cannot change change from Fahrenheit to Celsius. Then again I have not messed with it at the OCP so perhaps it can only be done there. Can you change from C to F on the Pentair web interface.
3. The i10D body control (circuit 1 & 6) functions have some unintended software features (bugs) that do not set the status bytes properly in i10D mode. This is probably what is going on. Depending on whether the personality card is Shared, Single, or Dual these two circuits are managed differently. The i10D team may be the folks with 6 fingers on the left hand and 4 on the right. Hopefully Pentair releases some fixes soon.

For the dashPanel stuff you can simply post enhancement requests or unintended software features on the repo dashPanel Issues. Thanks for the offer to send me something but I really don't need anything at this time. I got involved in this project due to my own needs and as it turns out others seemed to have them as well. Bonus.