Uncaught Exception During Configuration

[koensayr]

Hello There,

During my initial configuration I seem to have run into a port conflict:

Code: Select all

Dec 29, 2020 at 1:52:43 PM
   Enabling plugin "HomeKit Bridge 1.0.2"
   Starting plugin "HomeKit Bridge 1.0.2" (pid 51044)
   HomeKit Bridge                  Caching all HomeKit Bridge devices...
   Started plugin "HomeKit Bridge 1.0.2"
   HomeKit Bridge Error            Exception in httpsvr.startServer line 65: [Errno 48] Address already in use
							 CODE: self.httpd = ThreadedHTTPServer(('', port), AuthHandler)

   HomeKit Bridge Error            Unable to open port 8558 for HTTP Server

Not an issue. I'll just change the port number in the configuration. So I click in the plugins menu and then HomeKit Bridge and try to select configure. After a short rainbow spinning pinwheel, I get this exception in the logs:

Code: Select all

  Error (client)                  timeout waiting for plugin response from com.eps.indigoplugin.homekit-bridge for request UiGetValues1
   Error (client)                  timeout waiting for plugin response from com.eps.indigoplugin.homekit-bridge for request CallPluginFunc
   Error (client)                  runConfigDialog() caught exception: NSInvalidArgumentException -- *** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]
   Error (client)                  timeout waiting for plugin response from com.eps.indigoplugin.homekit-bridge for request UiGetValues1
   Error (client)                  timeout waiting for plugin response from com.eps.indigoplugin.homekit-bridge for request CallPluginFunc

[koensayr]

Interesting that during startup when I RDP to the server I get this exception:

Screen Shot 2020-12-29 at 2.40.49 PM.png (42.55 KiB) Viewed 1705 times

[koensayr]

An interesting point is that connection via a Remote Indigo UI didn't generate the above error (not that I'd expect that). I didn't see it unless I VNC to the server itself.

After enabling and applying the exclusion in the security preferences pane, I was able to cleanly start the plugin without issue.

FWIW:

MacOS: 10.15.5
Plugin Version: 1.0.2

This issue can be closed