PG3 MQTT errors?

[DaveStLou]

I haven't been in to look at ISY on Polisy in awhile. When I did today, I found the PG3 controllers and all their nodes empty.  I found the System Log full of errors like below:

11/2/2021, 16:58:20 [pg3] error: MQTT on Inbound processFunction: TypeError: Cannot read properties of undefined (reading 'status')
    at setDriver (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/nodeserver/status.js:178:20)
    at runMicrotasks (<anonymous>)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at listOnTimeout (node:internal/timers:526:9)
    at processTimers (node:internal/timers:500:7)
    at async Promise.all (index 0)
11/2/2021, 16:58:20 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:52:bf:24,9] :: {"error":"No valid API calls provided","message":"{\"set\":[{\"address\":\"controller\",\"driver\":\"GV1\",\"value\":\"58\",\"uom\":0}]}"}
11/2/2021, 16:58:20 [pg3] error: [00:0d:b9:52:bf:24_9] status set :: TypeError: Cannot read properties of undefined (reading 'status')
    at setDriver (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/nodeserver/status.js:164:18)
    at async Promise.all (index 0)
11/2/2021, 16:58:20 [pg3] error: MQTT on Inbound processFunction: TypeError: Cannot read properties of undefined (reading 'status')
    at setDriver (/var/polyglot/node_modules/@universaldevices/pg3/lib/modules/nodeserver/status.js:178:20)
    at async Promise.all (index 0)
11/2/2021, 16:58:20 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:52:bf:24,9] :: {"error":"No valid API calls provided","message":"{\"set\":[{\"address\":\"controller\",\"driver\":\"GV9\",\"value\":\"440218\",\"uom\":0}]}"}

The Nodeserver logs are full of errors similar to this:

2021-11-02 16:48:05,359 MQTT       udi_interface.interface ERROR    interface:_message: error No valid API calls provided
2021-11-02 16:48:05,360 MQTT       udi_interface.interface ERROR    interface:_message: Invalid command received in message from PG3: 'message' {"set":[{"address":"forecast_6","driver":"GV13","value":"803.0","uom":25}]}
2021-11-02 16:48:05,449 MQTT       udi_interface.interface ERROR    interface:_message: error No valid API calls provided
2021-11-02 16:48:05,450 MQTT       udi_interface.interface ERROR    interface:_message: Invalid command received in message from PG3: 'message' {"set":[{"address":"forecast_6","driver":"GV20","value":"0.132","uom":106}]}

Not sure of the root cause but it appears the MQTT server is not responding as expected.

[bpwwer]

Try restarting the ISY.  This looks like the same issue reported on Slack and for that case, it appears the ISY is simply refusing connections from PG3.

[DaveStLou]

3 minutes ago, bpwwer said:

Try restarting the ISY.  This looks like the same issue reported on Slack and for that case, it appears the ISY is simply refusing connections from PG3.

I tried that and rebooting the Polisy, but no change. I tried again just now, no joy.

[bpwwer]

I've been able to reproduce the errors by changing the ISY configuration in PG3 to use an incorrect port.  You might want to try just  re-entering the port number and saving from the ISY/edit current ISY screen in PG3.

[bpwwer]

I believe the root cause of this has been determined.  It looks like the most recent version of node broke something with host name resolution. Specifically it fails to properly resolve 'localhost' to 127.0.0.1.

To resolve the issue in PG3, replace 'localhost' in the ISY configuration IP field with '127.0.0.1' and save it.

[MBell]

Could you tell me what the MQTT port # should be?

 

Thank you,

[bpwwer]

5 hours ago, MBell said:

Could you tell me what the MQTT port # should be?

 

Thank you,

Context?

This thread is about PG3 MQTT errors and PG3 doesn't have a user configurable MQTT port setting.  This looks like it is probably from PG2, in which case the default setting is 1883.