Closed bigdaveakers closed 3 years ago
i am seeing the same issue, scanning the barcodes from the box or manually, both of mine are not being recognised
@bigdaveakers / @Nayonac1 are you still able to reproduce this?
Just retested and its working now, tried with 2 devices and both have added successfully, scanning from the box did say invalid QR code, but using the the stickers inside seemed to work (even though they look identical ?)
@Nayonac1 would you mind sending a photo of these two QR codes to support so that we can do a post-mortem of that?
have sent an e-mail, but looking closer at the box it doesnt have the RPI code which is why i think it was showing as invalid, thats probably what the issue was.
I am getting the same errors. The device does not exist or code is incorrect. I get this weather I enter manually or scan QR code. I have tried scanning the sticker on the box, on the hotspot and the two loose ones that were floating around inside the box. Very frustrating.
I'm also having the exact same issue.
The QR code on the box is different than the ones inside the box and on the device.
The QR code on the box also only lists the NSER
.
I've tried scanning all 4 QR codes, and tried entering the ETH
and RSER
manually but I keep getting the error:
"The device does not exist or code is incorrect"
My device is not fully synced yet (~90%) and I also haven't asserted a location. Don't know if that makes any difference.
It's an indoor version, Freq 868. Ordered somewhere in march and was delivered this week.
I've tried it yesterday and today. Both from my phone (iOS) QR Code scan and manual input and from the browser on my laptop.
I am also having the same issue with 2 boxes. Tried to scan the QR code, tried adding manually but getting error "The device does not exist or code is incorrect" I also wrote an email to sales but no luck yet. I confirmed the RPi Serial and the ETH MAC on the local diagnostic information page
Same issue. manual or scanning the 3 QR codes "The device does not exist or code is incorrect"
Any fix?
Same issue. manual or scanning the 3 QR codes "The device does not exist or code is incorrect"
Any fix?
Nebra support has been in contact with me, they say they will let me know when I should try again. I guess they are adding my device to their system so it no longer says invalid device. I will post here again when its working for me. You may need to contact them individually with the numbers on your box to get this resolved.
Exact same problem, have tried multiple times in the last week. QR or manual entry same error. Same results on desktop (win) or mobile (android). QR scan does pull in the correct values (they match the internal sticker and what the hotspot is reporting). I purchased from a distributor if it matters. I opened a ticket with sales@nebra but no response yet. Hotspot is working great otherwise. Thank you!
exactly the same problem here, nebra on email asked for model and frequency, rpi and eth address, they said they will respond. I doubt it but let's see
exactly the same problem here, nebra on email asked for model and frequency, rpi and eth address, they said they will respond. I doubt it but let's see
Could you please ask them to have someone from Nebra just reply to this issue on Github instead?
I also have same issue.
My issue has been resolved after sending an email to Nebra support. I asked them twice to give an update about this issue on Github but they did not respond to my request. Let’s hope third time’s a charm.
This issue was resolved for everyone.
@vpetersson Can you please close this?
Awesome. Yes let's close it out.
Describe the bug Trying to add a new hotspot results in the following error message by either manual entry or QR entry using the details on the label or via the local diagnostic page:
The device does not exist or code is incorrect
To Reproduce Steps to reproduce the behavior:
Expected behavior Expected to be able to add the hotspot
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Speaking with Sh!ne it seems that it may be that incorrect RSER has been assigned