viamin/homebridge-rise-garden

Access your Rise garden via HomeBridge

homebridge-rise-garden's Issues

Plugin is slowing down home bridge

[7/3/2022, 4:00:56 PM] [homebridge-rise-garden] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[7/3/2022, 4:00:56 PM] [homebridge-rise-garden] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

https://github.com/homebridge/homebridge/wiki/Characteristic-Warnings#this-plugin-slows-down-homebridge

Trigger patch release on dependabot upgrade

Dependabot PRs should trigger an npm release.

Hopefully just one per batch of updates

Semantic-release failed due to node version

After upgrading to the latest version of semantic-release in #66, deployments are failing:

[semantic-release]: node version >=18 is required. Found v16.19.0.
[10](https://github.com/viamin/homebridge-rise-garden/actions/runs/3916130984/jobs/6694970877#step:5:11)

[11](https://github.com/viamin/homebridge-rise-garden/actions/runs/3916130984/jobs/6694970877#step:5:12)
See https://github.com/semantic-release/semantic-release/blob/master/docs/support/node-version.md for more details and solutions.

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Add CD workflow

Let's add a CD GitHub workflow that will upload new versions of the npm package when things change (such as dependabot dependency upgrades.)

It should update the dot version and build and upload the package (if possible)

Plugin is reported as unresponsive in Home app

It looks like the plugin may be failing to load altogether:

[1/7/2023, 1:15:35 PM] Homebridge v1.6.0 (HAP v0.11.0) (Rise Garden) is running on port 30130.

/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/core/AxiosError.js:89
  AxiosError.call(axiosError, error.message, code, config, request, response);
             ^
Error: connect ETIMEDOUT 3.128.218.254:443
    at Function.AxiosError.from (/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/adapters/http.js:526:25)
    at RedirectableRequest.emit (node:events:390:28)
    at ClientRequest.eventHandlers.<computed> (/homebridge/node_modules/homebridge-rise-garden/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:390:28)
    at TLSSocket.socketErrorListener (node:_http_client:447:9)
    at TLSSocket.emit (node:events:390:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

axios was recently updated in #55 so that is a possible culprit.

Light status no longer displays correctly

It seems that something changed in the Rise API recently, and we no longer parse the light brightness correctly anymore. The light is still displayed as on, but with 0% brightness.

Use refresh token when available

Currently when the login token expires, we just log in again. We should use the refresh token received when logging in so we're not sending the username and password over the network again.

Release notes don't include dependabot commit messages

Merging in dependabot PRs now creates a new release, but the release notes are empty. I think the .releaserc config needs to include the dependabot commit message type and/or scope.

Plugin is crashing when trying to read airTemperature

[1/3/2023, 4:55:02 PM] [Rise Garden] Error getting airTemperature reading from Rise API
Error: HAP Status Error: -70402
    at new HapStatusError (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/hapStatusError.ts:17:5)
    at RiseGardenAirTemperature.getTemperature (/homebridge/node_modules/homebridge-rise-garden/src/temperature.ts:84:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

However this log was generated around 6:10pm, so there's also a timestamp issue...

Plugin is crashing

Plugin is crashing on launch after update to Homebridge 1.7.0

Logs:

[11/23/2023, 2:57:08 PM] [Rise Garden] Launched child bridge with PID 22562
[11/23/2023, 2:57:08 PM] Registering platform 'homebridge-rise-garden.RiseGardenPlatform'
[11/23/2023, 2:57:08 PM] [Rise Garden] Loaded homebridge-rise-garden v1.1.22 child bridge successfully
[11/23/2023, 2:57:08 PM] Loaded 2 cached accessories from cachedAccessories.0E1F7982D189.
[11/23/2023, 2:57:09 PM] [Rise Garden] Loading accessory from cache: Microbio
[11/23/2023, 2:57:09 PM] [Rise Garden] Loading accessory from cache: Microbio
[11/23/2023, 2:57:09 PM] Homebridge v1.7.0 (HAP v0.11.1) (Rise Garden) is running on port 30130.

/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/core/AxiosError.js:89
  AxiosError.call(axiosError, error.message, code, config, request, response);
             ^
Error: getaddrinfo EAI_AGAIN prod-api.risegds.com
    at Function.AxiosError.from (/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/core/AxiosError.js:89:14)
    at RedirectableRequest.handleRequestError (/homebridge/node_modules/homebridge-rise-garden/node_modules/axios/lib/adapters/http.js:591:25)
    at RedirectableRequest.emit (node:events:517:28)
    at ClientRequest.eventHandlers.<computed> (/homebridge/node_modules/homebridge-rise-garden/node_modules/follow-redirects/index.js:14:24)
    at ClientRequest.emit (node:events:517:28)
    at TLSSocket.socketErrorListener (node:_http_client:501:9)
    at TLSSocket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
[11/23/2023, 2:57:09 PM] [Rise Garden] Child bridge process ended
[11/23/2023, 2:57:09 PM] [Rise Garden] Process Ended. Code: 1, Signal: null

Plugin Config:

        {
            "name": "Rise Garden",
            "username": "*****",
            "password": "*****",
            "pull_timer": 30,
            "_bridge": {
                "username": "*****",
                "port": 30130
            },
            "platform": "RiseGardenPlatform"
        },