Odd behaving WBNAN - Attn stays high always

Hardware
1

I recently purchased a WBNAN. I must have purchased this model by mistake because all my others are WBNAW. I don’t think it matters, but I mention it in case it does. This notecard seems to always, always, always hold the Attn pin high. As soon as I apply power it is a 3.3v. I have done multiple { “req”: “card.restore”, “delete”: true} commands and then a hub.set and code that works for all my other cards does not work for this one. I’ve tried to discover what is different about it and I really don’t know. I did run List Notefiles via curl and got some odd results. This was part of the response:

  {                                                                                                                                                                      
    "id": "_health_host.qo",                                                                                                                                           
    "template": {
      "text": "1",
      "alert": true,
      "voltage": 12.1,
      "voltage_mode": "1",
      "milliamp_hours": 14.1,
      "method": "1"
    }
  }

  {
    "id": "_track.qo",
    "template": {
      "_time": 14,    "_lat": 14.1,   "_lon": 14.1,
      "_ltime": 14,   "status": "aaaaaaaaaa",
      "motion": 12,   "seconds": 14,  "time": 14,
      "dop": 12.1,    "voltage": 12.1,
      "daily_charging_mins": 14,
      "distance": 14.1, "bearing": 14.1, "velocity": 14.1,
      "temperature": 12.1, "humidity": 12.1, "pressure": 14.1,
      "lux": 14.1,    "total": 12,    "count": 12,
      "sensor": "12", "usv": 14.1,    "cpm": 12.1,
      "cpm_secs": 12, "cpm_count": 14,
      "journey": 14,  "jcount": 12,
      "button": true, "inside_fence": true,
      "usb": true,    "charging": true
    }
  }

I have no idea what that is or if it has anything to do with the Attn pin issue.

Thanks.

2

Hi @sn13TX,

FYI the response you’re seeing looks like Notefile templates stored on Notehub, so nothing to be concerned about there.

As far as your other issue re the ATTN pin, can you issue a card.attn request and see what the response is?

{"req": "card.attn","mode": ""}

Thanks,
Rob