Anyway- Now auto discover works, and I can add my Yale doorman and it works.
NICE!
Cool!
- but the auto discover doesn’t seem to bind the location info - And I’m not able to guess the correct channel
I’m able to reproduce your behaviour, I have two Verisure installations, one in our home and one in our summer house.
The Verisure API exposes two variables; currentLocationName and currentLocationId. Since we now are on vacation in our summer house, the API returns:
"userTrackings":[
{
"isCallingUser":true,
"webAccount":"jannegpriv@gmail.com",
"status":"ACTIVE",
"xbnContactId":"22938123",
"currentLocationName":"HOME",
"deviceId":"C094BEA3-42FA-4536-EB4E-EA9564BB37F",
"name":"Jan Gustafsson",
"currentLocationTimestamp":"2019-07-19T09:49:20.000Z",
"deviceName":"Jans iPhone",
"currentLocationId":"79ffa72e-3e23-4edf-ba23-e4f157f77563",
"__typename":"UserTracking"
},
This seems logical, currentLocationName is a string containing my location status `HOME’ and currentLocationId is an id.
However, for my location status at our house Verisure API returns:
"userTrackings":[
{
"isCallingUser":true,
"webAccount":"jannegpriv@gmail.com",
"status":"ACTIVE",
"xbnContactId":"22938123",
"currentLocationName":null,
"deviceId":"C094BEA3-42FA-4536-EB4E-EA9564BB37F",
"name":"Jan Gustafsson",
"currentLocationTimestamp":"2019-07-15T06:06:10.000Z",
"deviceName":"Jans iPhone",
"currentLocationId":"AWAY",
"__typename":"UserTracking"
}
currentLocationName is not set (null) and currentLocationId is a string with my location status AWAY
.
For me this looks like a in the API, or can someone explain the logic in this?
The binding can of course compensate for this, if currentLocationName is null then use currentLocationId instead.