this post was submitted on 14 Jan 2024
315 points (76.4% liked)
Technology
59735 readers
2693 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The issue with web IpT is that devices send data reports of their status every fraction of a second. The packet may just be a few bytes but over time it adds up. Instead I wished they could just send status when they change state and wait for a confirmation but that’s harder to code…
If (Status != Prev_Status) {Send_All_User_Data();}
Yes! The issue is that if the server misses that packet, the status is now wrong. So they need an aknowledgement send from the server.
Ok...? That's extremely standard. And easy.
And yet they don’t implement it…
Every single one that uses an interface like that does. All of them. i'm talking about the requiring a response from the server part.
Most also do not do .1s update rate or whatever you think the one device you have does.
No they don't. Most send updates every 5 seconds, every minute etc.
My MyQ garage door would disagree with you.
A washimg machine isnt a micro frontend, the machine should do all the calculations on cpu and not report every time the drum spins or whatever.
I think it’s dumber than that. It just sends a
status:onevery 0.5secThats verry dumb