Announcement

Collapse
No announcement yet.

a nill instance was returned

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

  • dcorsus
    replied
    Originally posted by bsobel View Post
    Im seeing the same thing. I wound up resetting everything, creating new devices (after fresh .ini file etc). All was good but today my log is again flooded with "Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance" Now the plugin shows the correct zones and everything seems to be working, so the error feels noise but wanted to let you know...
    Could you turn debug on, restart HS, capture log and post here together with .ini file?

    Leave a comment:


  • bsobel
    replied
    Im seeing the same thing. I wound up resetting everything, creating new devices (after fresh .ini file etc). All was good but today my log is again flooded with "Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance" Now the plugin shows the correct zones and everything seems to be working, so the error feels noise but wanted to let you know...

    Leave a comment:


  • dcorsus
    replied
    Originally posted by pcourt View Post
    I am having the same problem. How did you know which instance of the player to delete? Or does it matter?
    Never delete players from the HS devices management page!

    Make sure you are on the 3.1.x.x PI version not the end-of-life'd 3.0.x.x. stream (because delete players is broken there due to post release changes in HS)

    Assuming you are on 3.1.x.x release stream, I would delete the player from the plugin's config page in the device player table. If you had events (on the original players), they are corrupted anyway so if you delete the wrong player and it comes back, delete both and the player will be rediscovered and come back and that should be the end of it (I think!).

    If not:

    Stop hs
    delete sonos.ini file
    restart hs

    Leave a comment:


  • pcourt
    replied
    I am having the same problem. How did you know which instance of the player to delete? Or does it matter?

    Leave a comment:


  • w.vuyk
    replied
    That is not the case here. No devices were erased today. But it appears that after the upgrade of HS3 the sonos plugin has created double root devices. I have stopped the plugin here, removed the doubles and deleted the ini file.
    Then with a restart of the plugin the errors were gone again and all seems to function normal again.

    Guess there has been a hickup during the upgrade?

    Wim

    Leave a comment:


  • wadesready
    replied
    I had problems after the latest windows 10 update. it did the update while I was away, killed homeseer and corrupted everything, wiped out all my zwave devices and gave me errors on a reboot with sonos. lucky and thanks to blade I had a good backup. I restored with the backup, rebooted and everything was fine. updated to the latest .425, and did another backup. I hope setting windows 10 to a metered connection stops the updates until I am ready....

    Leave a comment:


  • w.vuyk
    started a topic a nill instance was returned

    a nill instance was returned

    Dirk,

    After upgrading to HS3 3.0.0.425 I keep getting groups of errors every 5 minutes in the log regarding the Sonos plugin:

    Code:
    apr-12 14:45:58	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DE13DA01400
    apr-12 14:45:48	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5FDE201400
    apr-12 14:45:38	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DB2DDE01400
    apr-12 14:45:28	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5F07401400
    apr-12 14:45:00	 	regenkans	er valt 0,1 mm/u om 14:55
    apr-12 14:40:56	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DE13DA01400
    apr-12 14:40:46	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5FDE201400
    apr-12 14:40:35	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DB2DDE01400
    apr-12 14:40:25	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5F07401400
    apr-12 14:40:00	 	regenkans	er valt 0,21 mm/u om 14:40
    apr-12 14:39:38	 	Event	Event Trigger "Tuin Tuinpomp uit"
    apr-12 14:35:53	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DE13DA01400
    apr-12 14:35:43	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5FDE201400
    apr-12 14:35:33	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_B8E937DB2DDE01400
    apr-12 14:35:23	 	Sonos Error	Error in CreateOneSonosController while instantiating the SonosPlayerInfo a nill instance was returned for UDN = uuid:RINCON_5CAAFDF5F07401400
    Any idea what might be causing this?

    Wim
Working...
X