You always want to support multiple sensors on one hub. I would argue you should support multiple Air+Sky as well in any combination (or quantity per hub).
I’m assuming you’re just going to tear apart the JSON per the API for Splunk. The Air/Sky JSON is ‘very’ close to the Tempest JSON. It would be very little work to support all the gear that is out there.
Right now, it supports multiple Tempest sensors on a single hub. I think it’ll also support multiple hubs, but I’m not sure since I don’t have multiple hubs.
If I had some sample data from Air and Sky units, I could add support for those devices.
Assuming you’re reading the UDP messages, just look at obs_air and obs_sky and tweak how you process obs_st (which is really the two old sensor observations combined essentially). It can definitely be done by inspection of the API.
One early Sky unit eats 8 of them a month when I want to feed it. Seriously though, look at my Amazon purchase history for 12-packs and see for yourself: