Hi,
I ran into a hard to track down issue running the plugin. I was experiencing a lot of problems updating my system and could not submit diagnostic reports to Sonos. Even going to the http://#.#.#.#:1400/support/review page would time out on some units. Sonos support couldn't track it down, even after remote controlling a system to debug the network for hours.
I eventually found that the plugin looks so much like a controller to the Sonos equipment, that the Zones were logging errors attempting to connect back to the HomeSeer server and attempting to query XML from controller to report in both diagnostics and apparently during updates. I have a very large system in one home (32 devices) and this system was the one that would time out. The cumulative time for each unit to query the 'Controller' and timeout made updating and generating the diagnostics fail.
After disabling the plugin I could both update and submit diagnostics again.
I was wondering if the plugin could either a) do something so the zones don't attempt to query it or b) if not possible, they actually open the port the zones are querying and give back some stub information to make it happy.
You can see this if you go to the support/review and open up the Controllers. You should see the plugin. Then in the logs on a Zone you should see the failed connection errors to that controller.
Best,
Bill
I ran into a hard to track down issue running the plugin. I was experiencing a lot of problems updating my system and could not submit diagnostic reports to Sonos. Even going to the http://#.#.#.#:1400/support/review page would time out on some units. Sonos support couldn't track it down, even after remote controlling a system to debug the network for hours.
I eventually found that the plugin looks so much like a controller to the Sonos equipment, that the Zones were logging errors attempting to connect back to the HomeSeer server and attempting to query XML from controller to report in both diagnostics and apparently during updates. I have a very large system in one home (32 devices) and this system was the one that would time out. The cumulative time for each unit to query the 'Controller' and timeout made updating and generating the diagnostics fail.
After disabling the plugin I could both update and submit diagnostics again.
I was wondering if the plugin could either a) do something so the zones don't attempt to query it or b) if not possible, they actually open the port the zones are querying and give back some stub information to make it happy.
You can see this if you go to the support/review and open up the Controllers. You should see the plugin. Then in the logs on a Zone you should see the failed connection errors to that controller.
Best,
Bill
Comment