DaveStLou

Migrating to PG3x did indeed fix the problem. Volumio reinstalled.

Since I use this daily, I fired up the Volumio integration in Home Assistant. Still have some bugs getting the Pandora stations to show up correctly as input selections but it's workable. So at least I have a viable workaround via Home Assistant.

So what's the next step in troubleshooting?

Good thought but alas, no difference. On a whim I tried disabling Pi-hole while installing. Also, no difference. I have a backup of Polyglot from a few days ago, should I try restoring that? Any downside or risk?

I had tried that a couple of times before posting. I've also tried rebooting and installing it in a different slot. Same results. Very strange. Any other thoughts?

This week Volumio was not responding properly so I decided to delete and reinstall my Volumio nodeserver. However, it never shows "connected". I am running PG3 3.1.21, Frontend 3.1.21 and IoX 5.6.0 on my Polisy. When I attempt to view the nodeserver logs is get this message: Looking into Polyglot log file (relevant piece attached) I found this line which complains about not being able to find volumio.py: 5/28/2023, 12:26:10 [pg3] error: [Volumio(1)] :: STDERR: python3: can't open file '/var/polyglot/pg3/ns/000db952bf24_1/./volumio.py': [Errno 2] No such file or directory Is there something I need to do differently to install nodeservers under the new PG3 version? log_excerpt.txt

I don't think it was always this way but the Triggered state on my two PTZ cameras is showing as a 0 when False and 1 when True. All of my other Fixed cameras are showing correctly. Is anyone else seeing this? I'm not sure if it's a bug or something in the way I have them set up in Blue Iris.

Very interesting. I had 3 or 4 "reboots" of my Polisy earlier this week. I have a program that sends me a Pushover notice - very similar to your email. I have not opened a ticket but I have reviewed the logs and haven't found anything obvious. In the meantime I've ordered a new power supply from UDI. It's on its way.

That was it. Thanks!

I noticed this some time yesterday that my WeatherPoly Node Server was offline. On the dashboard, I found it's displaying a notice "Failed to start weather monitoring service." Looking at the log, I found "Web server failed to start: [Errno 48] Address already in use" I haven't changed anything on my configuration and I confirmed the port is correctly configured as "8188" I use this NS to receive information from my weewx software and also, haven't made any changes over there. Via ssh, I found this in the port list which looks correct to me: USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS polyglot python3.9 77205 5 tcp4 *:8188 *:* What's the correct way to recover from this? Restarting the Node Server hasn't worked. Thanks!

You can find the PG3 version on GitHub here: https://github.com/exking/udi-mqtt-pg3

Not sure what you mean by "source code for the node servers" but the configuration page on PG3 is the same as PG2. I use devlist but devfile is listed as an option - I've just never used it.

Currently, the NS groups my Pandora stations first and then my Playlists. Would it be possible to place the Playlists first (which change less often) and then the Pandora stations? Since this may not be everyone's preference maybe via a configuration option? In my case, when Pandora stations are created (sometimes accidentally) outside of Volumio, any programs that reference a playlist are affected (since the NS inserts the station above the playlists). If I'm not making this clear, I can provide an example.

I'm not @xKing but yes, it does.

I had already tried moving then closer to my Polisy. Factory reset was the key. These are white label plugs I bought from Monoprice so long ago, I didn't remember how to do so on them but plugging them in while pressing the on button seemed to do the trick.

I have a few unbranded z-wave devices I use only at Christmas which I disable for most of the year. This is the first year I've tried to use them on my Polisy with Zooz dongle. I was able to re-enable two of them without issue but the other two were not responding. I removed them and am attempting to re-add them. They show up in the AC but still not working. During the add process I'm seeing "Add Node failed" Cannot initialize device database for new device". Is that an error of the device or on the dongle side? Any thoughts on how to get this back on my system? Thanks!

@Michel Kohanim, Thank you. Is there somewhere you can point me for more information on the device?

I finally got to follow up with AmerenMissouri (electric company) per the closed thread below. @Michel Kohanim they are asking if the devices would be connecting to the smart meter directly to the meter, the panel, or somewhere else in the home? As I said in my original post, I'm a complete novice to smart meters and don't know the answer or even if it would make sense. Can you help me with how the 3rd party HAN device would connect?

I noticed my were working for a routine that triggered just before 2:00 PM CST today too. Hurray!

Yeah, usually. But everything else is working fine. I still think something is going on in the Alexa system, not locally.

I have had several routines fail today -- ones that have triggered without issue for as long as I can remember. I suspect it an Alexa system issue (maybe related to time change?). My wife reports that alarms she has set in the kitchen today for various amount of times, immediately go off (like right away). She tried setting one recently and Alexa responded that she's having trouble -- whatever that means.

I usually install updates via SSH but this time I decided to try the instructions in the post for PG3 v3.1.6: "In the Admin Console, click on Configuration, Upgrade Packages." My Polisy is in another part of the house so I cannot hear the beeps to indicate upgrade is complete. I waited for 15 minutes and tried to login to the PG3 dashboard but it was not found. I tried SSH and then pinging but also not found. After 30 minutes of no communication, I power cycled the Polisy. No change, no communication. I tried resetting the network connection per the wiki but the LED light never changed. I have opened up a ticket with UDI support. Good reminder for everyone. Make sure you have current backups.

@Goose66 I'd rather not rollback the firmware on my Bond Bridge. What's a realistic ETA on resolution?

I did some testing from the Polisy command line using the Get Device Information as documented in the Bond API. I was able to successfully get the device information and then the information on the connected devices. My firmware is still on v3.3.13. [admin@polisy ~]$ curl -H "BOND-Token: *REDACTED" -i http://10.42.8.89/v2/devices HTTP/1.1 200 OK BOND-Flags: 4 Content-Length: 62 Content-Type: application/json; charset=utf-8 {"_":"3cb09490","__":"00000000","708bb457":{"_":"c66fbccb"}} [admin@polisy ~]$ curl -H "BOND-Token: *REDACTED*" -i http://10.42.8.89/v2/devices/708bb457 HTTP/1.1 200 OK BOND-Flags: 4 Content-Length: 363 Content-Type: application/json; charset=utf-8 {"name":"Ceiling","type":"CF","location":"Guest Room","template":"B2","actions":["DecreaseSpeed","IncreaseSpeed","SetSpeed","StartDimmer","Stop","ToggleLight","TogglePower","TurnLightOff","TurnLightOn","TurnOff","TurnOn"],"_":"c66fbccb","__":"89a4338e","commands":{"_":"dcb6ad47"},"state":{"_":"86b7414a"},"properties":{"_":"82bde9cf"},"skeds":{"_":"00000000"}} I did find this interesting note under the 64-bit Keys heading: As of v3.0.0 firmware, Bond products have moved to 64-bit keys as resource identifiers, instead of the previous 32-bit keys. So, rather than a device being identified by an 8-digit hex string, the ids for newly created devices will be 16-digit hex strings. However, it goes on to explain that the API is "libral(sic) in what it accepts" so they still support the shorter keys (like mine is showing) so it doesn't seem that would break the node server discovery function.

Sorry, I forgot to include that I am using Android. It's working now.