-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMI modbus readings are partly unsuccessfuly / console readings are not #9644
Comments
Please close this and open it in Gemu2015 github. |
My problem exists with current Tasmota with SMI - no matter whether the upcoming feature is in place. I adjusted the ticket to reflect this. |
don't get your point clearly. Keep in mind that, depending on a particular MODBus device the meter response delays may vary. there are devices that need several 100 milliseconds to respond. Thus the poll rate must be adjusted to the response time of the meter simply type sensor53 d1 in console to debug if poll rate is appropriate if not your poll rate is too small |
With the above mentioned extended script I just tried your command which gave me:
A few responses are split across lines. Does this mean the response was not understood by SMI? If I manually connect them again I get:
This manual view still misses one response around "22:05:04 : f7 03 1c ..." (the long line). Anything I can try to adjust? |
If I change
|
As long as you have Sensor53 d1 active, the webdisplay won’t get updates. You have to switch of the raw output first with Sensor53 d0 |
as @kugelkopf123 mentioned to view values in the GUI again you must switch off debug mode. there is always the possibility to miss a value due to hardware glitches but since the MODBus is checksum protected you won't get false values. to speed up web gui there would be the option to set webrefresh to a lower value. however this could lead to an overload of the cpu and i would not recommend it. |
You are correct, without |
PROBLEM DESCRIPTION
I connect my modbus device (Trovis 5573) to my ESP-01 at the default pins. I compiled Tasmota 9 including SMI.
When I use Tasmota without SMI I can send manual modbus request and each is answered properly.
When I have the script request values it takes a few tries until it eventually succeeds (roughly 3 tries till web UI shows device values).
REQUESTED INFORMATION
TO REPRODUCE
FYI that my setup works flawlessly without SMI:
serialsend5 F70300000001909C
-->{"SerialReceived":"F7030215C5BE92"}
, request: get device type, response: 5573EXPECTED BEHAVIOUR
Every modbus request initiated by script succeeds like at console.
SCREENSHOTS
n/a
ADDITIONAL CONTEXT
Most simple scripts...
and extended scripts...
need roughly three tries till values get updated.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: