Domoticz

Lokonli wrote: Sunday 20 October 2019 11:05 If you have created the all day event in the GMT timezone, and you use the calendar in the Amsterdam timezone then all day events will start at 2am, which is correct.

Can you check the timezone of your all day events?
Do the other events have the correct start time?

Stepdes wrote: Sunday 20 October 2019 11:53

Lokonli wrote: Sunday 20 October 2019 11:05 If you have created the all day event in the GMT timezone, and you use the calendar in the Amsterdam timezone then all day events will start at 2am, which is correct.

Can you check the timezone of your all day events?
Do the other events have the correct start time?

Ok, now i understand.
Well all of my systems are now on Brussels timezone and i made a few new all day events, now i have 1am as start hour, so it has definitely something to do with the correct timezone.(winter/summer time?) All my other events are shown at the correct start time

Thnx for your help!

adjustTZ
adjustAllDayTZ

I was able to reproduce some of the issues when I change the timezone of the Dashticz server. However, I cannot explain everything I see. Also in your case I don't understand how the all day events have an incorrect start time, while your normal events have the correct start time. The timezone interpretation happens on several places, and is pretty difficult to follow.

As a work around, I will add two parameters to calendar block definition:

Code: Select all

adjustTZ
adjustAllDayTZ

These can be used to adjust the time zone, by defining an offset in hours. If needed (like in your case) you can use the second parameter to adjust the AllDay events only.

Lokonli wrote: Wednesday 16 October 2019 16:52

magicduck wrote: Wednesday 16 October 2019 10:42 Hi !
Seems there is an issue with sonarr and images.

Is this the result of a Dashticz version update?

Do you use the beta or master branch? If beta: Could you test master as well?
On which version it was still working?

(I've never used Sonarr...)

magicduck wrote: Monday 21 October 2019 21:46

Lokonli wrote: Wednesday 16 October 2019 16:52

magicduck wrote: Wednesday 16 October 2019 10:42 Hi !
Seems there is an issue with sonarr and images.

Is this the result of a Dashticz version update?

Seems so... But I didn't noticed that until recently... I was thinking it was "cors" problems (well I fucked the php so it was not working).

Do you use the beta or master branch? If beta: Could you test master as well?
On which version it was still working?

(I've never used Sonarr...)

I use the beta branch, but my try on the master branch give the same results.

So this is somewhere and my knowledge of javascript is a bit limited ... :/

Stepdes wrote: Monday 21 October 2019 9:24

I was able to reproduce some of the issues when I change the timezone of the Dashticz server. However, I cannot explain everything I see. Also in your case I don't understand how the all day events have an incorrect start time, while your normal events have the correct start time. The timezone interpretation happens on several places, and is pretty difficult to follow.

As a work around, I will add two parameters to calendar block definition:

Code: Select all

adjustTZ
adjustAllDayTZ

These can be used to adjust the time zone, by defining an offset in hours. If needed (like in your case) you can use the second parameter to adjust the AllDay events only.

Hi Lokonli, thanks for your efforts already.
This calendar is a shared one and all events are allday events, now i see that depending the person who ads a allday event, the start hour is changing, thats because of the timezone settings of the creator of the event. So the offset parameter will not work for every event. Is it possible to add a parameter to the block definition that avoid showing the start hour? So only date and event like 29/10 - this is an event ?
Regards,
Stephan

Lokonli wrote: Monday 21 October 2019 23:25

ok, I'll add that parameter as well. (fixAllDay)

Stepdes wrote: Tuesday 22 October 2019 0:04

Lokonli wrote: Monday 21 October 2019 23:25

ok, I'll add that parameter as well. (fixAllDay)

Great thnx!

Lokonli wrote: Wednesday 23 October 2019 21:21
Could you test the calendar layout changes in the latest beta? Preferably for calFormat:0 as well as calFormat:1

freakshock wrote: Tuesday 24 April 2018 21:22 Not sure if this is a Dashticz bug, but I hope someone can help with this.
I use the buienradar image with a buienalarm url, to show a graph of the coming rain.
Lately however this is not working anymore. When the url is opened independently of dashticz (not within a frame) it works.
For instance this url:
http://www.buienalarm.nl/widget/graphic ... lor=4395c7

This is my code in config.js:

Code: Select all

var buttons = {}
buttons.buienradar = {width:12, isimage:true, refreshimage:60000, image: 'http://api.buienradar.nl/image/1.0/RadarMapNL?w=285&h=256', url: 'http://www.buienalarm.nl/widget/graphic?lat=51.692134&lon=5.290004&title=Den%20Bosch&color=4395c7'}

When clicking the buienradar image it just shows an empty frame. Anyone?

http://192.168.0.61/cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=admin&pwd=password

var buttons = {}
buttons.webcam = {
  image:"//192.168.0.61/cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=admin&pwd=password",
  url:"//192.168.0.61/cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=admin&pwd=password",
  isimage:true,
  width: 12,
  refresh: 2000
}

HansieNL wrote: Tuesday 26 November 2019 13:12 @ben53252642 : Some pages will not load in a frame because the publisher of the webpage doesn't allow that. The only thing you can try is to load that page in an own webpage and link to that page.

HansieNL wrote: Tuesday 26 November 2019 13:12 @ben53252642 : Some pages will not load in a frame because the publisher of the webpage doesn't allow that. The only thing you can try is to load that page in an own webpage and link to that page.

buttons.buienradar = {
        width:12, refreshimage:1000*60*15,
        btnimage: 'http://api.buienradar.nl/image/1.0/RadarMapNL?w=360&h=300',
        url:'https://www.buienalarm.nl/venlo-limburg-nederland/51.36234,6.18802',
    }