Page 2 of 28

Re: Dashticz - Bug report

Posted: Sunday 07 May 2017 21:04
by HansieNL
Just updated to latest beta and all the trash info is gone. I have only the icon left. Anyone else has same problem?

EDIT: Fixed :D

Re: Dashticz - Bug report

Posted: Sunday 07 May 2017 21:07
by robgeerts
Fixed in beta!

Re: Dashticz - Bug report

Posted: Sunday 07 May 2017 21:09
by htilburgs
robgeerts wrote:Fixed in beta!
Confirmed! And the new var trashnames / colors work nice!!

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 9:15
by Blueone
robgeerts wrote:
Blueone wrote:There appear to be a new bug with the thermostat function. Every 5 seconds (the refresh time) there is a class added to the thermostat setpoint. When you increase or decrease the setpoint the action is done for every added class, zo if you have the dashboard open for a couple of minutes the classed several dozens of classes are added to the setpoint, and it is going to change the setpoint for every class and one click will change the setpoint with 10 degrees for example:

thermostat.png
Please test in latest beta!

Sorry, not working yet, I know have one setpoint with loads of classes which increases with every refresh and one setpoint without a thermostat**** class. The up and down aren't working at all.

I also verified the code I added in the addthermostat function in main.js but that isn't causing the issue.

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 9:18
by robgeerts
Could you try once in another browser?

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 9:47
by Blueone
My mistake, I had some code in custom.js which was interfering. Both setpoint don't have a thermostat class at all at the moment, so changing the setpoint doesn't work but the multiple classes are gone.

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 10:35
by robgeerts
Those classes arent used anymore ;)

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 10:40
by Blueone
Oke clear, but the increase and decrease doenst work at the moment :P, so there is still a small bug somewhere.

Re: Dashticz - Bug report

Posted: Monday 08 May 2017 11:07
by maninblack30
on the latest master I have a selector switch, if I operate any other switch once, the drop-down for the selector doesn't stay open long enough for me to select, tried chrome and IE. it works fine if it's the first switch i use after a reload, but as soon as I operate anything else it breaks again.
Ta,

Re: Dashticz - Bug report

Posted: Tuesday 09 May 2017 9:02
by mikeoo
Updated to latest beta and cleared the cache.

I use some door sensors with Xiaomi Mi Smart Home Gateway 2.
Added them to Dashticz and try to use some other icons instead of the default ones because i want to use the doorsensor as a windowssensor.

For the test i use this in config.js

Code: Select all

blocks[1980] = {}
blocks[1980]['icon'] = 'fa-window-close';
blocks[1980]['title'] = 'Voordeur';
blocks[1980]['show_lastupdate'] = true;
But it keeps the default doorsensor icon .

When i do the same for a dummy switch it is working fine.

Re: Dashticz - Bug report

Posted: Tuesday 09 May 2017 18:37
by qwerk
hi,

since today I get

a java error main.js/v=54 line:417

It is not the lat beta also before that.
Is it my installation, or is dashticz?

Re: Dashticz - Bug report

Posted: Tuesday 09 May 2017 18:59
by HansieNL
mikeoo wrote:Updated to latest beta and cleared the cache.

I use some door sensors with Xiaomi Mi Smart Home Gateway 2.
Added them to Dashticz and try to use some other icons instead of the default ones because i want to use the doorsensor as a windowssensor.

For the test i use this in config.js

Code: Select all

blocks[1980] = {}
blocks[1980]['icon'] = 'fa-window-close';
blocks[1980]['title'] = 'Voordeur';
blocks[1980]['show_lastupdate'] = true;
But it keeps the default doorsensor icon .

When i do the same for a dummy switch it is working fine.
I'm not sure of this works in your case... maybe you can try? Add following code to custom.js. Change to your own icon.

Code: Select all

function getBlock_1980(device,idx){ 
   $('.block_'+idx).attr('onclick','switchDevice(this)');
   var html='';
   html+='<div class="col-xs-4 col-icon">';
      if(device['Status']=='Closed') html+='<img src="img/your_icon_closed.png" class="off icon" />';
      else html+='<img src="img/your_icon_open.png" class="on icon" />';
   html+='</div>';
   html+='<div class="col-xs-8 col-data">';
   html+='<strong class="title">'+device['Name']+'</strong><br />';
   if(device['Status']=='Off') html+='<span class="state">Closed</span>';
   else html+='<span class="state">Open</span>';
 
   if(_SHOW_LASTUPDATE) html+='<br /><span class="lastupdate">'+moment(device['LastUpdate']).format(_LASTUPDATE_FORMAT)+'</span>';
   html+='</div>';
   return html;
}

Re: Dashticz - Bug report

Posted: Tuesday 09 May 2017 22:42
by robgeerts
qwerk wrote:hi,

since today I get

a java error main.js/v=54 line:417

It is not the lat beta also before that.
Is it my installation, or is dashticz?
Try latest beta..
Do you still have the issue in this version?

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 7:55
by qwerk
robgeerts wrote:
qwerk wrote:hi,

since today I get

a java error main.js/v=54 line:417

It is not the lat beta also before that.
Is it my installation, or is dashticz?
Try latest beta..
Do you still have the issue in this version?
had it a few tmes with at least two dashticz versions

moved to latest beta and other webserver.
did not have it anymore

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 10:24
by mikeoo
HansieNL wrote:
mikeoo wrote:Updated to latest beta and cleared the cache.

I use some door sensors with Xiaomi Mi Smart Home Gateway 2.
Added them to Dashticz and try to use some other icons instead of the default ones because i want to use the doorsensor as a windowssensor.

For the test i use this in config.js

Code: Select all

blocks[1980] = {}
blocks[1980]['icon'] = 'fa-window-close';
blocks[1980]['title'] = 'Voordeur';
blocks[1980]['show_lastupdate'] = true;
But it keeps the default doorsensor icon .

When i do the same for a dummy switch it is working fine.
I'm not sure of this works in your case... maybe you can try? Add following code to custom.js. Change to your own icon.

Code: Select all

function getBlock_1980(device,idx){ 
   $('.block_'+idx).attr('onclick','switchDevice(this)');
   var html='';
   html+='<div class="col-xs-4 col-icon">';
      if(device['Status']=='Closed') html+='<img src="img/your_icon_closed.png" class="off icon" />';
      else html+='<img src="img/your_icon_open.png" class="on icon" />';
   html+='</div>';
   html+='<div class="col-xs-8 col-data">';
   html+='<strong class="title">'+device['Name']+'</strong><br />';
   if(device['Status']=='Off') html+='<span class="state">Closed</span>';
   else html+='<span class="state">Open</span>';
 
   if(_SHOW_LASTUPDATE) html+='<br /><span class="lastupdate">'+moment(device['LastUpdate']).format(_LASTUPDATE_FORMAT)+'</span>';
   html+='</div>';
   return html;
}
Nice, code is working fine.
Only problem when you need to use it for more sensors you get a lot of extra code in custom.js for every sensor.
Why does it works for most sensor when you change the icon in CONFIG.js but not for this type of sensor.

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 10:26
by Blueone
Blueone wrote:Oke clear, but the increase and decrease doenst work at the moment :P, so there is still a small bug somewhere.
Oke, i found the bug in this piece of code:
[/code]
if(typeof(addedThermostat[idx])=='undefined'){
addThermostatFunctions('.block_'+idx+'_2');
addedThermostat[idx] = true;
}
[/code]

The ‘_2’ is hardcoded while not every setpoint block contains the _2, for example, mine setpoint block class is simply Block_628, so the clickevent isn’t added to the block.

BTW: The thermostatfunctions are also added to the temperature blocks at the moment, not really an issue but it isn’t nessecary ;)

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 11:24
by robgeerts
Thanks for finding the bug, will fix this asap!

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 13:20
by robgeerts
Blueone wrote:
Blueone wrote:Oke clear, but the increase and decrease doenst work at the moment :P, so there is still a small bug somewhere.
Oke, i found the bug in this piece of code:
[/code]
if(typeof(addedThermostat[idx])=='undefined'){
addThermostatFunctions('.block_'+idx+'_2');
addedThermostat[idx] = true;
}
[/code]

The ‘_2’ is hardcoded while not every setpoint block contains the _2, for example, mine setpoint block class is simply Block_628, so the clickevent isn’t added to the block.

BTW: The thermostatfunctions are also added to the temperature blocks at the moment, not really an issue but it isn’t nessecary ;)
Could you test latest beta?

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 13:29
by robgeerts
mikeoo wrote:Updated to latest beta and cleared the cache.

I use some door sensors with Xiaomi Mi Smart Home Gateway 2.
Added them to Dashticz and try to use some other icons instead of the default ones because i want to use the doorsensor as a windowssensor.

For the test i use this in config.js

Code: Select all

blocks[1980] = {}
blocks[1980]['icon'] = 'fa-window-close';
blocks[1980]['title'] = 'Voordeur';
blocks[1980]['show_lastupdate'] = true;
But it keeps the default doorsensor icon .

When i do the same for a dummy switch it is working fine.
Should be fixed in latest beta!

Re: Dashticz - Bug report

Posted: Wednesday 10 May 2017 13:35
by htilburgs
@robgeerts, I'm using the index2 / custom_2 option right now. Works great, but....
Can it be that the custom.css doesn't work that's in this directory? Or did I miss something?