Cheers Joe. This has been impacting me too.
Sent from my iPhone using Tapatalk
Stopped plugin MQTT Connector
Upgrading plugin MQTT Connector to newer version 2022.1.1 (previous version moved to trash)
Loading plugin "MQTT Connector 2022.1.1" using API v3.0
Starting plugin "MQTT Connector 2022.1.1" (pid 44258)
Started plugin "MQTT Connector 2022.1.1"
MQTT Connector MQTT local broker: Starting Device
MQTT Connector Shelly connector: Starting Device
MQTT Connector Shelly NG connector: Starting Device
MQTT Connector Shelly connector: Subscribing to: shellies/# (0)
MQTT Connector Shelly NG connector: Subscribing to: shellies-ng/# (0)
MQTT Connector Warning getPluginList: Unable to parse plist, skipping: /Library/Application Support/Perceptive Automation/Indigo 2022.1/Plugins/PingSensor.indigoPlugin/Contents/Info.plist, err = not well-formed (invalid token): line 21, column 61
7 Feb 2023 at 08:16:02
Reloading plugin "MQTT Connector 2022.1.1" using API v3.0
Stopping plugin "MQTT Connector 2022.1.1" (pid 44258)
MQTT Connector MQTT local broker: Stopping Device
MQTT Connector MQTT local broker: Disconnecting
MQTT Connector Shelly connector: Stopping Device
MQTT Connector Shelly connector: Disconnecting
MQTT Connector Shelly NG connector: Stopping Device
MQTT Connector Shelly NG connector: Disconnecting
Stopped plugin "MQTT Connector 2022.1.1"
Starting plugin "MQTT Connector 2022.1.1" (pid 44328)
Started plugin "MQTT Connector 2022.1.1"
MQTT Connector MQTT local broker: Starting Device
MQTT Connector Shelly connector: Starting Device
MQTT Connector Shelly NG connector: Starting Device
MQTT Connector Shelly connector: Subscribing to: shellies/# (0)
MQTT Connector Shelly NG connector: Subscribing to: shellies-ng/# (0)
berkinet wrote:...UPDATE: I have added a trigger to catch any MQTT Connector disconnects and restart the plugin and send me a log snippet.
FlyingDiver wrote:Ok. I have been running the Broker in an interactive shell...It's possible it's a problem with the Broker plugin. Unfortunately, due to the way that asyncio works, errors in the async code doesn't get reported via the Indigo log. If you think there's an issue there, you should run the plugin in an interactive shell. To do that, you need to check the "Enable debugging menus" in the Plugins panel of the Indigo preferences.
Starting shell for plugin MQTT Broker.indigoPlugin.
To access the plugin instance use the global named self.
Python 3.10.2 (v3.10.2:a58ebcc701, Jan 13 2022, 14:50:16) [Clang 13.0.0 (clang-1300.0.29.30)]
Connected to Indigo Server v2022.2.0, api v3.2 (localhost:1176)
Started Plugin MQTT Broker v2022.1.0
>>>
MQTT Connector Error CM MQTT Connector: Disconnected with result code 1
Trigger Monitor MQTT Connector
Reloading plugin "MQTT Connector 2022.1.1" using API v3.0
Stopping plugin "MQTT Connector 2022.1.1" (pid 4355)
Email+ sending email 'MQTT Connector plugin' to 'foo@bar.com' using Google SMTP+
MQTT Connector CM MQTT Connector: Stopping Device
MQTT Connector CM MQTT Connector: Disconnecting
Stopped plugin "MQTT Connector 2022.1.1"
Starting plugin "MQTT Connector 2022.1.1" (pid 74487)
Started plugin "MQTT Connector 2022.1.1"
MQTT Connector CM MQTT Connector: Starting Device
MQTT Connector CM MQTT Connector: Subscribing to: cm/LinkTap_reply/down (0)
MQTT Connector CM MQTT Connector: Subscribing to: cm/LinkTap/up/# (0)
MQTT Connector CM MQTT Connector: Subscribing to: # (0)
Schedule trigger "Monitor MQTT Connector" (delayed action)
MQTT Connector Error CM MQTT Connector: Disconnected with result code 1
Users browsing this forum: No registered users and 4 guests