EWhite Posted September 10 Share Posted September 10 Latest version not showing devices offline. Yolink app shows device offline. device is an outside motion sensor. I use it for my driveway alert. took a few minutes to figure out why things were haywire.. hehe Quote Link to comment
Panda88 Posted September 10 Share Posted September 10 Can you send me a log file - Yolink keeps changing how they report on-line Please enable debug before getting the log file Christian Quote Link to comment
EWhite Posted September 11 Author Share Posted September 11 here is the log file. I replaced the batteries so now device is online. hopefully you can still get what you need out of it. YoLink_9-10-2024_52013_PM.zip Quote Link to comment
Panda88 Posted September 11 Share Posted September 11 (edited) I assume the log with bad data was earlier than the log you sent Did you notice if other data was valid or unknown when the device was offline My code was supposed to follow the online state, but there is a bug so the actual state does not get updated - data should be unknown If data is valid I need to get a logfile to see what the data looks like - I may be able to recreate it later Thanks Edited September 11 by Panda88 Quote Link to comment
EWhite Posted September 11 Author Share Posted September 11 nope..this log covers it. in the yolink app the driveway motion sensor was showing offline, but in pg3x it showed as online. i went and removed the batteries again just to check,, no change in pg3x but app showed offline. weird... Quote Link to comment
Panda88 Posted September 11 Share Posted September 11 In your log there are 348 cases on 'online' parameter being returned - 343 are true and 5 are false. In the case of 5 false the same return structure also has a 'online' = True??? the 5 with false covering 5 different devices - all occured arounf 12:53. Maybe an internet issue I really do not know how to determine the if the device if offline or not - all report true Do you know at what time you unplugged the battery? Quote Link to comment
EWhite Posted September 11 Author Share Posted September 11 around that 12:53 mark is when i put the new batteries in. so it actually came back online. i unplugged battery AFTER i sent you the log..but saw the same thing you are seeing...which is no change Quote Link to comment
Panda88 Posted September 11 Share Posted September 11 Let me send them an email and ask how to determine on line off line 1 Quote Link to comment
Panda88 Posted September 14 Share Posted September 14 I heard back. It can take up to 3 reporting before it will be shown as off line. The reporting interval is up to 4 hours so it can take more than 12 hours before a device will go off line. Quote Link to comment
Panda88 Posted September 17 Share Posted September 17 I got a little more info - they use special channels in the APP (not available to the API) From support: I'd like to clarify the difference in detection speeds between the app and the API. Direct Device-App Communication The app communicates directly with the cloud platform in real time via optimized channels, allowing it to receive data almost instantly when a LoRa device transmits a signal. This is further enhanced by the use of push notifications, which are highly efficient in delivering updates immediately. API Request and Response Overhead On the other hand, API interactions rely on a request-response mechanism, which can introduce minor delays. This includes the time needed to: Establish an HTTP connection. Send the request. Wait for the server to process and respond. Handle authentication and authorization processes. These steps can cause slight lag. API Rate Limits and Throttling In addition, our API is subject to rate limits to ensure fair usage across all users. Specifically: A single UAC is limited to 100 API calls within a 5-minute sliding window. A single target device can receive no more than 6 API calls per minute, with a minimum interval of 200 milliseconds between calls. These restrictions help manage overall performance but may cause delays in scenarios requiring frequent updates. I hope this explanation clarifies the differences. If you have any further questions, feel free to reach out. Best regards, Thomas | YoLink Customer Support Quote Link to comment
EWhite Posted September 25 Author Share Posted September 25 strange.. since the battery was dead for 3 days before i got a chance to replace them...it still showed active in plugin but not in app... i think i will just change my battery status alarm to reflect an earlier alarm..should bandaid the problem..hehe Quote Link to comment
Panda88 Posted September 25 Share Posted September 25 If it happens again save the log. It should be possible to debug - it is always a guess when the API is not fully documented. I can try to pull a battery in one of my sensors to see if I can see a change Quote Link to comment
EWhite Posted September 25 Author Share Posted September 25 will do.. and thanks Quote Link to comment
Panda88 Posted September 26 Share Posted September 26 I tried my water sensor and over night it went offline - as expected - It may work now - there is no difference between sensors as they call the same functions (assuming the YoLink API acts the same) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.