Closed cdupont closed 4 years ago
This is the decoding on Gateway side: https://github.com/Waziup/wazigate-lora/blob/master/edge.go#L67
This is the log I have with V1.1:
2020-03-31T14:18:07.545138451Z [ ] Looking for connected radios...
2020-03-31T14:18:07.822436512Z [ ] Detected radio: SX1276
2020-03-31T14:18:08.492784413Z [ ] Receiving, please stand by...
2020-03-31T14:44:50.967648123Z [Edge ] Err: dial tcp 127.0.0.1:1883: connect: connection refused
2020-03-31T14:44:52.969644827Z [Edge ] Connected to edge mqtt.
2020-04-02T10:07:31.722123837Z [ ] Dest: 1, Typ: 24, Src: 8, Num: 215, Data: "UID/MyDevice/SM1/0.00", RSSI: -31
logs-wazigate-lora-2020-06-16_14.43.16.txt I am facing a similar problem. Any solutions?
@j-forster @mojtaba-esk
Do you see it with the new forwarder?
I think this is obsolete right? Old LoRa format is not supported in V2 (only LoRaWAN + LPP)?
I think so, let's see what Johann says about it.
On Wed, Nov 11, 2020 at 12:26 PM Corentin Dupont notifications@github.com wrote:
I think this is obsolete right? Old LoRa format is not supported in V2 (only LoRaWAN + LPP)?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/76#issuecomment-725369048, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHAUKAM7VWP2NJNLDUTSPJYF3ANCNFSM4LZO5JOQ .
-- Mojtaba Eskandari
The old payload encoding was replaced by LPP for Wazidevs and might be further improved by https://github.com/Waziup/WaziGate/issues/121. Any discussion on payload formats should be moved to the new issue.
This message appeared on several occasions on V1.1 final:
Partners assured that they didn't change the code on the WaziDev. With previous version of the WaziGate software, it was working, but with the new version the message appeared. Where can it comes from? @j-forster it would also be nice to print the content of the buffer in the logs for debugging.