# \[Solved\] Peripheral device defined, and has correct properties but data not stored

**URL:** <https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416>\
**Category:** Help\
**Created:** [February 22, 2017, 2:24am UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416 "2017-02-22T02:24:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Tim\_Hoffman](https://forums.losant.com/u/Tim_Hoffman)\
**Post date:** [February 22, 2017, 2:24am UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/1 "2017-02-22T02:24:51Z")

</div>

Hi

We have a device (Peripheral) attached to a gateway. Data is being sent by MQTT and we can see it in the connection log.

```auto
Device BLACKHAM GATEWAY (00000000d32fee9e) reported the state of Device 550781 (Blackham Pump 1)
MQTT losant/58855ed560781XXXX4fa88/state
Wed Feb 22 2017 10:21:47 GMT+08:00
One or more of your payload properties was rejected.
A provided attribute is not defined on the device, or the data type is incorrect.
Received Payload
(root){} 2 keys
  "data":{} 5 keys
    "count":8
    "timestamp":"2016-02-22T10:21:29.977182+08:00"
    "utctime":"2016-02-22T02:21:29Z"
    "RPM":1649
    "empty":false
  "time":"2016-02-22T02:21:29.000"

```

RPM is a correctly defined property and isn’t being rejected however no data is being stored against this device.

---

<div class="post-metadata">

**Author:** ![Tim\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Tim\_Hoffman](https://forums.losant.com/u/Tim_Hoffman)\
**Post date:** [February 22, 2017, 2:39am UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/2 "2017-02-22T02:39:14Z")

</div>

I have tried deleting the device and re-adding.

The data received is being sent to workflows, but not being stored.

---

<div class="post-metadata">

**Author:** ![Tim\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Tim\_Hoffman](https://forums.losant.com/u/Tim_Hoffman)\
**Post date:** [February 22, 2017, 2:52am UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/3 "2017-02-22T02:52:10Z")

</div>

Ok, found it.

Totally missed the fact that the clock was wrong. (Out by 1 year).  
For some reason the NTP service (was running but hadn’t set the time).  
Restarting ntp solved the issue.

Sorry to bother you.

T

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [February 22, 2017, 5:06pm UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/4 "2017-02-22T17:06:46Z")

</div>

No worries! Glad it got figured out. It would make a good feature to display a warning in the application log if the time is more than some reasonable time in the past.

---

<div class="post-metadata">

**Author:** ![Tim\_Hoffman](https://avatars.discourse-cdn.com/v4/letter/t/ebca7d/32.png) [@Tim\_Hoffman](https://forums.losant.com/u/Tim_Hoffman)\
**Post date:** [February 23, 2017, 12:10am UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/5 "2017-02-23T00:10:50Z")

</div>

That would have saved me some time. For some reason the source timestamp was the same date but one year out, so correct day and month, and to be honest am still no used to seeing 2017 😉

T

---

<div class="post-metadata">

**Author:** ![Michael\_Kuehl](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/michael_kuehl/32/99_2.png) [@Michael\_Kuehl](https://forums.losant.com/u/Michael_Kuehl)\
**Post date:** [March 14, 2017, 2:37pm UTC](https://forums.losant.com/t/solved-peripheral-device-defined-and-has-correct-properties-but-data-not-stored/416/6 "2017-03-14T14:37:47Z")

</div>

This kind of problem should be much easier to see now - as part of some updates released today, the application log will now display warnings if the timestamp of the reported data is more than a week in the past or is more than a few minutes into the future. So if it happens again, hopefully it will be obvious what is going on!