SIGTERM when trying to run plugin #3
Comments
|
Hmm, I can't trigger this SIGTERM based on the version differences alone. Were you able to add the Evolve okay, but then it failed afterwards? My output: |
|
@083750043 Looking at the relevant code, it's trying to pull the device uuid in the response object from the tuya API. Your device is all set up correctly in Tuya cloud? |
That's a good question. I'm 95% sure, since the device is showing as active/online in the project, so let me fiddle with some settings and see if it gets me anywhere. Will update the thread accordingly. |
|
No luck sadly. Everything looks alright from what I can tell. Random thought: The model I bought is the one without either the blue or green laser projectors; it only has the galaxy projector. I wonder if the discovery part of the code is barfing on that for some reason. No idea. 🤷 |
|
Ah, bummer. When I get a chance I'll push a point release with some extra logging, if you're up for helping to debug. Given it's barfing on the api response (either its structure or its contents), it doesn't feel like the model is the issue, but that's just my gut. |
|
Yeah for sure 👍 At your leisure! |
|
@083750043 1.0.1 is live with an extra log wrapped around the API call: |
|
@kevbo, sooooo maybe not API connection related? Still getting the same uuid error prior to the SIGTERM 🤔 |
|
@083750043 is debug logging enabled? |
|
Derp 😝 So looks like it might be a me-problem: I'll triple-check everything tomorrow again. I super appreciate the effort! |
|
I tried setting the plug-in up and am getting the same error as 083750043:
Happy to assist in debugging if that is helpful. |
|
I’ve got some downtime this weekend, so I’ll try deleting my Tuya cloud
project and starting from scratch so I can at least replicate this. I’m
hoping it’s a quick api fix or a missing step during the cloud setup.
…On Thu, Jul 4, 2024 at 10:33 PM adambursey ***@***.***> wrote:
I tried setting the plug-in up and am getting the same error as 083750043:
[7/4/2024, 11:23:18 PM] [HomebridgeSkyLiteEvolve] Discovered projector: {
code: 60009001, msg: 'API permission package error. For the solution, see
https://developer.tuya.com/en/docs/iot/authentication-method?id=Ka49gbaxjygox.',
success: false, t: 1720149798180, tid: 'ec4b20083a7d11efbecbbe9776cbd362' }
[7/4/2024, 11:23:18 PM] TypeError: Cannot read properties of undefined
(reading 'uuid') at EvolvePlatform.discoverDevices
(/volume1/homebridge/node_modules/homebridge-sky-lite-evolve/src/platform.ts:76:35)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
Happy to assist in debugging if that is helpful.
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABS6QN2T2WL6WDRNPK6WLLZKYH2PAVCNFSM6AAAAABITR36I6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZHE3TCMJTHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Apologies! Had some priority items come up and haven't been able to get back to mucking around with this. I can help test as well. |
|
Having the same problem, plugin was working fine as of a couple days ago, restarted homebridge and now I'm getting SIGKILL also. |
|
I was finally able to replicate this by going nuclear on my tuya iot account and app account. After doing some research, it looks like Tuya changed its API but hasn't updated the Node.js SDK I use. Someone else has already filed a bug: tuya/tuya-connector-nodejs#17. I filed a support ticket to see if they know what's up before I spend time writing my own shitty API wrapper that does it more right than the official SDK. The other Node.js libraries (and homebridge/homeassistant integrations) that use local communication all seem to fail for various reasons, including a jump in protocol versions in newer devices that the libraries don't support yet (codetheweb/tuyapi#325 (comment) and codetheweb/tuyapi#623 (comment)). That's just my suspicion, but in reverse engineering the network calls, the data that comes back doesn't appear to match a fixed pattern that other libraries are looking for. I'll try to find some time to debug further using tuyapi while waiting for tuya's API support to get back to me. |
|
Please try upgrading to 1.1.3 and let me know if it resolves your issues. |
seems to work for me, had to make a new dev account and app, but it is working as intended. Thank you! |
Describe The Bug:
SIGTERM when trying to run plugin on latest version of Homebridge and NODE.
To Reproduce:
Expected behavior:
Plugin starts and doesn't SIGTERM
Logs:
Plugin Config:
{
"cloud_credentials": {
"tuya_region": "https://openapi.tuyaus.com",
"tuya_access_key": "ACCESS-KEY",
"tuya_secret_key": "SECRET-KEY"
},
"projectors": [
{
"name": "Evolve",
"tuya_device_id": "DEVICE-ID",
"manufacturer": "BlissLights",
"model": "Sky Lite Evolve",
"serial_number": "Example Serial Number"
}
],
"advanced_settings": {
"polling_interval": 1000,
"max_api_retries": 5
},
"platform": "HomebridgeSkyLiteEvolve"
}
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: