Ok, gotcha!

These sensors are stationary, so I think I'll get that added in there.

Weird they wouldn't have that in the JSON! 

Thanks!

It's not really weird, if the sensor is stationary why use up the bits.  

I suppose!

You can actually grab all their sensors data by not including the sensor ID in the WebSocket - but there's not any indication of location information in the data so not very useful for spatial analysis.

@JeffSilberberg Turns out I was using the sensor ID for the wrong component in the. urn:dev:ops:16961-AQT530-V0810232 is the correct one and the schema is detected right away.

Nevermind... I was confused. Alright... moving along now.

---   Great. Be careful of that LONG key value in the Derived Schema.  

Good Luck - 

Hi Teresa,

We have this written up on our end to implement as an enhancement to add support for custom headers in WebSocket connection from the Velocity backend. Please test the workaround provided by @JeffSilberberg and let me know if that works for you or not?