# Saleae Logic 2 Automation API

**URL:** <https://discuss.saleae.com/t/saleae-logic-2-automation-api/1685>\
**Category:** Logic 2 Software\
**Created:** [July 6, 2022, 11:10pm UTC](https://discuss.saleae.com/t/saleae-logic-2-automation-api/1685 "2022-07-06T23:10:00Z")\
**Posts on this page:** 1\
**Showing post:** 143

<div class="post-metadata">

**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\
**Post date:** [March 28, 2025, 8:54pm UTC](https://discuss.saleae.com/t/saleae-logic-2-automation-api/1685/143 "2025-03-28T20:54:56Z")

</div>

@marco.degano Thanks for the heads up! I’m glad your automation script works regardless. I noticed another user posted about this as well here.

> <https://github.com/saleae/logic2-automation/issues/50>
>
> \## Issue Description
> 
> When importing the \`saleae.automation\` package, users enco…unter a warning message about protobuf version incompatibility:
> 
> \`\`\`
> Protobuf gencode version 5.29.0 is exactly one major version older than the runtime version 6.30.1 at saleae/grpc/saleae.proto.
> \`\`\`
> 
> \## Technical Details
> 
> \- \*\*Generated Files\*\*: The \`saleae/grpc/saleae.proto\` files were generated using \`grpcio-tools\`, which specifies a dependency constraint of \`5.26.1 \<= protobuf \< 6.0dev\`. This results in generated code with version \`5.29.0\`.
> 
> \- \*\*Runtime Version\*\*: The package's dependency specification in the pyproject.toml file only requires protobuf to be greater than version \`3.5.0.post1\` without an upper bound. This allows pip to install the latest protobuf version (\`6.30.1\` at time of writing), creating a major version mismatch.
> 
> \- \*\*Warning Trigger\*\*: The version mismatch causes a warning to be logged whenever the package is imported.
> 
> \## Impact
> 
> Currently, this issue only produces a warning message when importing the package. However, future protobuf releases may break compatibility entirely, potentially rendering the package unusable.
> 
> \## Steps to Reproduce
> 
> 1. Create a Python virtual environment:
> 
> \`\`\`bash
> python -m venv .venv
> \`\`\`
> 
> 2. Install the Saleae Logic 2 automation package:
> 
> \`\`\`bash
> pip install logic2-automation
> \`\`\`
> 
> 3. Run a Python script that imports the package:
> \`\`\`python
> from saleae import automation
> \`\`\`
> 
> \## Recommended Solution
> 
> \- Add \`grpcio-tools\>=1.71.0\` or some other version to the list of general dependencies. This will allow pip to see the additional constraint and avoid installing a protobuf version that is too high.
> 
> \## Other Solutions
> 
> 1. \*\*Pin the protobuf runtime dependency\*\* to match the gencode version (5.29.0) in the package's dependencies.
> 2. \*\*Update dependency constraints\*\* to prevent installing protobuf 6.x+ until compatibility is resolved.
> 3. \*\*Update the build process\*\* to use a newer version of \`grpcio-tools\` that supports protobuf 6.x.

I doubt it’s anything critical, but we’ll double check.

---

_[View the full topic](https://discuss.saleae.com/t/saleae-logic-2-automation-api/1685)._