Re: IMPORTANT REQUEST!!!
Posted: Thursday 25 October 2018 12:01
Grrrr can't get access-control-allow-origin header working with nginx. Anyone who can help me with that one? 
The fontawesome update some time ago results in different names for the icons to be used.poudenes wrote: Thursday 25 October 2018 9:41See my post 2 up... For me it work now. Only the custom icons part is gone now. But rest is workinggielie wrote: Thursday 25 October 2018 9:40Nope, i cant get it to work.robgeerts wrote: Wednesday 24 October 2018 21:15 Wow had to read back a lot and good to see that most off you already have it working again!!
I started from scratch, installed dashticz in var/www/html (instead of domoticz/www) with all the necessary dependencies.
I also tried to host the files on my synology and redirected to that address but still no luck.
Can someone make a clear tutorial how to change this.
And one question, if i change the icall/garbage file wont this be a problem with the next git pull update?
I will check it. As far as I could see this morning some where same. But will look again. Thanks!Lokonli wrote:The fontawesome update some time ago results in different names for the icons to be used.poudenes wrote: Thursday 25 October 2018 9:41See my post 2 up... For me it work now. Only the custom icons part is gone now. But rest is workinggielie wrote: Thursday 25 October 2018 9:40 Nope, i cant get it to work.
I started from scratch, installed dashticz in var/www/html (instead of domoticz/www) with all the necessary dependencies.
I also tried to host the files on my synology and redirected to that address but still no luck.
Can someone make a clear tutorial how to change this.
And one question, if i change the icall/garbage file wont this be a problem with the next git pull update?
The new name for fa-window-close is:
'far fa-window-close' for a regular icon.
or
'fas fa-window-close' for a solid icon.
On fontawesome.com you can find the correct names. Sometimes only fas or far is supported (not both). Sometimes there is a small change in the name as well.
Same here. Man I need to learn a lot...edge wrote:Grrrr can't get access-control-allow-origin header working with nginx. Anyone who can help me with that one?
That is only the apache/server part and i'm sure this is working fine because i run other web applications using apache.poudenes wrote: Thursday 25 October 2018 9:41See my post 2 up... For me it work now. Only the custom icons part is gone now. But rest is workinggielie wrote: Thursday 25 October 2018 9:40Nope, i cant get it to work.robgeerts wrote: Wednesday 24 October 2018 21:15 Wow had to read back a lot and good to see that most off you already have it working again!!
I started from scratch, installed dashticz in var/www/html (instead of domoticz/www) with all the necessary dependencies.
I also tried to host the files on my synology and redirected to that address but still no luck.
Can someone make a clear tutorial how to change this.
And one question, if i change the icall/garbage file wont this be a problem with the next git pull update?
Ok, I reverted the calendar.js and changed: config['calendar_parse_localy']=true; --> config['calendar_parse_localy']=1;Lokonli wrote: Wednesday 24 October 2018 22:14The CONFIG.js setting should be:stuffer wrote: Wednesday 24 October 2018 21:41@robgeertsrobgeerts wrote: Wednesday 24 October 2018 21:15 Wow had to read back a lot and good to see that most off you already have it working again!!
Almost
First I want to thank you for the project. A crate of beer is on his way when I get this working(or at the Jumbo 1,5 for the price for one )
What I did on my Ubuntu 16 machine for domoticz:
apt install apache2
apt-get install python-software-properties
add-apt-repository ppa:ondrej/php
apt-get update
apt-get install php7.2
apt-get install php7.2-curl
service apache2 restart
nano /home/pi/domoticz/www/dashboard/js/calendar.js
//\\changed://\\
if (settings['calendar_parse_localy']){
curUrl = './vendor/dashticz/ical/?time=' + cache + '&url=' + curUrl;
} else {
curUrl = 'https://dashticz.nl/ical/?time=' + cache + '&url=' + curUrl;
}
//\\to//\\
change curUrl = 'https://MYOWNDOMOTICZIP/ical/?time=' + cache + '&url=' + curUrl;
and add this in my CONFIG.js
config['calendar_parse_localy']=true;
With the result that the dutch tv section is working again. Only my 2 iCals are still not responding. (Google and RMN https://inzamelschema.rmn.nl/ical/0356200000014977)
What is the best way to look at this?
config['calendar_parse_localy']=1;
The change you made in calendar.js is not needed (and incorrect) so better to revert that one.
For the debugging: press F12 in Chrome, and look for errors in the console.stuffer wrote: Thursday 25 October 2018 21:06 Ok, I reverted the calendar.js and changed: config['calendar_parse_localy']=true; --> config['calendar_parse_localy']=1;
Still no luck. Where i can start to debug this? It feels that i am pretty close but I don't no where to start searching.
(and I hope to create an how to for other users)
I didn't change anything inside the Dashticz code. Only addgielie wrote: Thursday 25 October 2018 14:56That is only the apache/server part and i'm sure this is working fine because i run other web applications using apache.poudenes wrote: Thursday 25 October 2018 9:41See my post 2 up... For me it work now. Only the custom icons part is gone now. But rest is workinggielie wrote: Thursday 25 October 2018 9:40
Nope, i cant get it to work.
I started from scratch, installed dashticz in var/www/html (instead of domoticz/www) with all the necessary dependencies.
I also tried to host the files on my synology and redirected to that address but still no luck.
Can someone make a clear tutorial how to change this.
And one question, if i change the icall/garbage file wont this be a problem with the next git pull update?
im sure It is the dashticz part that need a change which i cant get right.
Code: Select all
config['calendar_parse_localy']=true; And that doesn’t make sense because it should be 1 or 0 instead of false/true.poudenes wrote: Friday 26 October 2018 8:14I didn't change anything inside the Dashticz code. Only addgielie wrote: Thursday 25 October 2018 14:56That is only the apache/server part and i'm sure this is working fine because i run other web applications using apache.poudenes wrote: Thursday 25 October 2018 9:41
See my post 2 up... For me it work now. Only the custom icons part is gone now. But rest is working
im sure It is the dashticz part that need a change which i cant get right.
to CONFIG.jsCode: Select all
config['calendar_parse_localy']=true;
Yes, I experience the same. It would be nice if the weather part did not have to reload every time. How much does weather change in forecast? Not too much.poudenes wrote:Only problem i still have is the Weather icons. Load very very slow in latest Dasthicz version.
Same problem, very very slow, not workablepoudenes wrote: Friday 26 October 2018 11:09 Only problem i still have is the Weather icons. Load very very slow in latest Dasthicz version.
I cannot reproduce the problem. Which weather provider are you using? WU or OWM? In case of WU, try with OWM. WU is using cors-anywhere.herokuapp.com, which might introduce some delay.
Code: Select all
config['owm_api'] = 'your OpenWeatherMap key';
config['owm_city'] = 'Mainaschaff';
config['owm_name'] = '';
config['owm_country'] = 'de';
This makes sense. When the icons won't load and I have the browser in debugging mode, I see the following error:Lokonli wrote: Friday 26 October 2018 19:42 I cannot reproduce the problem. Which weather provider are you using? WU or OWM? In case of WU, try with OWM. WU is using cors-anywhere.herokuapp.com, which might introduce some delay.
You cannot use WU and OWM simultaneously.
In CONFIG.js add:then replace in your block 'weather' with 'weather_owm' and 'currentweather_big' with ' currentweather_big_owm'Code: Select all
config['owm_api'] = 'your OpenWeatherMap key'; config['owm_city'] = 'Mainaschaff'; config['owm_name'] = ''; config['owm_country'] = 'de';
Code: Select all
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource
at https://cors-anywhere.herokuapp.com/https://api.wunderground.com/api/1xxxxxxxxxxxxxxxxxd/forecast10day/q/NL/Dxxxxxxx.json.
(Reason: CORS header ‘Access-Control-Allow-Origin’ missing).[Learn More]Thanks for fixing. I was happy to see the dates with their respective colors back. However, when I looked at the type of garbage being picked up next (Restafval: maandag), I realized that it is not correct. This was last Monday and not next Monday. Next Monday it will be GFT instead. Number 2 and 3 on my list (I limited it to 3) are correct for next week Thursday, (Papier and Plastic).Lokonli wrote: Thursday 25 October 2018 8:07 HVC is part of 'afvalstromen'. For afvalstromen all code already is implemented, except for HVC. I'll make the fix this weekend.
EastXIII wrote: Thursday 25 October 2018 12:30Same here. Man I need to learn a lot...edge wrote:Grrrr can't get access-control-allow-origin header working with nginx. Anyone who can help me with that one?
Thanks for updating the wiki! I've added a few garbage companies that are supported as well already.jake wrote: Friday 26 October 2018 22:03Thanks for fixing. I was happy to see the dates with their respective colors back. However, when I looked at the type of garbage being picked up next (Restafval: maandag), I realized that it is not correct. This was last Monday and not next Monday. Next Monday it will be GFT instead. Number 2 and 3 on my list (I limited it to 3) are correct for next week Thursday, (Papier and Plastic).Lokonli wrote: Thursday 25 October 2018 8:07 HVC is part of 'afvalstromen'. For afvalstromen all code already is implemented, except for HVC. I'll make the fix this weekend.
I updated the Dashticz wiki page with the new situation for the Module - Garbage collector. Please check my changes. I also put some comments in the Module - Calendar. I wonder if we still yes/no need the config.js parameter: config['calendar_parse_localy']=true;
Please also check / modify / add that section as well.