I have been spinning my wheels on this issue for a week now, I have 3 tdeck devices that are on different firmwares, but none receive messages from meshbot. I can see that meshbot receives a command, like wx, and it sends the reply, but nothing shows up on the tdeck devices, even when setting the tdecks to bluetooth programming mode and using a meshtastic app on my phone.
Edit: the firmware versions on the tdeck are 2.6.4 and 2.6.11, and I do receive replies on all of my other meshtastic devices (heltec v3, heltec 114, etc)
I have been spinning my wheels on this issue for a week now, I have 3 tdeck devices that are on different firmwares, but none receive messages from meshbot. I can see that meshbot receives a command, like wx, and it sends the reply, but nothing shows up on the tdeck devices, even when setting the tdecks to bluetooth programming mode and using a meshtastic app on my phone.
Edit: the firmware versions on the tdeck are 2.6.4 and 2.6.11, and I do receive replies on all of my other meshtastic devices (heltec v3, heltec 114, etc)
<!-- github-sync-id:3332370584 -->
Via channel or DM? Keys might have been broken. But all of this is mesh firmware not really the bot.
One issue with tdek and games mostly is there is no 🍋 support yet. So Lemonstand for example may not be ideal UI experience.
But simple messages should work fine I just texted my bot from a tdek. I expect no issues overall.
Too much gain possibly get further away?
Via channel or DM? Keys might have been broken. But all of this is mesh firmware not really the bot.
One issue with tdek and games mostly is there is no 🍋 support yet. So Lemonstand for example may not be ideal UI experience.
But simple messages should work fine I just texted my bot from a tdek. I expect no issues overall.
Too much gain possibly get further away?
<!-- github-comment-id:3198999693 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have been spinning my wheels on this issue for a week now, I have 3 tdeck devices that are on different firmwares, but none receive messages from meshbot. I can see that meshbot receives a command, like wx, and it sends the reply, but nothing shows up on the tdeck devices, even when setting the tdecks to bluetooth programming mode and using a meshtastic app on my phone.
Edit: the firmware versions on the tdeck are 2.6.4 and 2.6.11, and I do receive replies on all of my other meshtastic devices (heltec v3, heltec 114, etc)
Via channel or DM? Keys might have been broken. But all of this is mesh firmware not really the bot.
One issue with tdek and games mostly is there is no 🍋 support yet. So Lemonstand for example may not be ideal UI experience.
But simple messages should work fine I just texted my bot from a tdek. I expect no issues overall.
Too much gain possibly get further away?