Yep that is unfortunately correct. We are in the process of fixing it because having to link your devices in two different places (console and dashboard) kind of sucks.
For deeper context, this fragmentation has to do with how we isolate devices within a workspace. Right now when you create a new org in the dashboard, it creates its own workspace behind the scenes. It’s a private workspace and it’s not visible from your API console account where you can see all your other workspaces.
Last Monday, our team discussed this inconsistency and how it’s frustrating for customers that console and dashboard don’t quite communicate with each other. We want to fix it. There’s a bit of technical debt in the way of merging these, and we have to address it first. I am hoping to have this done in July.
I’ll add that we’re also going to add Seam as a provider for the connect webviews. So if you use the dashboard to connect all your devices, you will then be able to import them into various applications (e.g. Hospitable, Guesty…etc) using your Seam credentials. Stated another way, you can link up all your device accounts (August, Schlage, Yale…etc) within the Seam Dashboard, and then connect all these accounts at once with your third-party apps that already use Seam to connect directly to devices. This should make life a lot easier for larger operators who have dozens/hundreds of different device accounts that they must otherwise pair by one by one.
the dashboard and it had a very different view that what was specified early in this thread
Also correct. At the time of this original posting, we had not yet released dashboard.seam.co. The screenshots/walk-through I shared was for the API console (now at console.seam.co). The Device Dashboard is a newer product we released in March to address the need of some customers that need a visual way to manage large, heterogenous fleets of devices across many locations. Our API console was not sufficient to cover their needs. This product is still very much a work in progress.
I do notice that under the Activity section for each lock, it shows no activity, even if I use one of the test codes I set up.
This is almost certainly a bug. My apologies for this. I am going to chase it down this coming week with the team to make sure this gets addressed. In the API console, you should be able to see real-time events for many device brands. The goal is absolutely for those events to also be visible in the Dashboard. Again, it’s a bit of a work in progress…Feel free to email me as well if you want an update when the fix is live.