@phusebox depends on your settings ofcourse, but yes
Trying to wrap my head around it. I thought, okay, letās use a cloud provider to check if Homey sends a heartbeat. But there is no request getting through.
Iām using Cronitor, and it provides a heartbeat URL.
My flow is similar to the one from phusebox.
@Joni-be What do you mean with no reqeust getting trough? like it says youāre offline?
and please send a diagnostic report
When I create a heartbeat in Cronitor, I get a URL.
Then I change it in the app configuration in Homey.
In Cronitor, I can see the latest Activitys, but none are showing. However, itās not like Homey is saying " Iām offline "
diagnostic report code is 12c008c3-cebe-44c1-a502-a2dd7b2cb1ad
@Joni-be Actually the url works:
can you make a typo in your url?(to check if it fails)
But actually network-check checks if it can reach that url. So in this case if the url is incorrect and redirects to only cronitor.link itās still valid.
@martijnpoppen I changed the url with a 502 status code.
@Joni-be Then to me it looks like it works as it should on Homey. But no idea why you donāt see the traffic in cronitor
and just to be clear. The 502 will also say that their is still internet connection? Or will it trigger a connection is lost?
@Joni-be it should trigger connection lost.
@Joni-be Just thinking. When Homey canāt reach the internet, it will never show up in cronitor anyway. Because Homey canāt reach the url
So you will only see succesful calls
Yes, but my idea was to set a timer so that if Cronitor doesnāt receive a call in 1 minute, it sends an alert.
Iām going to keep it the way you intended it to work.
Thanks for the help Martijn!