@Yveaux I also add the delay to not ddos the gateway. When I did the MySensors workshop, 20 people started to connect to the gateway almost at the same time. And they got Funky messages. Since then I do a delay. But it would probably be better to add a random time to the delay. Something like 20ms + random( 0 - 30 ) ms. That way you don't get the ddos effect. Sonoff had the same problems with their solution a couple of years ago, when the servers went down. All Sonoff devices tried to reconnect almost the at the same time. Which caused a ddos xd
Group Details Private
Tech Evangelist
Spreading the word about MySensors Technology
-
RE: Sensor presentation failure
-
RE: Commenting and chat seem to be broken
Ok, could not find the root cause for why the embedded forum thread on openhardware.io couldn't detect if user has a valid session/is logged in to the forum.
Did a workaround by adding a "Comment" button which redirect user to the thread on the forum.
-
RE: Commenting and chat seem to be broken
@BearWithBeard
Good!Still investigating the comment problems on openhardware.io. Might need to do manual restarts of the forum to test things later on.
-
RE: Commenting and chat seem to be broken
Fixed the rate limit when fetching data from github (now 5000 requestst vs 60 per day). Should fix the fetch problem we saw on the main site @mfalkvidd.
-
RE: Commenting and chat seem to be broken
No forum crashes/restart for 2 hours. Seems fixed.
-
RE: Commenting and chat seem to be broken
Yeah, noticed that as well an hour ago. It was actually caused by an exception/crash of the forum. I think I pinpointed the problem and fixed it. Need to keep an eye on the logs over the day.
-
RE: Commenting and chat seem to be broken
I fixed the raspberry article, the updated markup-parser seems a bit more picky about newlines before/after headers and code-blocks for some reason.
Edit: Correction, the bare <br> html-elements all over the article needs to be separated with newlines -
RE: Commenting and chat seem to be broken
Not sure if it helps. But chrome changed things for CORS. If the CURS headers aren't set correctly you can not use a rest api anymore.
-
RE: Commenting and chat seem to be broken
Hmm.. something seems to be broken (for me as well). The "Login" button should not be present if you are logged in to the forum. Clicking it seems to generate a js-error.
This all might be triggered by some new cross-site security feature of chrome and it could take some time for me to figure out a solution.