Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I have for some time ago tried to connect to a test firebase database using WebSockets, but with limited success and have not been able to get any useful data. I have been able to get a basic REST connection running using HTTP GET / POST, but would like to have "real-time" data.
As an alternative I have been looking at using SSE / REST-Streaming, but I have not yet had the chance to look into this.
Have anybody had success in connecting to firebase directly using websockets or in general get a REST-Streaming connection up and running?
I guess it is not a "problem" but more a friendly request to hear if anybody else have had success by connecting to ex. firebase using websockets or REST-Streaming and see if anybody would share some knowledge about implementing this in a WICED based system.
I have not tried setting up a REST-Streaming connection, but my initial idea is to try making a streaming HTTP connection and see what happens. When I tried to connect to a test firebase system I had configured, I ended up with a response as described in this thread: nest api - Firebase websocket protocol, am I missing something? - Stack Overflow and I was not successful in moving past this. I have not been looking into it for some time now.
Did you manage to get a connection up and running to a firebase system using the websocket_client snip and be able to send and receive data?
I was not able to connect to firebase as it throws "upgrade header" error. I need to capture the logs and check if the upgrade header is being sent by WICED device. I will try to debug the issue and et back to you. Let me know if you have made any progress