viamin / homebridge-rise-garden Goto Github PK
View Code? Open in Web Editor NEWAccess your Rise garden via HomeBridge
License: Apache License 2.0
Access your Rise garden via HomeBridge
License: Apache License 2.0
[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.
Dependabot PRs should trigger an npm release.
Hopefully just one per batch of updates
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.
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:
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.
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 π¦π
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:
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.
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 π¦π
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)
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.
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.
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.
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.
[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 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"
},
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.