Comments (9)
I am using the web interface. Using the iOS app overcomes the problem. There seems to be a problem with the web interface. Can you try connecting to the web interface using a PC and see whether you can replicate.
Edit: root topic on my config is msh/EU_868
I'm working in an area with bad cell reception so my VPN home isn't giving me a strong enough connection to test the web interface at the moment. I'll have to wait until this afternoon when I get home. I was able to see you on the MQTT channel (dingus, lol), but the private message I sent you didn't go through. Just want to confirm that you have upload and download enabled on the primary channel too.
Just noticed EU setting so maybe it wasn't you on MQTT unless you are currently on the East Coast of the the US.
EDIT: was able to connect to my router web interface over the VPN (think the Heltec battery died last night). I attempted to send a message but it never confirmed. Then I attempted to send a private message and it too failed.
YOU SEEM TO BE CORRECT! Looks like there is an issue with sending and receiving messages from the Web Interface. I'll have to check my other nodes when I get home to see if the message sent out over LoRa but just failed MQTT.
from firmware.
I believe there was some kind of temporary fix for MQTT that changed how it operates with the disable transmit option. There was a big discussion here before it was implemented but I can't find the link now.
from firmware.
If you do find the link let me know. LoRa disabled or not, I don't believe messages are being routed via MQTT at all on Channel 0. I only seem to be able to send/receive LoRa messages over Channel 0 (and mostly local one's at that.. hence the interest in MQTT). No MQTT traffic seems to appear on the Primary Channel 0. I do however receive lot's of node updates when setting the Primary Channel 0 to downlink enabled.
from firmware.
Ahh, make sure you have uplink and downlink enabled for channel 0. Also, if you are using the main MQTT channel your node is going to get overwhelmed and probably crash/be unreachable because of the ammount of traffic
from firmware.
Unfortunately setting the Channel 0 to both uplink and downlink doesn't change the situation. Channel 0 messages are still not being sent or received over MQTT. By default I usually set to uplink only on Channel 0 in order to avoid downloading 100's of node updates. As I mentioned earlier, Direct messages are also not being sent with MQTT but... I can receive them, which seems odd.
from firmware.
To summarise:
Bluetooth and iOS app MQTT enabled + proxy LoRa disabled: messages sent and received received successfully on Primary Channel 0 with uplink enabled only.
Bluetooth and iOS app MQTT disabled + proxy LoRa enabled: messages sent and received received successfully on Primary Channel 0 with uplink enabled only.
Bluetooth and iOS app MQTT enabled + proxy LoRa enabled: messages sent and received received successfully on Primary Channel 0 with uplink enabled only.
WiFi Web interface MQTT enabled LoRa disabled: messages sent and received received unsuccessfully on Primary Channel 0 with uplink enabled only.
WiFi Web interface MQTT disabled LoRa enabled: messages sent and received received successfully on Primary Channel 0 with uplink enabled only.
WiFi Web interface MQTT enabled LoRa enabled: messages sent and received received successfully on Primary Channel 0 with uplink enabled only.
Definitely appears to me that the WiFi implementation of MQTT is not functioning correctly.
from firmware.
What hardware are you testing this on? I will try to reproduce the issue if I have the correct hardware. ALSO, have you been trying to use the default MQTT channel? The problem could be your node is being overwhelmed and can't find free CPU cycles to send messages.
I see you are using a Heltec V3. I've got one so I'll try to reproduce your bug.
from firmware.
I was not able to reproduce your issue, but I am on a v2.3.12.
MY SETUP: Heltec V3. LoRa TX Disabled. WiFi enabled and accessibile over network. (Android lets me connect to IP so I'm not using web interface) MQTT enabled using channel msh/US/CA/SantaCruz
. Proxy-to-client not enabled. Uplink and Downlink enabled on Primary Channel.
Was able to send a message through the MQTT server that was picked up by my Router Node and rebroadcast over LoRa. I don't have a dummy load antenna to use so I cannot be positive about receiving messages but if you wanna use that same MQTT channel we can send test messages back and forth to confirm.
Edit: I think I was able to confirm received. I changed the LoRa frequency on V3.
Edit2: Private messages are also sending/receiving without issue.
from firmware.
I am using the web interface. Using the iOS app overcomes the problem. There seems to be a problem with the web interface. Can you try connecting to the web interface using a PC and see whether you can replicate.
Edit: root topic on my config is msh/EU_868
from firmware.
Related Issues (20)
- [Feature Request]: Public MQTT location sharing fixes HOT 5
- [Feature Request]: "Screen Paused" on eink is a useless feature HOT 2
- [Bug]: 2.4.3.91d6612 Tbeam failed to find radio HOT 3
- [Feature Request]: Cannot Change Time Zone HOT 2
- [Feature Request]: WIO-SDK-WM1110 RF switch question
- [Bug]: 2.5.0 Technical Preview Not Publishing Location HOT 5
- [Feature Request]: Make Location Sharing More Obvious HOT 7
- [Bug]: Attackers can replace public keys for DMs HOT 6
- [Bug]: not direct nodes showen as direct (signal bar) HOT 4
- [Bug]: Heltec V3 boot loop with 2.4.2 and 2.5.0 HOT 1
- [Bug]: Serial output no longer includes unicode characters for messages
- [Bug]: Powerloss during early boot phase kills/resets device configuration on ESP32 devices HOT 12
- [Bug]: Dockerfile failure HOT 7
- [Bug]: Apparently finding our own node num in the nodedb can cause us to pick a new nodenum! HOT 3
- [Bug]: Randomization in generatePacketId() breaks TX PacketQueue priority sorting HOT 1
- [Feature Request]: Add the absolute amount of received Meshtastic packets to telemetry HOT 3
- [Feature Request]: Admin message to request a refresh of the nodedb
- [Bug]: Heltec Mesh Node T114 no screen option - bluetooth PIN random rather than fixed
- [Bug]: T1000-E external notifications only work with factory firmware HOT 1
- [Bug]: GPS not recognized on RAK4631, w/ver. 2.5.0.ab7de7f, works fine on 2.5.0.d6dac17 HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from firmware.