mqtt &ALERT_JPEG is low resolution

Nikotine

n3wb
Apr 4, 2021
13
6
Belgium
Hi,

When Deepstack triggers, I have the alert jpeg sent to me via mqtt:

1660073730934.png

Before I was using Deepstack on the main stream, but to save some CPU, I switched to the substream:

1660073850204.png

However, now the alert jpegs that are sent via mqtt are from the substream as well, while I want them to be from the mainstream.

The manual says this:
1660074021700.png
1660074058624.png

However, I have pre-trigger enabled:

1660074112098.png

I also have high-res jpegs enabled, which I don't think has any impact anyway:

1660074162551.png

How can I ensure that the alert jpeg that is sent via mqtt is from the mainstream, without having to go back to the mainstream for AI?
 
Hi,

When Deepstack triggers, I have the alert jpeg sent to me via mqtt:

View attachment 136004

Before I was using Deepstack on the main stream, but to save some CPU, I switched to the substream:

View attachment 136005

However, now the alert jpegs that are sent via mqtt are from the substream as well, while I want them to be from the mainstream.

The manual says this:
View attachment 136006
View attachment 136007

However, I have pre-trigger enabled:

View attachment 136008

I also have high-res jpegs enabled, which I don't think has any impact anyway:

View attachment 136009

How can I ensure that the alert jpeg that is sent via mqtt is from the mainstream, without having to go back to the mainstream for AI?
To fix this need some programing changes so you will need to email support so they can make the change. I am going to email them later today about this issue, the more emails they see the better chance of them fixing it
 
To fix this need some programing changes so you will need to email support so they can make the change. I am going to email them later today about this issue, the more emails they see the better chance of them fixing it
Thank you for confirming the issue.
I've sent an email to the support team.
 
  • Like
Reactions: MikeLud1