Closed alemonta closed 4 years ago
Hi, maybe the same problem as #38150 (temporary solution described there)
Hi, maybe the same problem as #38150
Yes, most probably... I found an old opened issue (still present) related to the callback error opened in May: [(https://github.com/home-assistant/core/issues/35945)]
I was writing my issue just a few minutes after you added yours: when I checked if other were having troubles with ADS integration and 0.113, it seemed I was the only one! ;) A.
I also found this issue, but unfortunately I could not make a mental connection between these issues...
I have made a quickfix locally by editing manifest.json to use pyads 3.0.7 .. .otherwise the "woman acceptance factor" would go below 0 ;)
P.
I also found this issue, but unfortunately I could not make a mental connection between these issues...
I have made a quickfix locally by editing manifest.json to use pyads 3.0.7 .. .otherwise the "woman acceptance factor" would go below 0 ;)
P.
unfortunately my knowledge about the system is VERY LOW, expecially when it comes to Python... :( A.
Please keep the issue on topic and mind our Code of Conduct. We don't accept language that may be interpreted non inclusive by parts of our community.
https://github.com/home-assistant/core/blob/dev/CODE_OF_CONDUCT.md
Thanks for your understanding.
ads documentation ads source (message by IssueLinks)
The problem
I'm using HA to aggregate info from many different platforms, but my home application is based on Beckhoff PLCs. since last update (0.113), ads variables are not working anymore: I get all the variables read from PLC as unknown or false o 0. Checking the log, it seems an issue related to ADS implementation of callback notification with wrong buffer size of the return value (the log is below in the issue report). In order to avoid messy logs and to narrow the most the problem, I reduced the configuration down to the read of just 1 single udint var.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information