Dashticz - Bug report

[robgeerts]

With the latest beta, all my RFXMeter counter type blocks, generate a third block with 'undefined':

In Dashtics:
HeatDashticks.jpg

In Domoticz default:
HeatDomo.jpg

This is tested with a default config, with only the Domiticz ip and port modified.

Fixed in latest beta!

[madrian]

Hi Rob,

what about this (standby bug), sorry for posting on wrong place.

[robgeerts]

Hmm do you have latest version??
Whats your config? Standby is working correctly over here..

[Phantom]

when the standby screen is active it switches back to the main screen for a second and then back again to the standby every time the status of a switch changes.

Is there any way to turn this off, so it only go to the main screen when you touch the screen and not automatically?

[jake]

With latest beta, both Chrome and Maxthon will crash after a couple hours, or just freeze. I switched to an old 'stable' version and copied my custom-folder from the beta to the stable. That version runs fine now for 2-3 days. I therefore can conclude that it's neither the tablet nor the 'server' that runs the webpage.

With the beta version I saw that loading the garbage bin information and the (google) calendar element didn't work quite often and only give a 'loading...' sign.
The stable version I use, doesn't support yet the calendar and public transport blocks. During the last beta update, I saw an updat for main.js and trash.js, if I'm not mistaken.

[Phantom]

when the standby screen is active it switches back to the main screen for a second and then back again to the standby every time the status of a switch changes.

Is there any way to turn this off, so it only go to the main screen when you touch the screen and not automatically?

Sadly still waiting for an reply on this after a few weeks.

[robgeerts]

Sorry Phantom! Will test this tomorrow evening again. Already tested this with my dashboard but didnt have this problem.

[robgeerts]

when the standby screen is active it switches back to the main screen for a second and then back again to the standby every time the status of a switch changes.

Is there any way to turn this off, so it only go to the main screen when you touch the screen and not automatically?

Sadly still waiting for an reply on this after a few weeks.

Please try latest beta!!

[Phantom]

when the standby screen is active it switches back to the main screen for a second and then back again to the standby every time the status of a switch changes.

Is there any way to turn this off, so it only go to the main screen when you touch the screen and not automatically?

Sadly still waiting for an reply on this after a few weeks.

Please try latest beta!!

Thanks it works great now.

[jake]

With latest beta, both Chrome and Maxthon will crash after a couple hours, or just freeze. I switched to an old 'stable' version and copied my custom-folder from the beta to the stable. That version runs fine now for 2-3 days. I therefore can conclude that it's neither the tablet nor the 'server' that runs the webpage.

With the beta version I saw that loading the garbage bin information and the (google) calendar element didn't work quite often and only give a 'loading...' sign.
The stable version I use, doesn't support yet the calendar and public transport blocks. During the last beta update, I saw an updat for main.js and trash.js, if I'm not mistaken.

I updated to the 13-6 beta, but the issue of freezing screen after some time (clock also doesn't update anymore) is still there. How can I (help to) resolve the issue, while I run it on an Android tablet?

[robgeerts]

I'm currently testing this with some minor changes... will get back to you later today..

[robgeerts]

With latest beta, both Chrome and Maxthon will crash after a couple hours, or just freeze. I switched to an old 'stable' version and copied my custom-folder from the beta to the stable. That version runs fine now for 2-3 days. I therefore can conclude that it's neither the tablet nor the 'server' that runs the webpage.

With the beta version I saw that loading the garbage bin information and the (google) calendar element didn't work quite often and only give a 'loading...' sign.
The stable version I use, doesn't support yet the calendar and public transport blocks. During the last beta update, I saw an updat for main.js and trash.js, if I'm not mistaken.

I updated to the 13-6 beta, but the issue of freezing screen after some time (clock also doesn't update anymore) is still there. How can I (help to) resolve the issue, while I run it on an Android tablet?

Could you test latest beta?

[capman]

Get some error in my dashticz frontpage. Browser firefox and also on chrome.

[jake]

With latest beta, both Chrome and Maxthon will crash after a couple hours, or just freeze. I switched to an old 'stable' version and copied my custom-folder from the beta to the stable. That version runs fine now for 2-3 days. I therefore can conclude that it's neither the tablet nor the 'server' that runs the webpage.

Could you test latest beta?

I have the tablet now running for 2 days after your changes and it is running OK now, the issue of freezing or crashing is gone! Thanks!

However, I still experience a more slow performance when the website runs for more than half a day. At start the CPU is at 30%, but hours/day later, it has raised to 70%. Killing the browser and restarting it, lowers the CPU usage down to 30% again. At the 70% the usage raises to 100% when I try to switch to a 2nd page. Doing so goes fine right after I start the webpage, but takes more than 5 seconds after a day or so.

Is there a possibility to find out what is slowing the website down after time (on a Android tablet)?

[dutchdevil83]

On Ipad 2 (using Safari) after a couple of hours it also crashes. Sometimes after few hours, sometimes after half a day but not getting it stable for more then 1 day. Is there someway to log this so i can see when it crashes? Have installed latest beta version from github.

[robgeerts]

There should be tools to show whats causing the crashes but dont know wich one..
Does anyone have experience with this?

[jake]

Could you test latest beta?

I have the tablet now running for 2 days after your changes and it is running OK now, the issue of freezing or crashing is gone! Thanks!

However, I still experience a more slow performance when the website runs for more than half a day. At start the CPU is at 30%, but hours/day later, it has raised to 70%. Killing the browser and restarting it, lowers the CPU usage down to 30% again. At the 70% the usage raises to 100% when I try to switch to a 2nd page. Doing so goes fine right after I start the webpage, but takes more than 5 seconds after a day or so.

Is there a possibility to find out what is slowing the website down after time (on a Android tablet)?

In the 'Show your Dashboard' topic another used has no issues with the same Samsung Tab 3 8.0 tablet (SM-T310). The only difference was that I had the tablet running on a custom ROM, while he had the original Samsung Touchwiz ROM. I would expect that the behavior was inversed (better performance with a lean custom ROM). I have tried the default LOS 14.1, but also Xenon HD, both Android Nougat. The performance with Dashticz was equally bad over time (other websites run smooth, no other issues with these ROM's).
To outrule the standard Samsung ROM's experience, I decided to put NoleKat.T310. v1.1 (a tweaked version of the stock touchwiz experience, based on Android KitKat) and... the Dashticz runs smooth for days, no hickups by moving through screens. Just as it is intended to be.
= happy Dashticz user

[robgeerts]

Get some error in my dashticz frontpage. Browser firefox and also on chrome.

Is it possible to find out wich device causes this problem?
Maybe by removing each IDX from your config.js one by one?

[jake]

Wrong display of sensor value for 'multi-value' sensors when used in multiple columns.

Explanation of the cryptic sentence above:

I have the following block defined:

Code: Select all

blocks[127] = {}
blocks[127]['width'] = 3;
blocks[127]['title'] = 'Buiten'

I use it in 2 columns (displayed on 2 different pages), but in column 1 as '127_1' and in column 2 as 127
The second 127 was by accident, I forgot to add the _1 to it.

On the webpage it displayed to my surprise all 3 values on the 1st column (on page 1), scrolling to page 2, I saw the same. I have now updated the 2nd column also to '127_1' and now everything is back to normal. If I want to show all 3 values on page 2, I can of course do a '127_1', '127_2', '127_3' as a work around to avoid the error.

[Jan Jansen]

With the latest beta, all my RFXMeter counter type blocks, generate a third block with 'undefined':

In Dashtics:
HeatDashticks.jpg

In Domoticz default:
HeatDomo.jpg

This is tested with a default config, with only the Domiticz ip and port modified.

Fixed in latest beta!

My Domoticz dashboard shows:

Water2.PNG (17.13 KiB) Viewed 2511 times

Using the latest beta Dashticz shows:

Water1.PNG (19.8 KiB) Viewed 2511 times

I do not need "Total water", but I need the space of the block urgently. How can I fix that?