using the scope
as documented returns no useable information using /gethomedataread_smokedetector
Code: Select all
"smokedetectors": [
{
"id": "70:ee:50:5b:be:da",
"type": "NSD",
"last_setup": 1624787800,
"name": "Rauchmelder Keller"
}
Code: Select all
{
"id": "70:ee:50:5b:be:da",
"type": "NSD"
}
Code: Select all
{
type:"NSD"
firmware_revision:108
status_active:true
test_mode:false
hush_mode:false
smoke_detected:false
status_tampered:false
detection_chamber_status:"ok"
battery_alarm_state:"ok"
battery_percent:100
wifi_status:3
wifi_strength:52
sound_test:"ok"
last_sound_test:1624788573
last_seen:1624787918
last_wifi_connection:1624787914
status_low_battery:false
id:"70:ee:50:5b:be:da"
}
Is this a bug or is this the intended behavior ? It looks like that dev.netatmo.com has some secret scopes. What do I need to do to get this information from my smokedetector if I create my access_token only with published scopes ?
Did someone manage to get more info about the NSD similar to what dev.netatmo.com provides ?
Thanks,
-Markus