Currently, subscribing to events on the local cloud requires the name of the subscribed/published event to match exactly.
This is different from the behaviour on the Particle cloud, which supports prefix filtering.
In other words, if 2 Particle devices on a local cloud are publishing weather/temp and weather/light respectively, there is no way to subscribe to a weather event and get both data streams simultaneously. This however is documented as a possible method for the Particle.io cloud – when will we see this supported on spark/particle-server?
Also, any use of the / slash presents Not Found connection errors through the cloud API.
p.s. this might be related to how it's not possible to subscribe to device-specific events (#53) on the spark-server, and how the api url requests are being parsed?
Currently, subscribing to events on the local cloud requires the name of the subscribed/published event to match exactly.
This is different from the behaviour on the Particle cloud, which supports prefix filtering.
In other words, if 2 Particle devices on a local cloud are publishing
weather/tempandweather/lightrespectively, there is no way to subscribe to aweatherevent and get both data streams simultaneously. This however is documented as a possible method for the Particle.io cloud – when will we see this supported on spark/particle-server?Also, any use of the
/slash presentsNot Foundconnection errors through the cloud API.p.s. this might be related to how it's not possible to subscribe to device-specific events (#53) on the spark-server, and how the api url requests are being parsed?