-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
[MCP23017] Status changes are slow #22
Comments
Wow that's slow. It may be unnecessary to have the bus locks actually. When I decided to use the locks I was approaching it from a microcontroller perspective, but it seems the kernel provides file-like access to the bus. Side note: your first payload is 2 bytes but the state is set to |
Are you running v0.7.1? I made I tiny change to the function that acquired the bus lock so that I wouldn't have to repeat log messages. If so replace if lock:
break
else: |
To your side note: The status reported back via MQTT seems to be inverted:
The output of the MCP23017 is okay. A poll afterwards is okay:
|
Yes, I'm running 0.7.1!
|
I thought I had fixed this, I will look into it. |
You must be running the dev version to have the lock delay bug. I need to identify dev versions better in the logs... I'm going to push some commits that fix these issues, would you mind testing before I make it a release? |
I am running dev, yes. Both problems are fixed in dev now! Thank you! |
Thank you for reporting and testing! Let me know if you find anything else or have any suggestions. There's also a room over on Gitter I'd you have any questions. |
The change of a status from ON to OFF and vice versa takes a lot of time.
Configuration:
Log output:
Looks like the acquirement of the locks takes 5 seconds?!
The text was updated successfully, but these errors were encountered: