Debug Queue

[skiv71]

Hi,

I'm just looking at the Queue and whilst I can see jobs lined up for a specific node, but what is the device has more than one instance?

I'm looking to cross ref in an attempt to prevent duplicate entries etc. but if I have a node 3 with instances 1 and 2 and a specific command class, I need to know which instance the queued command relates to.

Thanks

Neil

[skiv71]

... looks to me as if the payload data tell's all... think I've figured out the node and instance as fields 1 and 6....

[pofs]

1) It really is in payload, but you shouldn't rely on it to be at specific offset, because of possible encapsulations;
2) It is encrypted for secure jobs, so you cannot access it;
3) You are not supposed to access the queue directly, queue viewer is made only for debugging purposes;
4) The queue automatically removes/rearranges duplicate jobs where appropriate, so there's no need to do anything with it.

[skiv71]

Ah, hmmm... I was hoping to interrogate the queue to see if the command request I have in mind is already present.

I'm trying to trim the queue down.

I am interrogating the queue via a wget and there are duplicate jobs

[pofs]

Some duplicate jobs are allowed for a reason.
But usually you shouldn't see two jobs for the same node having the same payload.

If you provide a specific example of a job added twice, we may discuss why there's a duplicate.

[skiv71]

I don't doubt you're right...

I think, in the meantime, I'm gonna implement my own duplicate command filtering between my system and the z-way server

[skiv71]

I have a solution now, but I'd much rather know the actual controller command queue, but in the absence of instance info, any decision's I make wouldn't be reliable.

I'm sure I've seen some user's log's on here for the queue show instance info though.

Is this something that was introduced in later versions?

[pofs]

I'm sure I've seen some user's log's on here for the queue show instance info though.

Is this something that was introduced in later versions?

You must have been mistaken, as there's no instance info there.