DaveStLou

Never mind. I found it under the new Purchases tab. Hopefully we're squared away now.

@Jimbo I've been using the PG3 version for some time and I just realized that I've never been prompted to pay. I think the Store offered a trial but I'm way past that. How do I trigger the purchase option so I pay?

Same here. Pandora is on almost all the time and the Pandora plugin is the reason I started using Volumio. I don't have the audio directly connected to my Raspberry Pi. Instead I'm sending it out to all my Chromecast audio via mpd2chromecast I installed on it. Has a few quirks but it works 99% of the time.

Rather than add webradio favorites, I found that I can create a playlist of a station. That works better since I might not want all of them to show up in the node sever. Same thing with Artists, or Genre - just make a playlist if I really want to use that in the node server. I wish I could make a playlist of a Pandora Station like I do the Web Radio. That way I can limit the stations to only the ones I want in the node server. The Volumio Pandora plugin doesn't support that currently though. Does the node server check for changes in Pandora stations on a regular basis or does that occur only on restart? What I'm running into is when I add or remove Pandora stations, it messes up programs that refer to that as a source - basically it's a moving target. I'm trying to figure out how to manage that better.

I'm running Volumio version 3. What items are being scanned for inclusion as "Sources" in the selection list? Currently I see Favorites (but I'm having trouble in v3 getting that to populate - I'm still learning) and my Pandora stations but I don't see my playlists.

I use the ISY Launcher but got the Polisy Administrative Console from this post:

I've been wondering the correct way to change that myself.

The ISY shows the slot empty and it hasn't dissappeared. I did find this in the log: 12/7/2021, 17:33:36 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:52:bf:24] :: [200] :: 5.979086ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 12/7/2021, 17:33:36 [pg3] error: verifyNodeServers (00:0d:b9:52:bf:24) :: Invalid response from ISY, skipping I checked the user name and password and all looked good there. Since there was nothing else there I deleted the ISY in PG3 and re-enterred it. The nodeserver is gone.

I attempted to remove all my several test node servers from PG3 connected to ISY on Polisy. In doing so I discovered there is one node server that I'm unable to remove. It's listed as "Unmanaged" on the Dashboard (see below) even though there are no Node Servers showing in the drop down menu in ISY on Polisy. I SSH'd and looked around and do not see any folders listed for my ISY on Polisy. I tried restarting both ISY and PG3 and even rebooting Polisy but it's hanging on. How do I fix this? Is there a way to clean it out of the database?

My wife and I joke about having three "assistants" at our house: "Izzy" (ISY), Alexa and now "Polly" (Polisy).

Yes, PG2 can only be pointed to one ISY. PG3 supports nodeservers on more than one ISY at a time.

While I can't answer you're question, I can tell you that "sudo service isy status" is what you want to run to see the status of the ISY service under FreeBSD which is the OS Polisy uses. Also, trying running "sudo service pg3 status" to see the status of the Polyglot v3 service.

Sent by PM

I checked "Configure Colors/Values/Icons" and it says "No User Mapped Values for this Node Property".

I'm running 0.111. This morning I noticed that it appears to be using the default icon rather than the one set under Edit Favorite:

This thread made me wonder where I stood. Discovered I have plenty of room to grow.

@asbril I still use the Holidays Google Nodeserver for a few of my programs. I had a similar experience to you last week. I found a lot of errors in the Nodeserver log in the dashboard. Restarting the Nodeserver and watching that it cleared up worked for me.

I discovered PG3 was missing from /usr/local/etc/rc.d so I reinstalled it. I have access again still checking if all is back to normal now.

Appreciate the optimistic thoughts but I suspect it will take some intervention on my part with a little help from my forum friends.

I am unable to bring up PG3 dashboard in my browser and my nodes are blank in ISY on Polisy and PG3 nodes are showing all zeros in my ISY94i. I've tried restarting polyglot and rebooting Polisy but to no avail. This occurred while in the process of deleting a PG3 Nodeserver. Appreciate help in getting PG3 up again. Thanks!

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

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.

Ahh. I was crossed up and thought you were talking about the Presence-Poly nodeserver.

That's promising. Thanks!

I've not been able to get that node server to work on Polisy. It's been awhile since I tried but as I recall, Polisy does not support the Bluetooth module the nodeserver relied on for that function. I switched to using the ping node server to identify when my or my wife's phones are on my LAN. It has a few quirks but generally has worked well for me.