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

Not all messages are visible comparing to MQTT #19

Open
4 tasks done
leshniak opened this issue Dec 30, 2024 · 10 comments
Open
4 tasks done

Not all messages are visible comparing to MQTT #19

leshniak opened this issue Dec 30, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@leshniak
Copy link

System Health details

System Information

version core-2024.12.5
installation_type Home Assistant Container
dev false
hassio false
docker true
user root
virtualenv false
python_version 3.13.0
os_name Linux
os_version 6.1.21-v8+
arch aarch64
timezone Europe/Warsaw
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 4988
Installed Version 2.0.1
Stage running
Available Repositories 1497
Downloaded Repositories 24
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
GIOŚ
can_reach_server ok
Dashboards
dashboards 3
resources 13
views 9
mode storage
Recorder
oldest_recorder_run December 18, 2024 at 10:38
current_recorder_run December 24, 2024 at 01:14
estimated_db_size 284.36 MiB
database_engine sqlite
database_version 3.45.3

Checklist

  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of any previous issues..

Describe the issue

Not all messages are visible comparing to MQTT. See below:

Zrzut ekranu 2024-12-30 o 13 39 02

Reproduction steps

Configure Meshtastic node via MQTT and this integration, read messages from the channels.

Debug logs

(I'll try to paste it in the following posts, because it freezes my browser for some reason)

Diagnostics dump

No response

@broglep
Copy link
Owner

broglep commented Jan 1, 2025

That is a nice test setup, will try to do something similar (although I'm not really close to place where lot of messages are sent)

Would you mind trying the dev version as per instructions in #12 (comment) ?
That is currently the only reason I can imagine why you would not receive all messages

@broglep
Copy link
Owner

broglep commented Jan 2, 2025

@leshniak Can you please try with the new released version 0.4.0 and see if you are still seeing missing messages?

@leshniak
Copy link
Author

leshniak commented Jan 3, 2025

Sorry for lack of response, I’m sick with the flu.

I’ve just installed it and I’ll try to give you a feedback after some activity on channel.

@broglep
Copy link
Owner

broglep commented Jan 3, 2025

Sorry for lack of response, I’m sick with the flu.
I’ve just installed it and I’ll try to give you a feedback after some activity on channel.

No worries, get well soon.
I did not yet find time to create a test setup similar to yours. A stress test would be quite interesting. The meshtastic range test module could probably be used to create some synthetic load and constantly send out message and then compare between MQTT and this integration recorded messages

@broglep broglep added the bug Something isn't working label Jan 4, 2025
@leshniak
Copy link
Author

leshniak commented Jan 9, 2025

Unfortunately some messages are lost on v0.4.0 too. Other readings are fine and stable. Can I debug it for you somehow?
Zrzut ekranu 2025-01-9 o 12 50 34

@broglep
Copy link
Owner

broglep commented Jan 12, 2025

What would be helpful are debug logs of the home assistant integration as well as serial logs from the meshtastic node if that is possible to collect. If other readings are stable and fine, it seems strange the the messages themselves are not received all.
One thing that would be interesting to see if the meshtastic firmware actually publishes the message as phone notification (the log message reads like Tell client we have new packets).
What meshtastic firmware version are you using?

@leshniak
Copy link
Author

leshniak commented Jan 16, 2025

Hey @broglep, here are some debug logs from HA. As you can see, the last message from 21:02 is missing. I'll try to collect logs from the device, but it's more tricky. I'm using v2.5.18.89ebafc firmware.

Image

home-assistant_meshtastic_2025-01-16T21-14-43.849Z.log

@broglep
Copy link
Owner

broglep commented Jan 16, 2025

Thanks for providing the logs. I could find the corresponding debug log for the text message on 19:37:57, but none for the one that is missing at 21:02, which is really odd as there are quite some packets being processed at that time (position and telemetry), so the connection itself seems to be properly functioning.

Serial log outputs would be really helpful in this case, it almost appears like the text message is not being sent to the phone api. If I remember correctly mqtt publishing is done before sending notification to the phone api / client / this integration, some maybe something is preventing the notification to be sent on the firmware

@leshniak
Copy link
Author

I’m gonna setup second node and collect logs via serial, I will also setup rsyslog for the first, remote device. Hopefully we’ll find something.

@leshniak
Copy link
Author

I didn't have an opportunity to make this setup, I'll do this after February 6th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants