Announcement

Collapse
No announcement yet.

Problems after replacing switch

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

    Problems after replacing switch

    This is definitely not a problem with the plug-in but...

    I just replaced a Cisco SG200-50P switch with a Ubiqiti US-48-750W. They are both 48-port POE switches. I do not have a Ubiquiti USG, I am using a pfsense router. All I did was replace the switch, nothing else. Everything is working well with HomeSeer and I can control and see all of my devices with any Sonos app (PC or iOS). When I start HomeSeer I get:
    Code:
    Starting up....
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in InitializeSonosDevices creating the UPNP Master with Error = Object reference not set to an instance of an object.
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7389
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7390
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7391
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7392
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7393
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7394
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7395
    Startup Complete, 8 errors detected, check the log for more information.
    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

    #2
    Originally posted by rprade View Post
    This is definitely not a problem with the plug-in but...

    I just replaced a Cisco SG200-50P switch with a Ubiqiti US-48-750W. They are both 48-port POE switches. I do not have a Ubiquiti USG, I am using a pfsense router. All I did was replace the switch, nothing else. Everything is working well with HomeSeer and I can control and see all of my devices with any Sonos app (PC or iOS). When I start HomeSeer I get:
    Code:
    Starting up....
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in InitializeSonosDevices creating the UPNP Master with Error = Object reference not set to an instance of an object.
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7389
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7390
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7391
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7392
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7393
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7394
    
    12/4/2017 12:27:44 PM ~!~Sonos Error~!~Error in BuildSonosInfoList. Info not found in .ini file Devtype = Player deviceReference=7395
    Startup Complete, 8 errors detected, check the log for more information.
    This doesn't look good at all, my first bet would be that the .ini file and HS database are out of whack but I can't correlate that with replacing a switch.
    Last time I saw this error, it is caused by the PI reading from it's .ini file what the HS reference is for its masterdevice, use that to establish an HS reference and HS say ...nope, this reference does not exist. Everything goes downhill from there.

    Did anything happen to the HS database?

    Dirk

    Comment


      #3
      Well, this one confuses me. I restored HomeSeer from a backup and all is well. I am at a loss as to why replacing a switch could cause a problem in the HomeSeer config when restarting.

      HomeSeer was cleanly shut down prior to replacing the switch. Apparently several ini files and the HomeSeer database were corrupted on the restart. I will post back if I find the root cause.
      HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

      Comment

      Working...
      X