OMG bridge loses connection on Broker restart

Montreal666 · December 16, 2020, 1:33am

For some reason, if I stop my broker and restart it, OMG wont reconnect ( v0.95 on hacked Sonoff bridge) . I have to disconnect/reconnect the Sonoff bridge for OMG to come back online. What is the intended behavior when broker connection is lost and can I configure/troubleshoot it in any way?

Thanks!

1technophile · December 16, 2020, 1:41am

hello,

You let your broker stopped how long?

Montreal666 · December 16, 2020, 2:18am

Only a few minutes;
Also have
OMG on ESP32/BLE,
Tasmota/Portisch on an identical Sonoff bridge,
and RTL_433 on a SDR dongle.
All reconnect except OMG on Sonoff…
A simple reset and it reconnects, could there be some “heartbeat” feature involved ?
Worst case is there a way to soft reset the unit remotely ; I’ve seen such a command in your docs but only ESP compatible ?

1technophile · December 16, 2020, 10:41am

You are using which modules with the direct mod ?

Montreal666 · December 16, 2020, 1:26pm

Using Pilight ( v0.95 on hacked Sonoff bridge)

1technophile · December 16, 2020, 9:58pm

You are not alone:

github.com/1technophile/OpenMQTTGateway

Pilight doesn't reconnect after MQTT broker restart

opened 08:52AM - 04 Sep 20 UTC

closed 10:15AM - 09 Jan 22 UTC

melyux

wontfix

Before submitting a problem please check the troubleshooting section https://do…cs.openmqttgateway.com/upload/troubleshoot.html **Describe the bug** I run the BME280 and the Pilight modules together on the same device with OMG. I turned off my MQTT server for a couple of hours and then turned it back on, and the BME280 sensor carried on sending readings to the MQTT broker after the broker came back up. However, the Pilight module stopped sending received signals to the MQTT broker. I had to send a `{"cmd":"restart"}` to the `home/OpenMQTTGateway/commands/MQTTtoSYS/config` topic to get the Pilight readings coming through again. Maybe related to #550, but that was fixed... maybe they were using a different RF module other than Pilight and the fix only worked for that? **To Reproduce** Steps to reproduce the behavior: 1. Enable the Pilight module and use it with some 433MHz sensors. 2. Turn off the MQTT broker for a few seconds. 3. Turn the MQTT broker back on. 4. Observe the `home/OpenMQTTGateway/PilighttoMQTT` topic to see that Pilight messages no longer come through. **Expected behavior** Pilight messages should resume being sent to the MQTT broker after a broker outage. **Screenshots** N/A **Environment (please complete the following information):** * OpenMQTTGateway version used (V0.9.3, 0.8, development): 0.9.4 * Library version related to the problem you have: Pilight **Additional context** Running on Wemos D1 Mini with superheterodyne receiver and BME280 pressure sensor. * You should not have a compilation error if you use the versions of the libraries linked into the libraries folder, this badges show you the state of the compilation [![Build Status](https://github.com/1technophile/OpenMQTTGateway/workflows/Build/badge.svg?branch=master)](https://github.com/1technophile/OpenMQTTGateway/actions) * If you are not sure this is a bug or an enhancement post your question to the forum below [![Community forum](https://img.shields.io/badge/community-forum-brightgreen.svg)](https://community.openmqttgateway.com)

Is it possible to try this branch please?

Montreal666 · December 16, 2020, 10:04pm

Thx for the reply, will try to find some time to reflash and report back.

Btw is this command available on the OMG sonoff bridge/pilight combo as it would be easy for me to automate it as a last resort:

" . I had to send a {"cmd":"restart"} to the home/OpenMQTTGateway/commands/MQTTtoSYS/config topic to get the Pilight readings coming through again.