You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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
andweather/light
respectively, there is no way to subscribe to aweather
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 presentsNot 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?
The text was updated successfully, but these errors were encountered: