zinen / node-red-contrib-huawei-router

Node-RED node to get information and send commands to Huawei LTE routers.
MIT License
4 stars 1 forks source link

"125002: Session error" #15

Closed HerrTuulik closed 1 year ago

HerrTuulik commented 1 year ago

Hello!

What does this error mean? I have three instances of the huawei info node, Month statistics, Monitor Node, Traffic statistics. Monitor node returns this error when called, the others seem to work fine.

I'm using huawei e5576-320

HerrTuulik commented 1 year ago

Didin't notice the post post below at first so i tried that. Timeout is 5 minutes or 300 seconds, which seems to be very close to the default 298 seconds. Set it to 300 but this error still occurs.

zinen commented 1 year ago

Yeah so the 298 seconds is my way of making sure that the 5 minutes timeout is respected minus 2 seconds as a safety measure. Question 1: Do you use the same server config for all your 3 nodes?

image

Using the same server config should make sure that they share the session and so not to hit the amount of session limit. Might be that they try is request data at the same time and the router cant handle this.
Question 2: Are the nodes actives at the same time? If so try making them run one by one. I haven't implemented a queueing system as I haven't seen this problem you speak of. But I only run one node at a time.

Question 3: Also what version of this node are you using?

HerrTuulik commented 1 year ago

Yes, they all share the same config. I'm on version 1.3.0 Some more info, maybe a clue:

I'll try offsetting the injections and report back the results next time i get the chance.

HerrTuulik commented 1 year ago

Offsetting the injection times worked! Thank you for your advice.

zinen commented 1 year ago

This suggest that a queue system might be a good addition. I'll note that to the API owner or maybe try implementing this myself in this module. Thanks for testing

zinen commented 1 year ago

I raised issue#28 at https://github.com/Salamek/huawei-lte-api-ts/issues/28 to hear about this.

zinen commented 1 year ago

I had multiple request noted for a version 2 update which was just released. Some included breaking changes but one of these was to implement a simple queuing feature as per this issue.

The simple queue is now in place. @HerrTuulik feel free to test this out and tell me if it works for you.

zinen commented 1 year ago

No response. Closing issue