Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Owntracks] Mqtt stops working. #8

Closed
Systm21 opened this issue Jan 3, 2024 · 5 comments
Closed

[Owntracks] Mqtt stops working. #8

Systm21 opened this issue Jan 3, 2024 · 5 comments

Comments

@Systm21
Copy link

Systm21 commented Jan 3, 2024

When i add a key to observe and make a crontab with curl to trigger a refresh, it dont gets updated. Only once, the first time when i add it.

@Chapoly1305
Copy link
Owner

When i add a key to observe and make a crontab with curl to trigger a refresh, it dont gets updated. Only once, the first time when i add it.

This sounds like the execution of the crontab and irrelevant to this project directly. You may post the crontab record here, I could help to have a look.

@Systm21
Copy link
Author

Systm21 commented Jan 28, 2024

There is an in depth conversation going on here if you would like to join in:

This have nothing to do with it, please stop spaming in every Topic.

This sounds like the execution of the crontab and irrelevant to this project directly. You may post the crontab record here, I could help to have a look.

I wouldn't post the problem here if it wasn't obviously related. If I trigger the whole thing directly via curl it works just as little. A problem can be excluded insofar as it generally works the first time, i.e. the first time it is published to the mqtt server. All subsequent attempts are confirmed as 200, but do not reach the MQTT server.

@Chapoly1305
Copy link
Owner

Insufficient information provided, no log, no execution steps, unable to determine to issue.

@Chapoly1305
Copy link
Owner

For the record, just checked, everything looks normal to me, mqtt posting is working as expected. I have no idea what's the issue about. The location of my tag updated right before I leave the house, and the earliest record was three days ago when I deployed for validating this issue.

image

@Chapoly1305
Copy link
Owner

I think this is related to this fix, cf64c39

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants