# Test Data (websocket?)

**URL:** https://community.tempest.earth/t/test-data-websocket/23977
**Category:** Developers
**Created:** [March 14, 2024, 2:44am UTC](https://community.tempest.earth/t/test-data-websocket/23977 "2024-03-14T02:44:31Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jeffstein](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/jeffstein/32/14763_2.png) [@jeffstein](https://community.tempest.earth/u/jeffstein)
#### Post date: [March 14, 2024, 2:44am UTC](https://community.tempest.earth/t/test-data-websocket/23977/1 "2024-03-14T02:44:31Z")

</div>

Is there a trove of **exhaustive** test data out there?

I’m getting the following off a websocket for lightning:

```json
{
  "serial_number": "ST-00081234",
  "type": "evt_strike",
  "hub_sn": "HB-00061234",
  "evt": [
    1710383159,
    13,
    -182,
    1
  ],
  "source": "enhanced",
  "device_id": 392412
}

```

But this doesn’t “seem” to match what I expect

The QuickStart says we have this

 ![image](https://us1.discourse-cdn.com/flex020/uploads/sws/original/3X/0/a/0a0c662d8902ec741302e94dfd0844517e604dbe.png)

And the other API docs say we have this:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/sws/original/3X/a/1/a15401ba1e8dad6c5def71204e8b73f3019877c6.png)

Fine - I have these fields - but there are other fields that show up in the messages … and I’m trying to see if there is a list somewhere of what they are. I’d like to have an `exhaustive` websocket lib that gets everything.

I just kind of catch issues with my parsing - throw the files into a test fixture and refine.

---

<div class="post-metadata">

### Author: ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)
#### Post date: [March 14, 2024, 5:47pm UTC](https://community.tempest.earth/t/test-data-websocket/23977/2 "2024-03-14T17:47:51Z")

</div>

A similar question was unanswered two years ago - [Lightning Strike Event [type = evt\_strike] - What is the unit for Energy? - #7 by amin](https://community.tempest.earth/t/lightning-strike-event-type-evt-strike-what-is-the-unit-for-energy/13223/7)

---

<div class="post-metadata">

### Author: ![jeffstein](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/jeffstein/32/14763_2.png) [@jeffstein](https://community.tempest.earth/u/jeffstein)
#### Post date: [March 14, 2024, 6:14pm UTC](https://community.tempest.earth/t/test-data-websocket/23977/3 "2024-03-14T18:14:15Z")

</div>

I thought that was answered somewhere. There is no unit for energy it just is a number

---

<div class="post-metadata">

### Author: ![peter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/peter/32/1365_2.png) [@peter](https://community.tempest.earth/u/peter)
#### Post date: [March 14, 2024, 6:57pm UTC](https://community.tempest.earth/t/test-data-websocket/23977/4 "2024-03-14T18:57:42Z")

</div>

> [@jeffstein](#):
>
> and I’m trying to see if there is a list somewhere of what they are.

I’m afraid you are not going to find what you are looking for. The API docs only document the fields that are supported for third-party access. The other “undocumented” fields are either used to support WF’s own apps (they don’t use a separate API), are for testing, or are experimental features that may disappear at any point. Sometimes us users can deduce what a value may be, and can choose to use it if we wish, but it is at risk of being removed from the API at any point

---

<div class="post-metadata">

### Author: ![vinceskahan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tempest.earth/vinceskahan/32/2785_2.png) [@vinceskahan](https://community.tempest.earth/u/vinceskahan)
#### Post date: [March 17, 2024, 12:25am UTC](https://community.tempest.earth/t/test-data-websocket/23977/5 "2024-03-17T00:25:12Z")

</div>

> [@jeffstein](#):
>
> I’d like to have an `exhaustive` websocket lib that gets everything.

Suggest you code to the published public interface ‘and’ have your code defend itself against unexpected extra input like any good program should be coded to do.