PG3x - error: BOBBY: Checking client "portal-x" (x = 1 or 2)

[GJ Software Products]

PG3x 3.1.23

IoX 5.5.9

Since the AWS IoT provisioning the other day I noticed my eisy getting very chatty to AWS IoT.  Today when looking at the PG3x console I found it continually reporting "Successfully retrived IoX's from database" as if in a loop.  Review of the PG3x Log shows:

3/26/2023, 16:35:11 [pg3] error: setClientState: id = portal-1 cmd = setClientState data = {"online":true,"remote":true,"timestamp":1679873711011}
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-1"
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-2"
3/26/2023, 16:35:11 [pg3] info: Sending message to remote clients
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-1"
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-2"
3/26/2023, 16:35:11 [pg3] info: Sending message to remote clients
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-1"
3/26/2023, 16:35:11 [pg3] error: BOBBY: Checking client "portal-2"
3/26/2023, 16:35:11 [pg3] info: Sending message to remote clients

which repeats...

Does anyone have any idea what is causing all the traffic to AWS IoT (it looks like cert auth requests but I haven't dug that deep yet and then of course the repetitive "Successfully retrieved IoX's from database" messages and the "BOBBY" errors in the PG3x Log?  With one node server (Elk) why is the eisy so chatty to AWS IoT?

Thanks.   -G

[DennisC]

Possibly related to the rollout last Friday. The update was rolled back this morning.

 

 

[bpwwer]

PG3x version 3.1.23 was extra chatty as we used that to do some initial testing for PG3x remote access.  That has been removed in the latest version 3.1.24 of PG3x.