Error: getMeasure error: Status code404

[karbassi]

Error: getMeasure error: Status code404

[mainstreetmark]

Netatmo finally replied. the "device_id" is the base station's mac. I needed to pass each device'd mac via "module_id" to getMeasure.

[karbassi]

@mainstreetmark: Make sure your auth and options variables is filled in.

Using api.getStationsData(), you can get your device_id that is in options

var netatmo = require('netatmo');

// FILL THIS OUT
var auth = {
  "client_id": "",
  "client_secret": "",
  "username": "",
  "password": "",
};

var api = new netatmo(auth);

api.getStationsData(function(err, devices) {
  console.log(devices);
});

// FILL THIS OUT
var options = {
  device_id: '',
  scale: 'max',
  type: ['Temperature', 'CO2', 'Humidity', 'Pressure', 'Noise'],
};

api.getMeasure(options, function(err, measure) {
  console.log(measure.length);
  console.log(measure[0]);
});

[mainstreetmark]

Yep. getStationData is working. I use it. Here's a section of getStationData's reply:

{
  _id: '03:00:00:01:cf:24',
  type: 'NAModule4',
  last_message: 1500993523,
  last_seen: 1500993497,
  dashboard_data: {
    time_utc: 1500993497,
    Temperature: 25.4,
    temp_trend: 'stable',
    Humidity: 57,
    CO2: 682,
    date_max_temp: 1500956588,
    date_min_temp: 1500978683,
    min_temp: 24.3,
    max_temp: 25.4
  },
  data_type: [
    'Temperature',
    'CO2',
    'Humidity'
  ],
  module_name: 'Office',
  last_setup: 1440081115,
  battery_vp: 4840,
  battery_percent: 36,
  rf_status: 69,
  firmware: 44
}

and then here's the code that 404's:

var options = {
  device_id: '03:00:00:01:cf:24', //<-- _id
  scale: 'max',
  type: ['Temperature'],
};

api.getMeasure(options, function(err, measure) {
        console.log(err);
  console.log(measure);
});

[karbassi]

@mainstreetmark check again, it may be that you hit an API rate limit or the service was down.

Also, could you print our what is in err and measure.

[mainstreetmark]

Error: getMeasure error: Status code404
    at netatmo.handleRequestError (/Users/mark/Sites/tg4/node_modules/netatmo/netatmo.js:46:15)
    at netatmo.<anonymous> (/Users/mark/Sites/tg4/node_modules/netatmo/netatmo.js:383:24)
    at Request.self.callback (/Users/mark/Sites/tg4/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/Users/mark/Sites/tg4/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at IncomingMessage.<anonymous> (/Users/mark/Sites/tg4/node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:291:19)
undefined

measure is "undefined".

getStationData appears to be working, sending back a list of devices[0].modules, so the Netatmo connection is working.

├── [email protected]

[mainstreetmark]

Here's my form post, from line ~370 of netatmo.js (with my particular access token hash X'd out):

{ url: 'https://api.netatmo.net/api/getmeasure',
  method: 'POST',
  form: 
   { access_token: 'xxx|xxx',
     device_id: '03:00:00:01:cf:24',
     scale: 'max',
     type: 'temperature' } }

A valid URL, it seems.

Here's what was in body:

{"error":{"code":9,"message":"Device not found"}}

So, perhaps the error message handling could be improved?

[mainstreetmark]

ok, ... another note.

I can't even get dev.netatmo.com to recognize the MAC it's giving me, and the MAC it does give me doesn't OUI to Netatmo. So the "404" in all of this has been that my MAC wasn't found. Netatmo thinks the devices should start with "70:ee:50:00:00"

So I'm going to spend some time with NMAP and maybe ask Netatmo themselves why my MACs are not lining up.

"Status code404" was misleading. :)

[karbassi]

@mainstreetmark thanks for updating this. 💯

On the server side, technically 404 status code is correct since your device couldn't be found in their DB.

On a service level, please do reach out to Netatmo. It's weird that the MAC addresses aren't synced correctly. Could be a number of reasons for that. My bet is that they'll just have you delete it from your account and re-add it.

Keep me updated. 👍

[mainstreetmark]

Ok. Will let you know. Looks like my ecosystem needs a bunch of batteries anyways.

Meanwhile, maybe display the actual error from the body, rather than the status code. Thanks. :)

[karbassi]

@mainstreetmark It should already.

The code will display error.message from the body response. See line 37-40.

Line 382-388 is the logic.

Can you debug and tell me what is being sent to line 383?

For the function call this.handleRequestError(err, response, body, "getMeasure error"), can you debug and give me the values of err, response, and body?

response may be large, but I'll need to see the response.statusCode part as well.

[mainstreetmark]

My content type is application/json; charset=utf-8 and failed the line 37 test.

[karbassi]

@mainstreetmark I'm not behind my workstation, but can you try changing line 37 from:

if (body && response.headers['content-type'] === 'application/json') {

to

if (body && response.headers['content-type'].trim().toLowerCase().indexOf('application/json') !== -1) {

I'm trimming and lowercasing it even though the content-type should be already in the correct pattern, but it's better to be safe than assume.

[mainstreetmark]

Yep. That fixes it:

Error: getMeasure error: Status code404

... to ...

Error: getMeasure error: Device not found

No reply from Netatmo yet, but that's not a problem you need to worry about. Thanks for help.

[alcm-b]

Kind of confirming the @karbassi 's solution: make sure you submit device MAC address in lowercase.

For example, 70:AB:CD:56:58:5C yields 404 error, while 70:ab:cd:56:58:5c is okay.

At least that was the problem in my case. No idea, why Netatmo devs are so picky when it comes to MAC addresses :)