-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[Bug]: MQTT messages sent to secondary channels are always posted in primary channel #2109
Comments
I have tested this quite a bit and they go to the right places, do your channels have the same indexes on both networks? |
@garthvh The Json stuff is the problem, proto mode works fine. The newly crafted package from the Json translation indeed does not have the correct channel index set. |
@garthvh They should have since I set up one device and then shared via QR code. I also checked on both devices using meshtastic ---info and they both showed the same channels in the same order with the same psk. To be clear, in this instance the message does not originate in the other network, but from a weatherforecast that is polled on node-red every 6 hours and then transmitted via mqtt into the "weather" channel. Edit: I was writing this and then saw that that @caveman99 has figured this out now! |
I've now tested with 2.0.13 installed on the devices and the mqtt messages are still showing up in the wrong channel (primary channel) on the iOS interface, but the correct channel in MQTTX. Could it be that I have 4 channels, and only the first three are usable? My weather channel is on index 3, so the fourth channel. |
Edit, Ive now moved the messages over to channel index 2, and they are still showing up in the primary channel, but correct, changed channel on MQTTX. |
Posting serial output from router node here also for completeness sake
|
Category
Other
Hardware
Rak4631
Firmware Version
2.0.8
Description
When sending a correctly formatted mqtt message to the primary channel, it is displayed correctly and as expected in the primary channel of the iOS app. When sending a message to any secondary channel with mqtt upload and download enabled, the same message does not arrive in the expected secondary channel on iOS, but always in the primary channel.
I have confirmed this behaviour for several secondary channels, and observed the messages in the correct topic using MQTTX.
Example:
Sending a message to mqtt node msh/2/json/Primary/ works as expected: In MQTTX, it appears in msh/2/json/Primary/ and on the iOS app it also appears in the primary channel. So far so good. Now I change the mqtt node to msh/2/json/Secondary/, and as expected, in the MQTTX browser the same messages appear in the channel msh/2/json/Secondary/, but on the iOS app, the messages still appear on msh/2/json/Primary/. In my view since the same message displays fine in the primary channel, and MQTTX is picking up the messages in the correct secondary channel, that would indicate something is wrong in the meshtastic plumbing?
Relevant log output
The text was updated successfully, but these errors were encountered: