# Flowfuse Dashboard out of sync

**URL:** <https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528>\
**Category:** Dashboard\
**Tags:** flowfuse, dashboard-2\
**Created:** [6 June 2024 05:55 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528 "2024-06-06T05:55:13Z")\
**Posts on this page:** 11\
**Page:** 2

<div class="post-metadata">

**Author:** ![bltDefender](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bltdefender/32/33722_2.png) [@bltDefender](https://discourse.nodered.org/u/bltDefender)\
**Post date:** [8 June 2024 09:26 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/21 "2024-06-08T09:26:01Z")

</div>

I also put the event node against a debug node to see if I can catch any other msg.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 June 2024 09:34 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/22 "2024-06-08T09:34:58Z")

</div>

> [@bltDefender](#):
>
> put another, older android pad in place in parallel. first two days, no disconnect from this dashboard.

Oh, perhaps it is a hardware problem after all.

---

<div class="post-metadata">

**Author:** ![bltDefender](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bltdefender/32/33722_2.png) [@bltDefender](https://discourse.nodered.org/u/bltDefender)\
**Post date:** [8 June 2024 09:37 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/23 "2024-06-08T09:37:04Z")

</div>

> [@Colin](#):
>
> Oh, perhaps it is a hardware problem after all.

you mean there is kinda wipe in the wifi connection and it cannot recover by itself?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 June 2024 09:43 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/24 "2024-06-08T09:43:10Z")

</div>

It can't be the wifi dropping out, or you would get the Connection Lost message, as you do when you switch off the wifi, that is why I thought it must be node-red related. But if you have another device that does not show the issue then it is difficult to see what the problem is.

Perhaps not hardware, perhaps something to do with the version of Android or another app that you have installed. I don't see this problem with current Android though.

You said earlier,

> [@bltDefender](#):
>
> > [@Colin](#):
> >
> > Do you mean that it has triggered the error, so your slider does not work? If so, then that should make it easier to analyse as you can now get into the error state easily.
> 
> no, there is no debug msg showing up. means there is no queued msg that get through to the server once the connection is back again.

It isn't clear to me exactly what you mean.

1. Does the slider work after switching the wifi off and on again?
2. I am not sure whether you answered, when it has failed, if you switch to a different page and back again does it start working?

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [8 June 2024 10:17 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/25 "2024-06-08T10:17:04Z")

</div>

Have you monitored device memory usage?

---

<div class="post-metadata">

**Author:** ![bltDefender](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bltdefender/32/33722_2.png) [@bltDefender](https://discourse.nodered.org/u/bltDefender)\
**Post date:** [20 June 2024 07:32 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/26 "2024-06-20T07:32:42Z")

</div>

> [@hotNipi](#):
>
> Have you monitored device memory usa

Yes, as well as other indicators from the os. All in very good state.

---

<div class="post-metadata">

**Author:** ![bltDefender](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bltdefender/32/33722_2.png) [@bltDefender](https://discourse.nodered.org/u/bltDefender)\
**Post date:** [20 June 2024 07:36 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/27 "2024-06-20T07:36:40Z")

</div>

I managed to have another device to compare with. Result from the last days is, it is an Hardware or OS issue. Running the dashboard on TAB A7 does not run out of sync. The one on the Blackview Tab 11 does. Will try to find an alternative ROM and see if that is OS related. Thank you @Colin for all your support, in the end you had the right hint 🙂

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [20 June 2024 10:33 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/28 "2024-06-20T10:33:07Z")

</div>

> [@bltDefender](#):
>
> it is an Hardware or OS issue.

Or browser.

---

<div class="post-metadata">

**Author:** ![bltDefender](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bltdefender/32/33722_2.png) [@bltDefender](https://discourse.nodered.org/u/bltDefender)\
**Post date:** [21 June 2024 12:49 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/29 "2024-06-21T12:49:47Z")

</div>

> [@Colin](#):
>
> Or browser.

I tried all know browsers with the exact same version on the exact same android version (excl. bloat ware for sure) on the other tablet. I guess there is kind of an energy management in the background which is not configurable properly.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [21 June 2024 15:29 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/30 "2024-06-21T15:29:29Z")

</div>

> [@bltDefender](#):
>
> kind of an energy management in the background

All Android devices I have used are liable to disconnect if not kept active by user interaction. They should try automatically to reconnect, which seems not to be happening for you. There are some further tweaks to connection code in 1.12 so it might be worth trying that.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 July 2024 15:29 UTC](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528/31 "2024-07-21T15:29:49Z")

</div>

Closed on 21 July 2024 15:29 UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/flowfuse-dashboard-out-of-sync/88528.md?page=1)