Hi,
Is there a way to route the Wi-Fi SSID that my Notecard Cell + Wi-Fi is currently connected to? I see that I can go to device > sessions and click on a session and see “ssid” in the JSON. Right now this is the only method I could find to be able to verify this.
The reason is that one of my devices is not connecting to a different Wi-Fi network that I tried to remotely configure the device to connect to via environment variables (via this method: Dynamically Switching Wi-Fi Networks on a Notecard - Blues Developers). This worked on another device with the same exact setup, but not the one in question. That is a separate issue.
Currently my dashboard only shows the configured Wi-Fi network (the environment variable), but is misleading my end-user into thinking the device is successfully connected to it. It is still connected to the originally configured Wi-Fi network.
I hope this makes sense. Thank you! 
Hey @tsuzenski,
Sorry for the late reply here and thanks for flagging this. It’s indeed a little weird that the ssid shows up in the Sessions UI in Notehub, but that it isn’t included in the routed _session.qo events. I’m going to do some asking around internally and get back with you.
TJ
1 Like
Ok, good news. We’re working on a change to Notehub that will add a number of fields to _session.qo events, including ssid.
I don’t have an exact timeline for you, but we already have a proposed implementation so I’m hoping this will be weeks away and not months. I made a note to follow up on this thread when it’s live.
TJ
1 Like
Very cool - thank you TJ!
@tsuzenski Just to follow up, the ssid is now present in _session.qo events when a new session starts.
TJ
2 Likes
Hi there,
Following up with this - I’ve noticed that the ssid reported by one of my Wi-Fi Notecards does not update correctly. I have a device that was previously connected to one Wi-Fi network but has since moved to a different geographic location and is now using a completely different Wi-Fi network. However, the Notecard still reports the old ssid, which should be impossible.
Is there a way to force an update or refresh of the reported SSID? I tried remotely restarting the Notecard but still no luck.
Thank you! 
Hey @tsuzenski,
Let me see if I can recreate this and get back with you. What firmware version are you running on the Notecard that had the issue?
Thanks,
TJ
Hi TJ,
Thank you! I am running 8.1.2.17005.
Hey @tsuzenski,
I just tested with 8.1.3.17044 and it worked for me. Specifically I:
- Connected a Cell+WiFi Notecard to Network A, and verified sessions were coming through with its
ssid in Notehub.
- Added a
_wifi environment variable to my Notecard via Notehub to tell it about Network B, and did a sync to ensure my Notecard had info on the new network.
- Unplugged Network A.
- Did a new sync, and verified the new sessions were coming through with Network B’s
ssid.
I’m going to try the same steps with 8.1.2.17005 later this morning and see if I get the same result.
TJ
1 Like
Ok, I was able to recreate your problem on 8.1.2.17005. When I switched my network through the environment variable the ssid on my session events never updated.
And It looks like we did push out a few wifi-related fixes in 8.1.3 (Notecard Firmware Releases - Blues Developers).
Can you try updating your device to see if the problem goes away?
And sorry, I should’ve been explicit about the firmware requirements when I mentioned this was available in my earlier comment.
TJ
2 Likes
That’s okay, TJ! Thank you so much! A simple fix.