Dashticz won't show lacrosse tx3 type temp reading while domoticz does. Topic is solved

Dashticz, alternative dashboard based on HTML, CSS, jQuery

Moderators: leecollings, htilburgs, robgeerts

Post Reply
Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

I can't get Dashticz to show the temp reading of the inverter.

In domoticz I get a correct reading of 32° C.

In dashticz the block remains empty and the following blocks in the column are not shown anymore.
Also the page sliding didn't work anymore and the second page is displayed under the first page. So with scrolling down you get the second page.
I use the latest beta.

Code: Select all

https://192.168.xxx.xxx/json.htm?type=devices&plan=0&filter=all&used=true&order=Name
Spoiler: show
"[
0
],
"Protected" : false,
"ShowNotifications" : true,
"SignalLevel" : "-",
"SubType" : "LaCrosse TX3",
"Temp" : 32.0,
"Timers" : "false",
"Type" : "Temp",
"TypeImg" : "temperature",
"Unit" : 1,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "352",
"trend" : 2

Code: Select all

}
blocks['352'] = {
 title: 'Temp Omvormer',
 width: 4
}
Any ideas?
Last edited by Douwe on Saturday 03 October 2020 14:58, edited 1 time in total.
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

Did you already try with

Code: Select all

config['use_favorites'] = false;

Sent from my SM-A320FL using Tapatalk

Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

Lokonli wrote: Saturday 03 October 2020 14:38 Did you already try with

Code: Select all

config['use_favorites'] = false;

Sent from my SM-A320FL using Tapatalk
Thanks for helping me!
But that didn't change it.
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

Open DevTools in Chrome by pressing F12. Refresh Dashticz.

Which error is reported in DevTools console tab?

Sent from my SM-A320FL using Tapatalk

Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

Lokonli wrote: Saturday 03 October 2020 15:09 Open DevTools in Chrome by pressing F12. Refresh Dashticz.

Which error is reported in DevTools console tab?

Sent from my SM-A320FL using Tapatalk
Hope this is what you asked:

Code: Select all

TypeError: deviceValue is undefined
    getStatusBlock js/blocks.js:783
    createBlocks js/blocks.js:1945
    createBlocks js/blocks.js:1908
    getBlockTypesBlock js/blocktypes.js:314
    handleDevice js/blocks.js:1293
    deviceUpdateHandler js/blocks.js:174
    addDeviceUpdateHandler js/blocks.js:226
    subscribe js/domoticz-api.js:533
    subscribe js/domoticz-api.js:454
    addDeviceUpdateHandler js/blocks.js:224
    getBlock js/blocks.js:82
    buildScreens js/main.js:619
    onLoad js/main.js:345
    loadFiles js/main.js:295
    mightThrow http://192.168.178.116:8082/dist/bundle.js?t=5:305
    F http://192.168.178.116:8082/dist/bundle.js?t=5:305
js/main.js:299:15
XML-parsefout: ongedefinieerde entiteit
Locatie: http://192.168.178.116:8082/tpl/graph_header.tpl
Regelnummer 5, kolom 65: graph_header.tpl:5:65
Uncaught TypeError: deviceValue is undefined
    getStatusBlock js/blocks.js:783
    createBlocks js/blocks.js:1945
    createBlocks js/blocks.js:1908
    getBlockTypesBlock js/blocktypes.js:314
    handleDevice js/blocks.js:1293
    deviceUpdateHandler js/blocks.js:174
    addDeviceUpdateHandler js/blocks.js:226
    set js/domoticz-api.js:561
    set js/domoticz-api.js:560
    setOnChange js/domoticz-api.js:348
    _setAllDevices js/domoticz-api.js:371
    onmessage js/domoticz-api.js:207
line 294 > injectedScript:783:28
XML-parsefout: troep na documentelement
Locatie: http://192.168.178.116:8082/tpl/graph_tooltip.tpl
Regelnummer 16, kolom 1: graph_tooltip.tpl:16:1
Uncaught TypeError: deviceValue is undefined
    getStatusBlock js/blocks.js:783
    createBlocks js/blocks.js:1945
    createBlocks js/blocks.js:1908
    getBlockTypesBlock js/blocktypes.js:314
    handleDevice js/blocks.js:1293
    deviceUpdateHandler js/blocks.js:174
    addDeviceUpdateHandler js/blocks.js:226
    set js/domoticz-api.js:561
    set js/domoticz-api.js:560
    setOnChange js/domoticz-api.js:348
    _setAllDevices js/domoticz-api.js:371
    onmessage js/domoticz-api.js:207
line 294 > injectedScript:783:28
    getStatusBlock js/blocks.js:783
    createBlocks js/blocks.js:1945
    forEach self-hosted:206
    createBlocks js/blocks.js:1908
    getBlockTypesBlock js/blocktypes.js:314
    handleDevice js/blocks.js:1293
    deviceUpdateHandler js/blocks.js:174
    addDeviceUpdateHandler js/blocks.js:226
    set js/domoticz-api.js:561
    forEach self-hosted:206
    set js/domoticz-api.js:560
    setOnChange js/domoticz-api.js:348
    _setAllDevices js/domoticz-api.js:371
    onmessage js/domoticz-api.js:207

​
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

There are indeed some errors reported. Now we have to find out what's causing this.

It seems there are at least two errors: one in a graph header, and one with a Domoticz block.
It can be caused by Domoticz block id 352, but it can also be something else.

First, can you remove domoticz id 352 from the column definition, and also the graphs that are using device 352?

Refresh Dashticz and check again whether the DevTools console is error free.

If there are still errors reported without device 352 we take the next step in debugging.
Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

Thanks for your help Lokonli! very much appreciated.

When I remove IDX 352 form the column I get the following warning (but no errors):

Code: Select all

DevTools failed to load SourceMap: Could not load content for http://192.168.178.116:8082/ical.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
The page sliding is working again.
(there was no graph for 352 added to CONFIG.js)
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

ok, then the problem is indeed related to device 352.

What is your exact Dashticz version? If it's lower than 3.6 please switch to 3.6 master (or latest beta) first.

If your custom.js is not empty, can you post it here?

Do you have a block definition for device 352 in CONFIG.js? If yes, can you post that part here?

On what kind of system did you install Dashticz? (windows, Ubuntu, Pi, Synology)
Domoticz is on the same system?

Can you post the complete Domoticz json output for device 352:

Code: Select all

http://192.168.178.116:8082/json.htm?type=devices&rid=352
Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

Hi Lokonli,

Again, your help is very much appreciated!

I am on a Pi 2 b (with buster)
domoticz is on the same system.

custom.js:

Code: Select all

pi@raspDomo:~/dev/dashticz/custom $ more custom.js
 //add custom javascript in here
/*
function afterGetDevices(){
if (Domoticz.getAllDevices()[s2].Data == 'Off') {
$('.block_S2 .title').addClass('warningblue');
$('.block_S2 .state').addClass('warningblue');
}
else {
$('.block_s2 .title').removeClass('warningblue');
$('.block_s2 .state').removeClass('warningblue');
}
}
*/
function getExtendedBlockTypes(blocktypes){
        //blocktypes.Type['Lighting 2'] = { icon: 'fa fa-lightbulb-o', title: '<Name>', value: 'ds' }
        return blocktypes;
}
pi@raspDomo:~/dev/dashticz/custom $
version:

Code: Select all

pi@raspDomo:~/dev/dashticz $ more version.txt
{
"version": "3.6.3",
"branch": "beta",
"last_changes": "More dials",
"changelog" : {
            "3.6.2": "Fix for graph issues in 3.6",
            "3.6.1": "Custom HTML block",
            "3.6.0": "Beta version derived from 3.6 master",
            "3.6": "Master version"
            }
}
CONFIG.js:

Code: Select all

}
blocks['352'] = {
 title: 'Temp Omvormer',
 width: 4
}

Your url:

Code: Select all

http://192.168.178.116:8082/json.htm?type=devices&rid=352
gave a '404' result (page not found)

Code: Select all

http://192.168.178.116:8080/json.htm?type=devices&plan=0&filter=all&used=true&order=Name
copied the 352 part

Code: Select all

{
			"AddjMulti" : 1.0,
			"AddjMulti2" : 1.0,
			"AddjValue" : 0.0,
			"AddjValue2" : 0.0,
			"BatteryLevel" : 255,
			"CustomImage" : 0,
			"Data" : "32.0 C",
			"Description" : "",
			"Favorite" : 1,
			"HardwareID" : 17,
			"HardwareName" : "PVOUtput",
			"HardwareType" : "PVOutput (Input)",
			"HardwareTypeVal" : 30,
			"HaveTimeout" : false,
			"ID" : "0001",
			"LastUpdate" : "2020-10-05 18:20:22",
			"Name" : "Temperatuur Omvormer",
			"Notifications" : "false",
			"PlanID" : "0",
			"PlanIDs" : 
			[
				0
			],
			"Protected" : false,
			"ShowNotifications" : true,
			"SignalLevel" : "-",
			"SubType" : "LaCrosse TX3",
			"Temp" : 32.0,
			"Timers" : "false",
			"Type" : "Temp",
			"TypeImg" : "temperature",
			"Unit" : 1,
			"Used" : 1,
			"XOffset" : "0",
			"YOffset" : "0",
			"idx" : "352",
			"trend" : 2
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

I see the HardwareType is 'PVOutput (Input)'

A specific blocktype is defined for this kind of hardware, but I see in the code that the assumption is that it's an energy device, not a temperature.

Do you also use other PVOutput devices?

As a quick hack, can you try with the following in custom.js (the function getExtendedBlockType is changed):
(other PVOutput devices will not work anymore!)

Code: Select all

 //add custom javascript in here
/*
function afterGetDevices(){
if (Domoticz.getAllDevices()[s2].Data == 'Off') {
$('.block_S2 .title').addClass('warningblue');
$('.block_S2 .state').addClass('warningblue');
}
else {
$('.block_s2 .title').removeClass('warningblue');
$('.block_s2 .state').removeClass('warningblue');
}
}
*/
function getExtendedBlockTypes(blocktypes){
        //blocktypes.Type['Lighting 2'] = { icon: 'fa fa-lightbulb-o', title: '<Name>', value: 'ds' }
        blocktypes.HardwareType['PVOutput (Input)'] = {
          icon: 'fas fa-thermometer-half',
	  title: '<Name>',
  	value: '<Temp>' + _TEMP_SYMBOL,
  	format: true,
  	decimals: 1,

        };
        return blocktypes;
}
If this solves the issue with the temperature device, I'll think of a real fix.
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

Can you post the Domoticz json output of all your PVOutput devices?
Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Douwe »

Lokonli wrote: Monday 05 October 2020 19:00 I see the HardwareType is 'PVOutput (Input)'

A specific blocktype is defined for this kind of hardware, but I see in the code that the assumption is that it's an energy device, not a temperature.

Do you also use other PVOutput devices?

As a quick hack, can you try with the following in custom.js (the function getExtendedBlockType is changed):
(other PVOutput devices will not work anymore!)

Code: Select all

 //add custom javascript in here
/*
function afterGetDevices(){
if (Domoticz.getAllDevices()[s2].Data == 'Off') {
$('.block_S2 .title').addClass('warningblue');
$('.block_S2 .state').addClass('warningblue');
}
else {
$('.block_s2 .title').removeClass('warningblue');
$('.block_s2 .state').removeClass('warningblue');
}
}
*/
function getExtendedBlockTypes(blocktypes){
        //blocktypes.Type['Lighting 2'] = { icon: 'fa fa-lightbulb-o', title: '<Name>', value: 'ds' }
        blocktypes.HardwareType['PVOutput (Input)'] = {
          icon: 'fas fa-thermometer-half',
	  title: '<Name>',
  	value: '<Temp>' + _TEMP_SYMBOL,
  	format: true,
  	decimals: 1,

        };
        return blocktypes;
}
If this solves the issue with the temperature device, I'll think of a real fix.
Hi,

I changed custom.js with the code you wrote. The result is that the block 352 is displayed correctly.

However, as you remarked, is the rest of the blocks coming from PVOutput(input) disappeared and after block 352 is the rest of the page/column empty.

Here the other PVPOutput(input) data:

Code: Select all

{
			"AddjMulti" : 1.0,
			"AddjMulti2" : 1.0,
			"AddjValue" : 0.0,
			"AddjValue2" : 0.0,
			"BatteryLevel" : 255,
			"CounterToday" : "6.000 kWh",
			"CustomImage" : 0,
			"Data" : "25289.600 kWh",
			"Description" : "",
			"EnergyMeterMode" : "0",
			"Favorite" : 1,
			"HardwareID" : 17,
			"HardwareName" : "PVOUtput",
			"HardwareType" : "PVOutput (Input)",
			"HardwareTypeVal" : 30,
			"HaveTimeout" : false,
			"ID" : "00000001",
			"LastUpdate" : "2020-10-05 22:45:23",
			"Name" : "SolarMain",
			"Notifications" : "false",
			"PlanID" : "0",
			"PlanIDs" : 
			[
				0
			],
			"Protected" : false,
			"ShowNotifications" : true,
			"SignalLevel" : "-",
			"SubType" : "kWh",
			"SwitchTypeVal" : 4,
			"Timers" : "false",
			"Type" : "General",
			"TypeImg" : "current",
			"Unit" : 1,
			"Usage" : "0 Watt",
			"Used" : 1,
			"XOffset" : "0",
			"YOffset" : "0",
			"idx" : "353"
		},
		{
			"AddjMulti" : 1.0,
			"AddjMulti2" : 1.0,
			"AddjValue" : 0.0,
			"AddjValue2" : 0.0,
			"BatteryLevel" : 255,
			"CounterToday" : "37.480 kWh",
			"CustomImage" : 0,
			"Data" : "63236.488 kWh",
			"Description" : "",
			"EnergyMeterMode" : "",
			"Favorite" : 1,
			"HardwareID" : 17,
			"HardwareName" : "PVOUtput",
			"HardwareType" : "PVOutput (Input)",
			"HardwareTypeVal" : 30,
			"HaveTimeout" : false,
			"ID" : "00000002",
			"LastUpdate" : "2020-10-05 22:45:23",
			"Name" : "SolarConsumed",
			"Notifications" : "false",
			"PlanID" : "0",
			"PlanIDs" : 
			[
				0
			],
			"Protected" : false,
			"ShowNotifications" : true,
			"SignalLevel" : "-",
			"SubType" : "kWh",
			"SwitchTypeVal" : 0,
			"Timers" : "false",
			"Type" : "General",
			"TypeImg" : "current",
			"Unit" : 1,
			"Usage" : "1337 Watt",
			"Used" : 1,
			"XOffset" : "0",
			"YOffset" : "0",
			"idx" : "354"
		},
For 'SolarMain' (IDX 353) and 'SolarConsumed' (IDX 354) a total of 6 blocks are generated. For me at the moment not totally clear, what the values displayed are saying.
So the solution you suggested is not a total fix for the problem.
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

Douwe wrote: Monday 05 October 2020 23:07 For 'SolarMain' (IDX 353) and 'SolarConsumed' (IDX 354) a total of 6 blocks are generated. For me at the moment not totally clear, what the values displayed are saying.
So the solution you suggested is not a total fix for the problem.
Should be fixed in latest beta. Can you test?

You have to reverse you changes to the getExtendedBlockTypes function in custom.js:

Code: Select all

function getExtendedBlockTypes(blocktypes){
        //blocktypes.Type['Lighting 2'] = { icon: 'fa fa-lightbulb-o', title: '<Name>', value: 'ds' }
        return blocktypes;
}
The PVOutput energy devices will create three blocks: Total Energy, Energy today, Actual power.
If you only want to show the actual power, you have to use '353_3' and '354_3' as device ids.
Douwe
Posts: 8
Joined: Saturday 02 April 2016 10:20
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does. [SOLVED]

Post by Douwe »

Hi Lokonli,

Thanks for your help. After the update the PVOutput temp block works fine and also the other PVOutput blocks were displayed.

For your information I added a jpg with the PVOutput devices.

So I think this is solved!
Attachments
pvoutput_dev.JPG
pvoutput_dev.JPG (84.79 KiB) Viewed 946 times
Lokonli
Posts: 2291
Joined: Monday 29 August 2016 22:40
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Dashticz won't show lacrosse tx3 type temp reading while domoticz does.

Post by Lokonli »

Great! Thanks for the feedback :)
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest