@larkim 

Hi

Given that the issue seems to arise specifically for the application, it's possible that network latency could be a factor. You may find it helpful to consider adjusting the primary DNS to 8.8.8.8 and the secondary DNS to 8.8.4.4 by referring to the resource provided in the link below: How to change DNS

We also welcome the opportunity for fellow users to offer additional suggestions or share their experiences with you.

  @Joseph-TP Thanks. I already use 8.8.8.8 but having read a little more it may relate to the fact that I am on the beta 1.7.0 firmware as I've now observed that others report this sort of behaviour. 

  @larkim 

Hi

I have included a Beta in your message to help address this issue. But you may need to refer to the following link to upgrade through firmware recovery：

How to use firmware recovery

  @Joseph-TP Thanks, but I'm a little confused as to what you mean?  

I've got the 1.7.0 beta installed on all my devices, for the benefit of the "connection preference" option which has solved issues I did have with keeping the connections strong throughout my house.  I don't want to reverse that if possible, but if it's a trade off with persisting with the messages showing devices offline when they are not OR keeping the connection preferences option available, I'd prefer to stick with the connection preferences beta firmware.

However, if you're saying there is a new / different beta that I could try that resolves my issue with the "device not connected" messages as well as the connection preferences option being available, I'm ready to hear it!

Once again, thanks for dropping into the thread and providing input!!   

Edit - sorry, I understand now - I've seen the direct message!!