Open source Home Automation System
https://forum.domoticz.com/
Code: Select all
sudo apt update
sudo apt install libmodbus-dev
sudo git clone https://github.com/gitaeuber/mbrtu.git
cd /mbrtu
sudo make
sudo make install
My system support only TCP/IP Modbus not RTU..
I also get these random modbus errors, but I'm using modbus TCP.Alain wrote: ↑Thursday 01 July 2021 0:39I'm getting these errors too (at least every day at random times). I have already set the polling rate to different intervals for each hardware device and I just added a 120 ohm resistor (although the lengths are short), but that didn't help either. I'm thinking about disabling the autopolling (disable the heartbeat part in the script) too and calling from a separate script. I currently have 15 devices reading from 2 different heat pumps.KrisWp wrote: ↑Saturday 17 April 2021 21:38No specific error. But the values I received are sometimes 0.andrehj wrote: ↑Saturday 17 April 2021 20:16
What error do you get when "the modbus flips"?
I also had many unexplained modbus errors. Sometimes there were hours without them, and then they would reappear at 12 minute intervals. Could not find an explanation, but all of these errors disappeared when I installed a 120 Ohm resistor on both ends of the RS485 bus, even though my bus is only 6 meters long (I use AWG23 twisted pair).
Everywhere you read that these resistors are only needed for very long lengths, but in my case they solved all modbus errors.
With another commandline tool (sdm120c), also bad results at the moment Domoticz return zero’s.
Resistors are also in place...
Is there a way to tune the polling? Or to disable autopolling and initiate it from script?
My problem seem to be different. I tried restart, but got lots of errors. So what I did I set different polling rates for different parameters, prime numbers from 11 to 43 seconds. I suspect PLC (Siemens LOGO!) doesn't handle well several modbus request at same time. Mostly works. I only get errors when multiple parameters are read about the same time.Alain wrote: ↑Monday 25 April 2022 10:52 I "solved" my problems by setting a crontab to restart Domoticz every 6 hours. This works for me, but I have to say that I don't run any other process on this pc. It's a remote server that only runs modbus for the heat pumps.
Restarting Domoticz every 6 hours ensures I don't have any errors from requests running simultaneously. This shows that that is the problem I and others have/had.
Code: Select all
@@ -173,6 +173,8 @@
import Domoticz
import sys
import pymodbus
import time
import random
from pymodbus.client.sync import ModbusSerialClient # RTU
from pymodbus.client.sync import ModbusTcpClient # RTU over TCP
@@ -324,6 +326,7 @@ def onDisconnect(self, Connection):
Domoticz.Log("onDisconnect called")
def onHeartbeat(self):
time.sleep(random.random()*5)
Domoticz.Log("onHeartbeat called")
Is this true anymore? If I add constant sleep (for example 1 second) in onHeartbeat call I still get these errors. IMO this indicates that multiple plugin threads are running at same time. Is there a way to prevent an plugin instance from executing if another one is already running?The following things should not be attempted using the Python Framework:
Waiting or sleepingin Domoticz callbacks. Plugin callbacks are single threaded so the whole plugin system will wait.
Code: Select all
sudo service domoticz stop
sudo sqlite3 -header -list /home/pi/domoticz/domoticz.db "UPDATE Hardware set Enabled = 0 where ID = 8"
sudo servive domoticz start
Works fine for me. Only issue is you have to add new hardware for each device, or register and if a hardware device polls its slave at the same time as another hardware device does this, you get errors. You can set a different poll rate for each hardware device but 10 seconds is not always precisely 10 seconds so after a while, they cross. I solved this by restarting Domoticz 4 times a day via a crontab. Works for me because I run Modbus on a dedicated remote server computer.
Sorry, I don't have any experience with this repository. I use the repository from user Domoticx.simat wrote: ↑Sunday 06 November 2022 18:18
I editted "CLOSE_PORT_AFTER_EACH_CALL = True" in domoticz/plugins/SDM120Modbus/minimalmodbus.py - from the following plugin https://github.com/remcovanvugt/SDM120M ... icz-plugin to get rid of the open port issue.
This plugin has been running fine for over a year.
Yes, thats was installed.Alain wrote: ↑Sunday 06 November 2022 18:00 Have you installed module pymodbus?
https://pypi.org/project/pymodbus/