GUVWAF

I can confirm the instability issues @EugenePanyaev is experiencing with the ME81H. The same problem seems to happen with the set/targetTemperature MQTT command. If there is any information you want...

Indeed, setting 'deviceOn' is still instable on the ME81H. The value of 'temperature' and 'state' does seem to change accordingly. However, now I cannot change 'targetTemperature' via MQTT at all...

> The LoRa shortcoming has been in my head for a while. I've considered making a warning about over-use of LoRa, but never did. As you mentioned it just now,...

Nice work. However, right now direct messages are not rebroadcasted as mentioned in issue #1459. With this PR in, I think direct messages can be handled just like broadcast messages,...

I did some testing using the small fix from my PR (#1593) and it seemed to work already. Maybe someone can confirm this before diving further into this? I didn't...

In my testing on 1.3.44 both --sendping and --reply are already working. When using 'meshtastic --reply' on one device, sending a message 'Hi there' from another gets a response "got...

This might not be a bug, but something that may happen in an RF environment. If the implicit ACK somehow does not end up at the sender, it will do...

feh123 reported this on Discord as well. We could actually let nodes re-ACK a retransmission for broadcast messages as well, but we should be careful that we are not ACK-ing...

A while ago I looked at Arduino-compatible FEC implementations in software. There're not that many that can handle variable payload lengths. Eventually I found one: https://github.com/Warchant/reed-solomon_syndrome_gf256 Though, these algorithms require...

> Compared to what we are using now, what sort of improvement in error correction, sensitivity and throughput would we realize? It's hard to give exact numbers. I've read 2-3dB...