search

FlyingDiver / Indigo-MQTT

MQTT plugin for Indigo Home Automation system
The Unlicense
2 stars 0 forks source link

Broker plug-in load requirement #21

Closed smuseby closed 1 year ago

smuseby commented 1 year ago

I am replacing the installed Insteon devices with Shelly controls. FWIW, I've noticed that every time I cycle a circuit breaker, that Indigo is unable to operate any Shelly devices until I reload the Broker plug-in (turning the breaker back on coincides with a new Shelly device on my LAN). (My Indigo server is not on the breakers I've cycled). Is it possible that adding a new Shelly device is disrupting the Broker? Before reloading the Broker plug-in, I've noticed that the Connector has a green light. I've created a trigger that sends an email when the Connector is restored - after reloading the Broker, after about 1 min, I receive an email that the Connector has been restored. I hope this helps. Bob

FlyingDiver commented 1 year ago

I'm going to see the logs for when that's happening. Both the Broker and the Connector plugins. It's more likely that something is messing up the Connector than the Broker.

smuseby commented 1 year ago

You want my logs? I've set the plugins to the lowest level. If you want my logs, what level of logging do you need?

On Tue, Apr 25, 2023 at 3:45 PM Joe Keenan @.***> wrote:

I'm going to see the logs for when that's happening. Both the Broker and the Connector plugins. It's more likely that something is messing up the Connector than the Broker.

— Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-MQTT/issues/21#issuecomment-1522512463, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3AW76BCJN5OZS7I6PTXDBHXFANCNFSM6AAAAAAXLTUTWQ . You are receiving this because you authored the thread.Message ID: @.***>

--

Robert Smith h - 510.524.0080 m - 510.529.1995

FlyingDiver commented 1 year ago

Regular Debug should work.

smuseby commented 1 year ago

I replaced 4 devices today, and cycled the power many times with no Broker disconnects. I'm wondering if previously, the issue might have been caused by cycling the power on a circuit that included a WAP.

On Tue, Apr 25, 2023 at 6:51 PM Joe Keenan @.***> wrote:

Regular Debug should work.

— Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-MQTT/issues/21#issuecomment-1522645889, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3AND4RPKC23VBWZ7QLXDB5QZANCNFSM6AAAAAAXLTUTWQ . You are receiving this because you authored the thread.Message ID: @.***>

--

Robert Smith h - 510.524.0080 m - 510.529.1995

FlyingDiver commented 1 year ago

Certainly anything that interrupts your LAN connections could cause that error.

smuseby commented 1 year ago

My Broker failed this morning, but it was not associated with power loss. I can narrow the failure down to 3 hours. If you would like my debug event log, can you suggest where I might find the 'needle in my haystack'?

On Thu, Apr 27, 2023 at 7:23 PM Joe Keenan @.***> wrote:

Certainly anything that interrupts your LAN connections could cause that error.

— Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-MQTT/issues/21#issuecomment-1526887735, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3BZ6Q64FZJM44OBILLXDMSZTANCNFSM6AAAAAAXLTUTWQ . You are receiving this because you authored the thread.Message ID: @.***>

--

Robert Smith h - 510.524.0080 m - 510.529.1995

FlyingDiver commented 1 year ago

The Broker failed, or one of the clients (Connector Plugin, etc) lost connection to it? Two different things. If the Broker actually failed there should be a log message in there somewhere. Otherwise the Broker does very little logging.

It might be worth setting up a different Broker (Mosquitto in Docker, for instance) and using that to see if the problem goes away or continues.

smuseby commented 1 year ago

I concluded that the Broker was at fault because reloading the Broker plug-in fixed the issue. I had two MQTT failures last night, both fixed with the Broker plug-in reload. Unfortunately, with debug logging set for both plugins, the event log maxed out 19 hours before the failures. I can't find a plug-in for Mosquitto On Docker. Is it obvious how to configure it to work with your Connector plug-in in Indigo?

On Sat, Apr 29, 2023 at 2:43 PM Joe Keenan @.***> wrote:

The Broker failed, or one of the clients (Connector Plugin, etc) lost connection to it? Two different things. If the Broker actually failed there should be a log message in there somewhere. Otherwise the Broker does very little logging.

It might be worth setting up a different Broker (Mosquitto in Docker, for instance) and using that to see if the problem goes away or continues.

— Reply to this email directly, view it on GitHub https://github.com/FlyingDiver/Indigo-MQTT/issues/21#issuecomment-1528879287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH5RS3A5YXKLCKND242GTX3XDWDQZANCNFSM6AAAAAAXLTUTWQ . You are receiving this because you authored the thread.Message ID: @.***>

--

Robert Smith h - 510.524.0080 m - 510.529.1995

FlyingDiver commented 1 year ago

Since reloading the Broker forces the client to reconnect, that's not definitive.

There is no plugin for Mosquitto. If you've never used Docker than that might not be the best solution. If you do get it running, you would just need to configure the Connector device to point to the (new) broker.

Without logs, there's nothing I can do about this. No one else has reported anything like this.