Announcement

Collapse
No announcement yet.

a nill instance was returned

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • bsobel
    replied
    Originally posted by dcorsus View Post

    anything that is a real error will show when you have logging OFF. I color them as a warning to see it in the log when debug is ON. Sometimes I do it to indicate to users that their player name was changed and they shouldn't be wondering why.
    Sorry, one clarification, when you say logging off, do you mean 'Debug flag off' or do you mean the "Log Error Only Flag" flag on? If the former, I'm still seeing the warning with debug off, but currently I do not have Log Error Only on. Thanks!

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post

    Thanks, would you consider moving those to info from warning in the future, anything warning or error makes me think something is wrong
    anything that is a real error will show when you have logging OFF. I color them as a warning to see it in the log when debug is ON. Sometimes I do it to indicate to users that their player name was changed and they shouldn't be wondering why.

    Leave a comment:


  • bsobel
    replied
    Originally posted by dcorsus View Post

    Harmless, hence warning
    Thanks, would you consider moving those to info from warning in the future, anything warning or error makes me think something is wrong

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post
    Ok, copied new exe over. Restarted. Deleted all devices (from the plugin) Plugin correctly deleted all and exited (might be nice to send back some HTML saying that, as when you press ok on the overlay HTML it doesn't go away and its unclear if the plugin saw the button press or not). Shutdown HS, removed the sonos.ini and sonos.ini.bak. Rebooted, the plugin looks like it correctly found all he players (no dupes so far). Will report more later, going to let it run a few hours...

    One thing (reported before) is this log message on stereo groups. Cant tell if that is harmless or actually a problem. Shows up once for each second player in a stereo group.
    Sep-23 10:00:08 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Master Sun Room_RF supposed to = Master Sun Room
    Sep-23 10:00:08 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Massage Room_RF supposed to = Massage Room
    Sep-23 10:00:07 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = TV Room_RF supposed to = TV Room
    Harmless, hence warning

    Leave a comment:


  • bsobel
    replied
    Ok, copied new exe over. Restarted. Deleted all devices (from the plugin) Plugin correctly deleted all and exited (might be nice to send back some HTML saying that, as when you press ok on the overlay HTML it doesn't go away and its unclear if the plugin saw the button press or not). Shutdown HS, removed the sonos.ini and sonos.ini.bak. Rebooted, the plugin looks like it correctly found all he players (no dupes so far). Will report more later, going to let it run a few hours...

    One thing (reported before) is this log message on stereo groups. Cant tell if that is harmless or actually a problem. Shows up once for each second player in a stereo group.
    Sep-23 10:00:08 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Master Sun Room_RF supposed to = Master Sun Room
    Sep-23 10:00:08 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = Massage Room_RF supposed to = Massage Room
    Sep-23 10:00:07 AM Sonos Warning Warning in ZoneNameChanged where ZoneName in Array didn't match. Found = TV Room_RF supposed to = TV Room

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post
    Sorry, just got back to the system today. Updated to the newest version in the updater, and here it the debug log.
    WOW, it takes the PI more than 5 minutes to create all new devices and completely initialize. There are no long gaps just steady work for > 5 min.
    So what happens is that after 5 minutes a discovery kicks in and that is the cause why it is trying to create duplicated devices.
    I made a small fix and attached a new version here.
    Try it out and see if that take away the duplicated device issues. You may have to delete the ini file one more time.
    Dirk
    Attached Files

    Leave a comment:


  • bsobel
    replied
    Sorry, just got back to the system today. Updated to the newest version in the updater, and here it the debug log.
    Attached Files

    Leave a comment:


  • bsobel
    replied
    Originally posted by dcorsus View Post

    Just a quick update. I did find the issue w deleting a player or all players causing the DB to get out of sync. I sporadically still see an error when the PI terminates but discussing it with Rich from HS, it appears to be a race condition and benign.

    I've been doing some more testing and I'm still trying to do a test on pushing the PI to have more than >16 (actually 17) instances to see if there is another issue, but I'm maxed out at 17 players so bsobel, I may need you to make me one more start-up log; I did add some debug statements. I can either post a beta version here or submit through the updater.

    Thoughts?

    Dirk
    Happy to do that and which ever version is easier for you to publish is fine with me...

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post

    No worries, rather deal with it and find root cause, makes the whole community better. If I nuke everything and restart, ok to cut/paste my grouping information from the INI file so I don't have to recreate those by hand?
    Just a quick update. I did find the issue w deleting a player or all players causing the DB to get out of sync. I sporadically still see an error when the PI terminates but discussing it with Rich from HS, it appears to be a race condition and benign.

    I've been doing some more testing and I'm still trying to do a test on pushing the PI to have more than >16 (actually 17) instances to see if there is another issue, but I'm maxed out at 17 players so bsobel, I may need you to make me one more start-up log; I did add some debug statements. I can either post a beta version here or submit through the updater.

    Thoughts?

    Dirk

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post

    No worries, rather deal with it and find root cause, makes the whole community better. If I nuke everything and restart, ok to cut/paste my grouping information from the INI file so I don't have to recreate those by hand?
    OK, embarrassing but issue of delete single and delete all was in my PI. Thanks to Rich who quickly confirmed everything looked kosher on the HS3 side of the house which motivated me to look a bit harder. So this is going to be fixed soon.
    During my debugging I might have seen something else that needs further investigating. I stumbled onto some "instances" array that has a max capacity of 16, so either it adjusts its own capacity (need to test tonight) or having more than 16 players is causing mayhem.

    Stay tuned.

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post

    No worries, rather deal with it and find root cause, makes the whole community better. If I nuke everything and restart, ok to cut/paste my grouping information from the INI file so I don't have to recreate those by hand?
    Yes you can cut/paste all linkgroupinfo.
    Have email into rjh
    Even deleting a single player causes the PI to be terminated by HS before or while entries in the .ini file are being deleted, causing all kind of mayhem.
    Tried to turn option to "load PI in background" off but made no difference.

    Dirk

    Leave a comment:


  • bsobel
    replied
    Originally posted by dcorsus View Post

    hmmmm ..... my worst fears ..... delete-all-players is broken again, something with HS!!!
    I brought all my Sonos devices on-line (19) and see immediately issues with delete-all.
    I have been doing some moving this afternoon and my dev environment is down. I see that you have duplicated devices now, even more so due to the issues with delete-all.
    Suggest you stop hs3, delete the .ini file which is a cleaner way to start fresh (unless we have issues here with HS3 as well).
    I did notice that the initialization took for ever and I had some players without names as well, I'll play with my 19 players some more.
    I'll post some updates as soon as I can, but I may have to consult Rich who a bit ago made some changes with PI init (and I guess shutdown) and I suspect something got broken.
    Sorry for the bad news, stay tuned,
    Dirk
    No worries, rather deal with it and find root cause, makes the whole community better. If I nuke everything and restart, ok to cut/paste my grouping information from the INI file so I don't have to recreate those by hand?

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post
    Yes, I did the delete all. The plugin exited as you said it would. HS tried to restart it automatically it but I got the 'instance cant be found....' so I restarted HS at that point

    Sonos.ini.bak attached.
    hmmmm ..... my worst fears ..... delete-all-players is broken again, something with HS!!!
    I brought all my Sonos devices on-line (19) and see immediately issues with delete-all.
    I have been doing some moving this afternoon and my dev environment is down. I see that you have duplicated devices now, even more so due to the issues with delete-all.
    Suggest you stop hs3, delete the .ini file which is a cleaner way to start fresh (unless we have issues here with HS3 as well).
    I did notice that the initialization took for ever and I had some players without names as well, I'll play with my 19 players some more.
    I'll post some updates as soon as I can, but I may have to consult Rich who a bit ago made some changes with PI init (and I guess shutdown) and I suspect something got broken.
    Sorry for the bad news, stay tuned,
    Dirk

    Leave a comment:


  • bsobel
    replied
    Yes, I did the delete all. The plugin exited as you said it would. HS tried to restart it automatically it but I got the 'instance cant be found....' so I restarted HS at that point

    Sonos.ini.bak attached.
    Attached Files

    Leave a comment:


  • dcorsus
    replied
    Originally posted by bsobel View Post
    Here you go. Saw that the Massage Room device was already duplicated, also noticed that the player table didn't have names for many and IPs for some devices...
    hmm, when the PI comes on, there are still players in the .ini file, did you do the delete all?
    Could you post the .bak log file (which is post to restart).

    Leave a comment:

Working...
X