Home Automation Domotica Forum Europe, Bwired Forum

I never heard of dbus. Probably Linux stuff I guess, which I don't use.

I do get this problem every few days: Mosquitto and OpenHAB are completely swamped with messages with 'random' data (ie all kinds of changing temperatures values, boiler on/off messages, etc.). I can't find the cause. The only thing I see is a slowly increasing CPU load (starting around 14:00 hours ...

No. And as far as I can see on an old picture, I've also used the BC557B's for my OTGW...

The BC557 is for higher voltages. For the rest it should be identical to the BC558 series.

https://www.fairchildsemi.com/datasheets/BC/BC559.pdf

Just some remarks: The gateway is not running in unknown operating mode. But if it doesn't respond to commands, otmonitor is unable to determine the mode it is in. The tclkit and exe versions run the exact same code, they are only packaged differently. If one doesn't work correctly, it is probably ...

That is very weird. So I did some extra testing for otmonitor in general and found the following: Running the exe windows version sometimes does connect to mqtt, but most of the times it doesn't The tclkit version does it right every time I use it. So that is currently the way it works on my server ...

You are great, It works :D I loaded your new mqtt-debug script and mqtt messages started to come in right away. I can also set the setpoint to control the thermostat. The only problem I have is that it seems that only changed values are sent by otmonitor, even after an disconnect/connect. And finall...

If F12 is the right function key, I will try RDP or hook up a keyboard to the server, and follow the steps you described. The gateway is stable as a rock with VR=5, so MQTT must work to integrate the otgw with Homeseer and OpenHAB 8) Got it @22:30: my message DISCONNECT Message sent to sock1488 my m...

I'm using otmonitor 4.1.1 (windows exe) and teamviewer for remote access.
F12 does nothing! The other function keys like F2-F7 work.

So either F12 is blocked by teamviewer, or F12 should be another function key. Tried F8-F12, but none of those give me the console window.

try to disable ipv6 in mosquitto, or change address to 127.0.0.1 I have no idea how to disable ipv6 in mosquitto. I'm using a secure connection for outside (owntracks) access and local port access for any client (no username/pw). I did enter 127.0.0.1 in otmonitor, but still nothing. Sending data t...

mike7 wrote:What is an output of "mosquitto_sub -t \# -v" ?

Nothing for otmonitor. I only see my testmessages send using mqttinspector and my owntracks messages, so mosquitto is running fine.

I did enable MQTT once more in otmonitor and restarted otmonitor, but still nothing...

This morning everything was still running fine. The only thing that I saw was a high CPU load on my server running otmonitor (around 25% instead of sub 1%), resulting in a 10W higher power consumption. I suspect that either otmonitor and/or the otmonitor webserver are responsible for the high CPU l...

Logs do take much of the guessing out of the equation. Your log shows Error 03 every other message, not every message. The messages from the thermostat are received correctly, only the messages from the boiler can not be understood. It is then even more surprising that the VR command fixed the issu...

I finally got it working by setting the reference voltage to 1.667 instead of the default 1.250! I didn't expect adjusting the reference voltage would help since you mentioned that "everything seems to work as expected" in monitor mode (or at least I think that's you meant). Monitor mode ...

New results :D After some hours of testing I finally got it working by setting the reference voltage to 1.667 instead of the default 1.250! While testing I had the following results: Setting IT=1 resulted in an Error 03 for every message Setting It=0 resulted in many Error 01 messages, but stopped t...