Error: unexpected response (4.00) to observeScene(169275, 200468) #36
Comments
|
Did you delete a scene? I guess I should not log an error for that response code. |
AlCalzone
changed the title
AlCalzone
changed the title
|
No scenes deleted or otherwise changed. But I agree with your proposed solution. :) |
|
Oh I mistook code |
|
Also getting 4.08s. I hadn't noticed that some are 4.00 and some are 4.08. You already ignore 4.04s. |
|
Ok, please check your logs with this version: c6a6967 |
|
4.08 means Request Entity Incomplete - this is due to an incomplete implementation of RFC 7959, see AlCalzone/node-coap-client#23 Some traffic logs would be nice to find out whats being sent and why its incomplete. |
|
Right. I've set everything up with links and updated everything. I'll let you know what happens. Thanks. |
|
Since running on the c6a6967 code, I have not seen this issue. Does that mean you've fixed it? |
|
Can't be as the errors come from |
|
I've been unable to reproduce this so I'm closing this issue for the time being. If it reappears with the latest code, I'll reopen it. Thanks. |
|
This has suddenly started happening again after I upgraded recently. I'm current running the Merry Christmas! :) |
|
Sorry to take so long, but you probably know where my priorities are right now. I'll need a tcpdump to understand whats going on, which must include the connection initiation. I usually set it up with a filter on port 5684 to only capture the CoAP traffic. And I'll need your connection credentials to decrypt the communication. |
|
Can you try again with the latest version of this library? I've identified an issue with expiring credentials - maybe that is the root cause of this issue. The lib now tries to automatically re-authenticate, therefore you should always call |
|
Just seen this again after all this time. It is consistent if I edit a scene in the Android app and happens on save: This is with |
|
Good to know! I'll see if I can reproduce it. |
AlCalzone
removed
the
needs info
|
@CliffS I guess I still need some info. I've tried with the following code: // @ts-check
const { TradfriClient, discoverGateway } = require("../../build");
const { wait } = require("alcalzone-shared/async");
async function main() {
const gwinfo = await discoverGateway();
const tradfri = new TradfriClient(
gwinfo.addresses[0],
(msg, sev) => sev !== "silly" && console.error(msg)
);
tradfri.on("error", (err) => console.error(err));
await tradfri.connect( /* my identity */, /* my PSK */);
await tradfri.observeGroupsAndScenes();
await wait(180000);
tradfri.destroy();
}
main();and added, edited and deleted a scene while the script was running. Did not see anything error-like. Can you try to provide a minimal example which reproducibly causes the error? |
Seeing a lot of
errorevents in long-running code.Should I care? Or should I just be ignoring them?
The text was updated successfully, but these errors were encountered: