Route api exceptions to the log for visibility

Not that there should be any of those in the first place.

Author: jmattsson

custom_components/powersensor/PowersensorMessageDispatcher.py

@@ -140,7 +140,6 @@ def _create_api(self, mac_address, ip, port, name):
         self._known_plugs.add(mac_address)
         self._known_plug_names[name] = mac_address
         known_evs = [
-            #'exception',
             'average_flow',
             'average_power',
             'average_power_components',
@@ -154,6 +153,7 @@ def _create_api(self, mac_address, ip, port, name):
         for ev in known_evs:
             api.subscribe(ev, self.handle_message)
         api.subscribe('now_relaying_for', self.handle_relaying_for)
+        api.subscribe('exception', self.handle_exception)
         api.connect()
 
     def cancel_any_pending_removal(self, mac, source):
@@ -162,6 +162,9 @@ def cancel_any_pending_removal(self, mac, source):
             task.cancel()
             _LOGGER.debug(f"Cancelled pending removal for {mac} by {source}.")
 
+    async def handle_exception(self, event: str, exc: BaseException):
+        _LOGGER.error(f"Plug connection reported exception: {exc}")
+
     async def handle_relaying_for(self, event: str, message: dict):
         """Handle a potentially new sensor being reported."""
         mac = message.get('mac', None)