Page 40 of 184
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:06
by robgeerts
formadvi wrote:robgeerts wrote:
Try chaning the name from 'Regen Verwacht' to 'Regen verwacht'
(Yes, not very handy this way but will do this different soon!)
I have the same issue. Changed to Regen verwacht but still only Regen Aan
Do you have the latest version of the dashboard?
What is de output of your device?
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:12
by robgeerts
CUSTOM ICONS
You can now define other icons, in config.js:
Code: Select all
blocks[1] = {}
blocks[1]['icon'] = 'fa-eye';
Find an icon at
http://fontawesome.io/cheatsheet/
OR, if you want to use an image, place it in img/ folder and specify as:
Code: Select all
blocks[1] = {}
blocks[1]['image'] = 'bulb_off.png';
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:36
by SwordFish
Great job with the custum icons.
I just downloaded the latest version and its seems that the train info is gone, i only have traffic?
In the previous version it is still working.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:39
by formadvi
robgeerts wrote:formadvi wrote:robgeerts wrote:
Try chaning the name from 'Regen Verwacht' to 'Regen verwacht'
(Yes, not very handy this way but will do this different soon!)
I have the same issue. Changed to Regen verwacht but still only Regen Aan
Do you have the latest version of the dashboard?
What is de output of your device?
Ik heb eind van de middag de laatste versie geinstalleerd. Net laatste versie gepakt van 30 min geleden. Deze werkt correct.
Thanks.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:51
by EdwinK
robgeerts wrote:CUSTOM ICONS
For statusblocks (like rain expected, other text-types,lux, sound level, rain, wind, motherboard sensors, air quality) you can now define other icons, in config.js:
Awesome.
Still trying to get this looking better
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 20:58
by robgeerts
SwordFish wrote:Great job with the custum icons.
I just downloaded the latest version and its seems that the train info is gone, i only have traffic?
In the previous version it is still working.
Kun je de laatste versie eens proberen?
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:00
by robgeerts
EdKo66 wrote:robgeerts wrote:CUSTOM ICONS
For statusblocks (like rain expected, other text-types,lux, sound level, rain, wind, motherboard sensors, air quality) you can now define other icons, in config.js:
Awesome.
Still trying to get this looking better
What was the output of your rain evice? (Or did I ask that already earlier?
En your screen width, so I can test it..
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:02
by SwordFish
robgeerts wrote:SwordFish wrote:Great job with the custum icons.
I just downloaded the latest version and its seems that the train info is gone, i only have traffic?
In the previous version it is still working.
Kun je de laatste versie eens proberen?
Will try it tomorrow, not at home.
Verzonden vanaf mijn iPhone met Tapatalk
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:04
by EdwinK
robgeerts wrote:
En your screen width, so I can test it..
Device output:
Code: Select all
{
"ActTime" : 1492110156,
"ServerTime" : "2017-04-13 21:02:36",
"Sunrise" : "06:50",
"Sunset" : "20:35",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Geen regen verwacht binnen komende 30 minuten",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 24,
"HardwareName" : "Weer",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveTimeout" : false,
"ID" : "00082113",
"LastUpdate" : "2017-04-13 21:02:00",
"Name" : "Regen verwacht",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : false,
"SignalLevel" : "-",
"SubType" : "Text",
"Timers" : "false",
"Type" : "General",
"TypeImg" : "text",
"Unit" : 1,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "113"
}
],
"status" : "OK",
"title" : "Devices"
}
Not sure about screen width. Now on my MacBook. I believe it's a 13" inch version.
ould be nice if the tile could be a bit bigger, like the train-info.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:05
by robgeerts
EdKo66 wrote:robgeerts wrote:
En your screen width, so I can test it..
Device output:
Code: Select all
{
"ActTime" : 1492110156,
"ServerTime" : "2017-04-13 21:02:36",
"Sunrise" : "06:50",
"Sunset" : "20:35",
"result" : [
{
"AddjMulti" : 1.0,
"AddjMulti2" : 1.0,
"AddjValue" : 0.0,
"AddjValue2" : 0.0,
"BatteryLevel" : 255,
"CustomImage" : 0,
"Data" : "Geen regen verwacht binnen komende 30 minuten",
"Description" : "",
"Favorite" : 0,
"HardwareID" : 24,
"HardwareName" : "Weer",
"HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
"HardwareTypeVal" : 15,
"HaveTimeout" : false,
"ID" : "00082113",
"LastUpdate" : "2017-04-13 21:02:00",
"Name" : "Regen verwacht",
"Notifications" : "false",
"PlanID" : "0",
"PlanIDs" : [ 0 ],
"Protected" : false,
"ShowNotifications" : false,
"SignalLevel" : "-",
"SubType" : "Text",
"Timers" : "false",
"Type" : "General",
"TypeImg" : "text",
"Unit" : 1,
"Used" : 1,
"XOffset" : "0",
"YOffset" : "0",
"idx" : "113"
}
],
"status" : "OK",
"title" : "Devices"
}
Not sure about screen width. Now on my MacBook. I believe it's a 13" inch version.
ould be nice if the tile could be a bit bigger, like the train-info.
in that case, add to your config.js, just below blocks = {}
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:19
by Blueone
I'm using the raspberry touchscreen with the dashboard, I'm already glad there is a stand-by mode. The problem is the touchscreen is very still very bright.
There is a command to adjust the brightness:
echo n > /sys/class/backlight/rpi_backlight/brightness
n is the brightness level 0-255
Also found some sort of API for it:
https://github.com/linusg/rpi-backlight
Is there a way I can run this command somewhere in the code when it goes to standby? I also notice the stand-by view isn't completly black and white, see the screenshot, the text is a bit gray but the dot is really white which makes it a better contrast
- 2017-04-13 21_35_26-10.100.10.119 (Domoticz-Dashboard) - VNC Viewer.png (27.43 KiB) Viewed 2050 times
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:21
by rbo0567
robgeerts wrote:rbo0567 wrote:Hi Rob,
I'm following this thread a couple of days now and I appreciate your work in this thread a lot.
For me it became more interesting when the camera's got your attention. Tried it after downloading the latest version of Dashticz but can only get 1 camera working at the same time. I made a screen specially for 4 cams but I see only the image of 1 cam (4 times).
Am I doing something wrong?
I didnt test with multiple cams yet... will do this soon!
If there is something I can help you with, please let me know.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:37
by robgeerts
Blueone wrote:I'm using the raspberry touchscreen with the dashboard, I'm already glad there is a stand-by mode. The problem is the touchscreen is very still very bright.
There is a command to adjust the brightness:
echo n > /sys/class/backlight/rpi_backlight/brightness
n is the brightness level 0-255
Also found some sort of API for it:
https://github.com/linusg/rpi-backlight
Is there a way I can run this command somewhere in the code when it goes to standby? I also notice the stand-by view isn't completly black and white, see the screenshot, the text is a bit gray but the dot is really white which makes it a better contrast
2017-04-13 21_35_26-10.100.10.119 (Domoticz-Dashboard) - VNC Viewer.png
Well, I can only call URL's, (local or internet), so if you can create something wich activates via de browser, I can make a function for this.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:43
by robgeerts
Blueone wrote:I also notice the stand-by view isn't completly black and white, see the screenshot, the text is a bit gray but the dot is really white which makes it a better contrast
Try latest version
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 21:44
by Blueone
robgeerts wrote:
Well, I can only call URL's, (local or internet), so if you can create something wich activates via de browser, I can make a function for this.
Thanks! Maybe I can create a switch in domoticz which runs a python script or someting
, I'm going to sort this out
Thanks for the quick reply again!
robgeerts wrote:
Try latest version
cool, I'm going to try it.
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 22:09
by l00pz
Very nice update with the custom icons
, but is it also possible to get bigger icons as they are a little small on my Tablet (Retina China Tablet).
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 22:10
by EdwinK
robgeerts wrote:EdKo66 wrote:robgeerts wrote:
En your screen width, so I can test it..
...
Not sure about screen width. Now on my MacBook. I believe it's a 13" inch version.
ould be nice if the tile could be a bit bigger, like the train-info.
in that case, add to your config.js, just below blocks = {}
When I do that, this is what I get
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 22:32
by robgeerts
What does console (F12) say?
Looks like you got an error..
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 22:46
by EdwinK
robgeerts wrote:What does console (F12) say?
Looks like you got an error..
Code: Select all
jquery.min.js:4 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
send @ jquery.min.js:4
ajax @ jquery.min.js:4
(anonymous) @ main.js?v=108:16
And then a load of urls from meteogroup/buienradar
Code: Select all
debug called: MG.map.wrapper.OpenLayers.setZoom(2)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.5,51.52)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setZoom(2)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.5,51.52)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setZoom(2)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.5,51.52)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setZoom(1)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.5,51.52)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setZoom(4)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.5,51.52)
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Thu Jan 01 1970 01:00:00 GMT+0100 (CET) - Thu Jan 01 1970 01:00:00 GMT+0100 (CET), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Sat Apr 15 2017 11:00:00 GMT+0200 (CEST) - Sat Apr 15 2017 11:00:00 GMT+0200 (CEST), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug blocked playback attempt since animationInterval or loopTimeout are defined
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Thu Jan 01 1970 01:00:00 GMT+0100 (CET) - Thu Jan 01 1970 01:00:00 GMT+0100 (CET), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Sat Apr 15 2017 11:00:00 GMT+0200 (CEST) - Sat Apr 15 2017 11:00:00 GMT+0200 (CEST), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug blocked playback attempt since animationInterval or loopTimeout are defined
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Thu Jan 01 1970 01:00:00 GMT+0100 (CET) - Thu Jan 01 1970 01:00:00 GMT+0100 (CET), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug Time interval computed: Thu Apr 13 2017 20:00:00 GMT+0200 (CEST) - Thu Apr 13 2017 20:00:00 GMT+0200 (CEST), hours: 0.0002777777777777778
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug totalAnimationDurationSeconds: 0.000001, frameBuckets: 1
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug increased that.animationSpeedFactor: 13500
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug blocked playback attempt since animationInterval or loopTimeout are defined
5VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error Error while parsing JSON-feed: /fileadmin/wme/feed_widget_wind.php?poi=&lat=51.52&lon=5.5
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error error
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setZoom(4.49)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug created map wrapper: OpenLayers
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapMoved
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug called: MG.map.wrapper.OpenLayers.setCenter(5.6,53)
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 debug OpenLayers.MapLoaded
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error Error while parsing JSON-feed: /fileadmin/wme/feed_page_home.php?activeLayer=rad_nl&locale=nl_nl&date=now&context=home%2F6%2F31
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error error
VM907 MG.WebMapEngine.debug.js?v=1.0.14&1478204245:30 error
adsbygoogle.js:18 Uncaught Q {name: "TagError", message: "adsbygoogle.push() error: Page-level tag does not work inside iframes.", stack: "TagError: adsbygoogle.push() error: Page-level tag…esyndication.com/pagead/js/adsbygoogle.js:22:207)"}
Gc @ adsbygoogle.js:18
Pc @ adsbygoogle.js:22
Lf @ adsbygoogle.js:80
(anonymous) @ adsbygoogle.js:82
(anonymous) @ adsbygoogle.js:82
2utilsMobile.min.js?v=1.0.14&1478204244:2 getCurrentPosition() and watchPosition() no longer work on insecure origins. To use this feature, you should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
(anonymous) @ utilsMobile.min.js?v=1.0.14&1478204244:2
(anonymous) @ utilsMobile.min.js?v=1.0.14&1478204244:2
c @ VM863 jquery.min.js:4
fireWith @ VM863 jquery.min.js:4
ready @ VM863 jquery.min.js:4
q @ VM863 jquery.min.js:4
main.min.js?v=1.0.14&1478204244:1 morpheoInitializeMap
main.min.js?v=1.0.14&1478204244:23 Uncaught TypeError: Cannot read property 'images' of null
at Object.updateRainChartAtLocation (main.min.js?v=1.0.14&1478204244:23)
at updateChart (main.min.js?v=1.0.14&1478204244:2)
at placeMarker (main.min.js?v=1.0.14&1478204244:2)
at Morpheo.setMarker (main.min.js?v=1.0.14&1478204244:3)
at ForecastRainRadar.render ((index):648)
at Object.success ((index):543)
at c (VM863 jquery.min.js:4)
at Object.fireWith [as resolveWith] (VM863 jquery.min.js:4)
at k (VM863 jquery.min.js:6)
at XMLHttpRequest.r (VM863 jquery.min.js:6)
updateRainChartAtLocation @ main.min.js?v=1.0.14&1478204244:23
updateChart @ main.min.js?v=1.0.14&1478204244:2
placeMarker @ main.min.js?v=1.0.14&1478204244:2
Morpheo.setMarker @ main.min.js?v=1.0.14&1478204244:3
ForecastRainRadar.render @ (index):648
success @ (index):543
c @ VM863 jquery.min.js:4
fireWith @ VM863 jquery.min.js:4
k @ VM863 jquery.min.js:6
r @ VM863 jquery.min.js:6
main.min.js?v=1.0.14&1478204244:1 gl context: [object WebGLRenderingContext]
main.min.js?v=1.0.14&1478204244:1 emscipten c-code says: initGL
main.min.js?v=1.0.14&1478204244:1 emscipten c-code says: init viewport: 0 0 290 200
main.min.js?v=1.0.14&1478204244:1 emscipten c-code says: initRadar nl
main.min.js?v=1.0.14&1478204244:1 emscipten c-code says: onDownloadImagesStarted: 25
main.min.js?v=1.0.14&1478204244:1 emscipten c-code says: initModel radarCount: 25
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 11 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132035.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 11 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132035.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 12 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132040.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 12 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132040.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 13 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132045.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 13 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132045.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 14 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132050.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 14 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132050.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 15 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132055.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 15 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132055.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 16 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132100.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 16 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132100.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 17 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132105.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 17 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132105.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 18 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132110.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 18 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132110.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 19 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132115.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 19 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132115.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 20 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132120.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 20 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132120.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 21 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132125.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 21 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132125.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 22 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132130.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 22 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132130.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 23 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132135.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 23 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/vel_201704132135.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 24 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/forecast_201704132035/for_201704132140.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 0 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704131940.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 0 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704131940.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 1 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704131945.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 1 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704131945.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 2 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704131950.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 2 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704131950.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 3 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704131955.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 3 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704131955.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 4 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132000.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 4 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132000.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 5 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132005.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 5 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132005.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 6 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132010.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 6 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132010.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 7 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132015.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 7 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132015.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 8 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132020.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 8 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132020.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 9 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132025.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 9 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132025.jpg
main.min.js?v=1.0.14&1478204244:1 downloading radar image: 10 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/rad_201704132030.jpg
main.min.js?v=1.0.14&1478204244:1 downloading velocity image: 10 http://cdn.meteogroup.de/images/mapengine/rain2.0/rad_nl/observation/vel_201704132030.jpg
main.min.js?v=1.0.14&1478204244:1 download elapsed time: 5.78 s
Re: Dashticz v2.0, custom positioning and multiple screens
Posted: Thursday 13 April 2017 22:55
by robgeerts
Hmmm there should be anotber one. Right after loading the page..