platypush/platypush
Fabio Manganiello ee7407a7cc Don't create an MQTT client connection if there are no topics to subscribe.
If we open multiple connections from multiple MQTT-based backends to the
same host, with some of them having no topics subscribed, Paho-MQTT can
mess up which client is supposed to receive which message and we may end
up with lost messages on the platypush_bus_mqt/<host> topic.
2021-02-15 22:05:08 +01:00
..
backend Don't create an MQTT client connection if there are no topics to subscribe. 2021-02-15 22:05:08 +01:00
bus Refactored logging names 2020-09-27 01:33:38 +02:00
common Only stop the loop if it is set 2020-09-30 13:53:32 +02:00
config Support for Python cronjobs in scripts folder - closes #156 2020-10-13 23:25:27 +02:00
context Refactored logging names 2020-09-27 01:33:38 +02:00
cron Parse actions in cron also from list 2020-11-11 17:09:36 +01:00
event Refactored logging names 2020-09-27 01:33:38 +02:00
message Fixed backend.zigbee.mqtt to work with the new zigbee2mqtt API 2021-02-11 23:52:06 +01:00
platydock Changed base URL to platypush.tech 2021-02-05 23:18:18 +01:00
plugins Still support default host/port fallback on mqtt.publish 2021-02-12 02:20:04 +01:00
procedure Refactored logging names 2020-09-27 01:33:38 +02:00
pusher Fixed logging level setting in pusher 2018-05-29 16:43:16 +00:00
user Implemented settings page and finalized multi-user support 2019-07-19 00:50:52 +02:00
utils Support for Python cronjobs in scripts folder - closes #156 2020-10-13 23:25:27 +02:00
__init__.py Don't default on logging.INFO level if another level is set in the configuration, and apply the same logging level also to the web server [closes #162] 2021-02-13 15:13:53 +01:00
__main__.py Dashboard rewritten in vue.js 2019-07-07 20:11:32 +02:00
logger.py More robust logging system and options to disable stdout/stderr logging capture 2019-01-27 00:53:30 +01:00