Not the latest version of SDK on Espressif's IDF Component Registry

[hayschan]

The registry is still showing the old release version v0.12.0.

However, the component manifest file idf_component.yml shows v0.12.2 instead.

version: "0.12.2"
description: Provides access to ThingsBoard platform over the MQTT protocol or alternatively over HTTP/S.
url: https://github.com/thingsboard/thingsboard-arduino-sdk
dependencies:
  bblanchon/arduinojson: "^6.21.2"
  idf:
    version: "*"

[MathewHDYT]

@imbeacon Could you update the Espressif IDF Registry accordingly.

[hayschan]

Espressif provides a GitHub action to help developers upload their ESP-IDF components to the registry as a part of the GitHub workflow.

You may check that out to automate the process of updating to the registry.

[MathewHDYT]

Ah perfect thanks a lot. I'll check if I can integrate it in v0.13.0.

[hayschan]

Here is my version of the GitHub actions. This GitHub action is triggered when a tagged commit is pushed. The version of the component published on the registry will be your git tag, indicated by ${{ github.ref_name }}.

For testing purpose, dry_run can be set to true so it will only test the action workflow, without actually uploading to IDF registry.

name: Push component to https://components.espressif.com
on:
  push:
    tags:
      - v*
jobs:
  upload_components:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          submodules: "recursive"

      - name: Upload component to the component registry
        uses: espressif/upload-components-ci-action@v1
        with:
          name: "xgzf4000"
          version: ${{ github.ref_name }}
          namespace: "hayschan"
          api_token: ${{ secrets.IDF_COMPONENT_API_TOKEN }}
          skip_pre_release: false
          dry_run: false

[hayschan]

Any timeline for updating the Espressif IDF Registry?

You can manually trigger your Upload to Registry action by adding workflow_dispatch to the YAML.

[MathewHDYT]

Once the PR has been merged and that needs some more time, because the examples on the ThingsBoard website have to be adjusted first.

I'd guess around a week, but I don't know for sure either.

[hayschan]

Any update on this?

On ESP Registry, the thingsboard/ThingsBoard version is still v0.12.0.

[MathewHDYT]

The pull request that includes the automatic release creation for Espress IDF Registry, sadly has not been merged yet as the maintainers are currently inactive and have not responded for a while.

From what I can see on the website the examples have also not been updated yet. So I sadly can not given you more information, when the pull request is merged, because I don't know either.

Perhaps @imbeacon or @ashvayka now a timeline, but they haven't responded to the last 2 pings in the Pull Request.

[hayschan]

Thanks @MathewHDYT for your always prompt response and detailed reply.

Sadly, this repo is not updated as frequently as it should be. Even though all it need is to do a PR merge. I also contributed several code examples, but misses a PR merge.

Is this repo originally a community-driven project or an official funded project by Thingsboard?

[MathewHDYT]

The first commits seem to be from forGGe. Which does not seem to be a ThingsBoard employee.

But the repository has been maintained by one ThingsBoard employee since then imbeacon and is of course on the official ThingsBoard subgroup. So I wouldn't necessarily say it started from ThingsBoard, but they definetly maintained the repository at the start, but have become more inactive with time.

The sad thing is they aren't completly inactive, because the Python SDK has received a commit just 2 weeks ago. Compared to the 5 months here, even tough it has less stars and less forks.

And a year ago the merge frequency was higher, it normally didn't take much longer than a week. I am assuming they have much less time now, or the repo isn't a big focus anymore.

For issues that has, at least for the last 2 years always been mainly me that answers them in my free time. Same for overall improvements and features, for example the original code only supported Arduino now it supports Espressif as well.

I am just hoping the pull request can be merged anytime soon, because I sadly receive issues that need help for fixed issues in the PR relatively often.

[hayschan]

The Action that uploads component to the registry failed.

[MathewHDYT]

I've seen it and commented why it happens in my now merged PR. Should be pretty simple to fix @imbeacon simply need to add the API token to the respository secrets.

[hayschan]

Yep. Need to add their token as a GitHub Actions secret environment variable in this repo.