Hello Nayely,
It is basically a two part issue.
-
logcat has authentication issues on just one of my two hubs, with one of my two accounts. Which is ‘interesting’. UPDATE: This no longer seems to be the case. Both hubs now give 403 errors. This is at least consistent.
-
The real meat in the sandwich is that ‘Hub 2’ has a driver installed and functional that somehow survived a deletion and reset of the hub. As far as the app and CLI are concerned the hub is not subscribed to the channel the driver comes from and the driver is not installed. If devices are installed using the driver, the app does not show the ‘Driver’ settings for them. However logcat knows it is there. That seems a smidgen odd, if not bonkers.
Q1) Yes that is correct. UPDATE: It WAS correct this morning. This evening Graham gives a 403 on both hubs.
Q2) As far as I am aware I used the Anidea account to install both hubs but I reserve the right to have picked up the wrong phone. As far as I can see there is no way for me to know after the event as they don’t seem to admit to having an ‘owner’.
Q3) I only have the one CLI installation. Graham gets a 403 with logcat from default authentication or PAT. I have only tried Anidea with PAT.
Q4) Not exactly.
Regardless of the account I use, and whether I use the CLI or the mobile app, all the indications are that my hub is only enrolled in two Edge channels (one of mine and the ST beta), and only has three Edge drivers installed (one of mine, Zigbee Button and Zigbee Switch). This is what I would expect.
These are the drivers that are installed according to the CLI (boring bits removed)
st edge:drivers:installed --hub=1 --token={{PAT for Anidea}}
┌───────────────┬─────────────────────────────┬
│ # │ Driver Id │ Name │
├───┼───────────┼─────────────────────────────┼
│ 1 │ Redacted │ Anidea Security Mode Helper │
│ 2 │ Redacted │ Zigbee Button │
│ 3 │ Redacted │ Zigbee Switch │ │
└───┴───────────┴─────────────────────────────┴
However if I fire up logcat, things are different.
st edge:drivers:logcat --hub-address=192.168.1.113 --token={{PAT for Anidea}}
┌───┬────────────┬─────────────────────────────┐
│ # │ Driver Id │ Name │
├───┼────────────┼─────────────────────────────┤
│ 1 │ Redacted │ Anidea Security Mode Helper │
│ 2 │ Redacted │ Virtual Devices V2 │
│ 3 │ Redacted │ Zigbee Button │
│ 4 │ Redacted │ Zigbee Switch │
└───┴────────────┴─────────────────────────────┘
? Select a driver. (all)
As you can see the hub actually has a fourth driver installed. Now the hub was enrolled in Todd’s channel and that driver was installed prior to deleting, resetting, and reinstalling the hub. So I am kind of puzzled that it is still there, and also why is it just that one? And how do I delete it given that my deletion tools insist that it isn’t there?
I should add that I haven’t really tried to delete it, for example by ID, just in case this isn’t expected behaviour and there is something diagnostic about what is going on.