borpin
(Brian Orpin)
12 November 2022 07:50
21
You need to post it as text, please.
[edit]
The info does need to make sense. Looks like the emoncms log level isn’t set to DEBUG.
You always get those warnings.
a23452533:
I’d left that docker running. As soon as I shut it down, the inputs on emonpi started working properly again, with no delay, and the mqtt connection error on emonpi stopped appearing in the log.
So is the time on the Docker MQTT, correct?
I’m unclear what settings you have on MQTT Brokers, emoncms & emonhub.
emonhub → Docker MQTT ← Emoncms - there is a delay
emonhub → EmonPi MQTT ← emoncms - no delay
If so looks like an issue with your Docker MQTT setup.
Did you change the settings for emonhub & emoncms to point to that Broker & restart both or did you just stop the Docker?
ah sorry I haven’t been clear.
Here’s what I had. The dotted lines show the 2nd instance (docker) of emoncms connected to my primary MQTT. When I shut the docker emoncms down then the problems disappeared.
borpin
(Brian Orpin)
19 November 2022 05:05
23
Quite possibily, the NAS does not have the processing power to do both then.