Comments (5)
@sohil4932 - can you try flashing your electron with a v0.6.3 system firmware and see how that goes?
I am guessing that the electron is going into "low power mode" which has a newer way to reconnect to the server. This would be the same with the Argon and Boron.
from spark-server.
The reason it reconnects after every 30 seconds is because in 'settings.js' timeout value is set to 30 seconds. So before data is received the timer value resets and connection is re-established. Increase the value and rebuild CLI and try again. You can also edit this in your own firmware. It should work.
from spark-server.
Ahh.. that makes sense. Do you know what the standard timeout for electron is on the hardware-side?
It might make sense to allow the setting to be configurable per device type.
from spark-server.
@jlkalberer The timeout duration varies by mobile network operator. The default timeout is set to 23 minutes. However, when using third party SIM cards, timeout value needs to be set manually depending on the carrier.
from spark-server.
Got it. I see they have a keepalive function here - https://docs.particle.io/reference/device-os/firmware/electron/
I would hope that it would ping the server with that value so we can store it and use it as the keepalive.
If it's not doing that, it would make sense to just check if the device is an electron and use 23 minutes instead of 30 seconds.
from spark-server.
Related Issues (20)
- Error on spark-server update-firmware HOT 4
- Response timeout for event: spark-server/call_device_function HOT 5
- ERROR: DeviceServer.js for local server HOT 2
- firmware device counter increases with failed flash attempts HOT 2
- Cannot upload device IDs with non-numeric characters
- Hook for device status change? HOT 3
- Is there a way to pass the contents of the publish event directly to MQ? HOT 7
- Memory Leak
- update-firmware requests failing HOT 3
- support for mesh devices HOT 1
- Function call returns error when firmware function returns zero HOT 6
- Throws error on starting spark-server HOT 1
- device names not accepted as deviceId - breaks particle-cli HOT 15
- Device.js/14528 on hostName: Device disconnected (cache_key=_5, deviceID=deviceid, duration=46.791, disconnectCounter=1) HOT 1
- Error with handshake process HOT 32
- Claiming / provisioning a devices without an deviceID HOT 5
- Does this still work? HOT 15
- Is there a renamed implementation of Particle.subscribe(particle/device/name); ? HOT 5
- P2 compatibility? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spark-server.