Trying to get this going again and I have a LoRa device setup to join a TTN v3 application.
The device is configured and on the application I see join requests being accepted
However those join request accepts aren’t being seen back on the device. I can’t work it out
Any thoughts ?
oh @ajlennon what did you do?
could you please grant me support access of your device via DM?
I made a bit of progress… If I run an alternate example on the device (Heltec CubeCell htcc-ab02s) - the LoRaWAN_OLED instead of LoRaWAN_OnBoardGPS_Air530 it joins and works “better” although I get timeouts.
So I am thinking this is more likely device end stuff now and have bumped it over to Heltec here…
So I don’t want to waste your time atm!
Missed this one! Did they get you resolved over there at Heltec @ajlennon?
Hi Marc, it’s been a minute. I hope you are well? I finally got round to setting up the Rak pi 4 - 4gb again and logged onto balena yesterday but noticed my gateway had disappeared.
I Read the info about applications becoming fleet and re set my gateway. New card, etched a new 64 bit version and added to my device.
Everything is downloading and installing but she keeps getting stuck in supervisor state and fails to update.
Looking at the logs it looks not to be pointing to ttn but she communicating with balena as it’s showing online.
Could I ask you point me in the direction of new literature for setting up a packet forwarder on a pi/rak2245 or take a quick peek to tell me what I’ve done wrong but go easy I’m new to this 
How did you deploy this project?
What OS and supervisor version are you using?
Could you please try to restart services?
El ds., 25 de set. 2021, 10:09, Ben Leahy via balenaForums <balena@discoursemail.com> va escriure:
I am using host os version :
balenaOS 2.83.10+rev1 and
supervisor version 12.10.1 is this correct?
I’ve just restarted services and the pi is back online but no logs currently since last night but showing online for 30 mins. I then went to diagnostics and checked device health everything has succeeded and then run supervisor state
On the left hand side
Update pending : false
Update failed : false
Update downloaded : false
I then run a device diagnostics and I’m looking at the script now it’s the same issue upon before starting up the supervisor v12.10.1 it hits an error from daemon ; no such container : resin_supervisor
Everything else seems to have successfully installed
Could you please confirm the repo you are deploying? I will try to reproduce 
El ds., 25 de set. 2021, 15:28, Ben Leahy via balenaForums <balena@discoursemail.com> va escriure:
And how would one go to retrieve such information for you?
Hello @2bods1dream what is the repository that you are deploying on your balenaCloud fleet?
Hi Marc, so after your message I done some more reading and watching then I realized that I didn’t have a repository installed. I followed a happy hour tutorial and downloaded the basic station from balena hub but it isn’t clear to me from the videos how to push to the pi using my laptop/windows and when I read the documentation it says do this in the usual way.
I just watched this video and ask
am I on the right track? Do I need to download visual studio code to enable me to do this ?
Hello @2bods1dream you have a supervisor error that is very weird.
Let’s try to restart again from scratch? If you go from balenaHub, follow these steps:
Fork this fleet.Add Deviceand introduce your WiFi credentials (or use Ethernet). That will download an OS image.Does it appear? Send me a screenshot and fingers crossed that now everything works well
Morning Marc thanks for the information.
I’ve just done that just now. Device showing online again but in the logs I’m getting errors around the URI
Did you define the TC_URI variable?
El ds., 2 d’oct. 2021, 13:49, Ben Leahy via balenaForums <balena@discoursemail.com> va escriure:
@2bods1dream Did you define TC_URI variable? Let me know if you could solve your issue.
Help with missing tag!
HOST OS VERSION: balenaOS 2.87.16+rev1 (production)
SUPERVISOR VERSION: 12.11.0
CURRENT RELEASE: `6ec3107`
TARGET RELEASE: `6ec3107`
This is one of three Basic Station gateways I have built this one using a RAK831 concentrator with a new Raspberry Pi Zero2 W to evaluate. For some odd reason I have no persistent EUI for my new gateway, the “tag” is blank, doesn’t exist.
Oddly, when I look at the console log, I see an error that the gateway ‘all 8 bytes of an EUI’ does not exist. If I copy this from the device’s console log to the TTS device “General Settings >> EUI” boom! I have a working gateway.
The problem is that the number I copy from the console log is not persistent and is regenerated each restart!
Have I done something obviously wrong or is there some sort of configuration file where I can write a persistent EUI?
Here is an image of the “tag” field on the Balena dashboard, it is populated in my other devices!
Thanks in advance
Garry
Hello @GryKyo welcome to the balena community!
EUI is the mac address and probably it doesn’t detect the mac address of the Raspberry Pi Zero2 W.
Could you please try this command from the HostOS Terminal and share the results?
cat /sys/class/net/eth0/address | sed -r 's/[:]+//g' | sed -e 's#\(.\{6\}\)\(.*\)#\1fffe\2#g'
Thanks
Thanks for the reply. This works with a small adjustment (eth0 >> wlan0) as the board is connected via WiFi but returns the MAC address OK -
e45f01fffe3c42dc
Is it possible to make a local change reflecting the …/wlan0/… interface or can I write the MAC address to somewhere to make this persistent?
It seems you are on to the issue OK, let me know if you have a suggestion and thanks again for the support.
FYI: Despite my lack of any IT training this is my first support request since using this platform since the old “resin” days! This has to be a pretty good test
Garry
Great @GryKyo that you made it work with wlan0 instead of eth0.
Did you try if that worked on The Things Stack?
PS: good to see you back from resin