-
Notifications
You must be signed in to change notification settings - Fork 28
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
Instance does not start after upgrading from v6.1.0 to 6.2.3 #539
Comments
And you are sure that it is not the devcie which has issues? |
when I go back to 6.1.0 it works. Device is reachable. Config wasn't changed.
|
I had the same problem. I was wondering why it works with my testsytem and not with my main system. In my testsytem im not using "discrete inputs". So i added an discrete input and i had the same error as described above. P.S. I'm using a WAGO 750-880 Controller. |
I have the same problem with Wago. I have no "discete inputs". If I marked "Do not align addresses to 16 bits" everything is working fine. |
The error could only come because of it: #510 |
Please try 6.3.3 and if the version works without "Do not align addresses to 16 bits" too. If it works, so the PR #510 must be checked again |
Hello, where can I get 6.3.3? With 6.3.0 it works with and without "Do not align addresses to 16 bits". |
I meant 6.3.0 |
@Q7Jensen #510 (lets discuss in this issue) I think that here: https://github.com/ioBroker/ioBroker.modbus/pull/510/files#diff-58417e0f781b6656949d37258c8b9052ed266e2eb7a5163cad7b0863e6b2916aR753 Should be |
@Dirk-Ma I think I could find the error. Please test the 6.3.1 |
@GermanBluefox |
@GermanBluefox |
@GermanBluefox Installed 6.3.2 from GitHub and instances are coming up green, I get data and can trigger the devices. Looks good now for me |
Describe the bug
When updating from v6.1.0 to v6.2.3 I get for one out of three running instances errors in log (adapter stays yellow):
from 1 up to 13
The device is a Protoss-PW11 RS485 to Wi-Fi
To Reproduce
Steps to reproduce the behavior:
happens immediatly after updating the adapter at the attempt to restart instance
Downgrading to 6.1.0 solved the issue
Expected behavior
instance should run after update of adapter
Screenshots & Logfiles
Versions:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: