JoshDinsdale wrote: ↑Thursday 01 November 2018 17:20
Is there anyway to get dashticz to create a debug or log or something? I have some odd issues but dont know how to get any useful debug information...
In Chrome you can press F12. You then see the developer window, in which you can see errors, monitor network traffic, etc.
If you want to see the errors from your web server, then you can find log files in /var/log/apache2/ if you are using Apache on Linux.
My beatiful dashboard also ran into issues regarding the calendars...
And they worked so wel...
As a Linux Noob I have read this thread a couple of times and made the adjustments that were suggested.
Unfortunately I cannot get it to work. If I try to debug it this is what I get:
The first error seems to be a bit odd - I have PHP 70 running... What does the 501 Error mean?
I hope that I did not something stupid but sometimes the replies to this thread are contradictionairy so it's hard to find the truth.
But it is out there!
tred wrote: ↑Friday 09 November 2018 17:23
Hi guys,
My beatiful dashboard also ran into issues regarding the calendars...
And they worked so wel...
As a Linux Noob I have read this thread a couple of times and made the adjustments that were suggested.
Unfortunately I cannot get it to work. If I try to debug it this is what I get:
The first error seems to be a bit odd - I have PHP 70 running... What does the 501 Error mean?
I hope that I did not something stupid but sometimes the replies to this thread are contradictionairy so it's hard to find the truth.
But it is out there!
Thanks for al your efforts helping people out
Theo.
The first error shows that php is not running. Are the IP and port address correct? Is 192.168.1.222:8099 your Domoticz server or your web server with PHP support?
The other three lines show a reference to dashticz.nl, which will not work, because dashticz.nl is down, and is not used anymore in the latest beta. Did you enter this somewhere manually in your CONFIG.js? You can remove the herokuapp part and the dashticz.nl part.
1) (my preference)
Create a fresh install of dashticz in /var/www/html (assuming you run Apache on 192.168.1.222:82). I assume it will be /var/www/html/dashticz_v2.
Copy your current CONFIG.js to /var/www/html/dashticz_v2/custom
Then open dashticz via 192.168.1.222:82/dashticz_v2/
2)
First try 1)
Probably it's better to first try the most recent beta, without changing calendar.js
There is just 1 of the 4 calendars failing now. Three of them are webcalls and the one that does not work is a http:\\ call? Could that be the cause?
It's the soccer calendar of my son
tred wrote: ↑Saturday 10 November 2018 10:58
Really appreciate your quick and helpful replies!
There is just 1 of the 4 calendars failing now. Three of them are webcalls and the one that does not work is a http:\\ call? Could that be the cause?
It's the soccer calendar of my son
I have tried to replace https:\\ with http:\\ and also tried "webcal://" instead of https...
Can't seem to find the issue, hope you now what this is?
Thanks again...
The sportlink calendar requires you to login first. Then a token is stored, and the calendar can be retrieved via this token. The token in the link you provided expired already, and as a result the loading of the calendar gives an error.
It's not so easy to solve this. I'll give it a try ...
Is there a workaround you know of?
Like manually exporting the calendar entries and them import them via Google calendar?
If it's complex and I am the only one with this request.... just let it be...
Is there a workaround you know of?
Like manually exporting the calendar entries and them import them via Google calendar?
If it's complex and I am the only one with this request.... just let it be...
That's a good idea.
If you can save the ical file manually to for instance /home/pi/ical.ics then you can load the file in dashticz via:
Forbidden
You don't have permission to access /dashticz_v2/index.html on this server.
Apache/2.4.25 (Raspbian) Server at 192.168.0.115 Port 80
Probably a permission issue indeed. I've a slightly different setup, and I'm not an expert, but probably you have to add read permission to all users for the dashticz related files, and execute permission for the folders .
Lokonli wrote: ↑Thursday 06 December 2018 20:25
Probably a permission issue indeed. I've a slightly different setup, and I'm not an expert, but probably you have to add read permission to all users for the dashticz related files, and execute permission for the folders .