Hello,
Would it be possible to implement a kind of supervision with an alert on the communication method of your choice when an external integration changes its status from « Connected » to « Disconnected » (it must have been connected at least once, otherwise we will receive alerts as soon as the external integration is installed)?
Indeed, the goal is to be alerted, for example, for Daikin if the connection token expires to restart the connection or any other issues that would change the status to « Disconnected ».
Perhaps the same alert could also be set for the « In Progress » status.
Thank you
For TV integration, this isn’t possible. When the TV is on, we’ll have the info that we’re connected. But once turned off, we risk having false notifications.
I’m talking about this:
When the TV is off, does « Connection » switch to disconnected on your end?
Yes 
because the websocket is closed
Let’s see if we can add some exclusions 
But why isn’t it the service that manages its token renewal?
In my case, when I turn the TV back on, I have a WOL to physically turn on the TV and a socket reconnection.
For you, when the token expires, shouldn’t it automatically renew it?
Or do you have to do a manual action, of course? 
I haven’t encountered this case with Daikin as I believe the token expires in 1 year
So I’ll see in 1 year if it is automatically renewed or not 
But I was just giving this as an example, it may be in a disconnected state because Daikin is experiencing a problem, for example, or the integration encountered an unhandled error and it crashed and ended up in a disconnected state
What are the connection statuses? Connected, disconnected? Maybe we should have a degraded state?
No idea
Yes, maybe a degraded state
