No, stopped again to work since this morning.
In the console i get:
Do you use a proxy server to access the Internet? If so, it may be doing its own caching. In that case doing both a clear cache and force reload (in Chrome thereās an option to do these together if you hold down on the reload button with developer tools open) may help.
Otherwise I donāt know why this is still happening for you as it is loading fine from here in all browsers (Chrome, Firefox, and Safari).
Still broken for me also.
Access to script at 'https://unpkg.com/[email protected]/src/lib/units/hour?module' from origin 'https://xcxxc
duckdns.org:8123' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header has a value 'http://hassio.local:8123' that is not equal to the supplied origin.
units.js:5 GET https://unpkg.com/[email protected]/src/lib/units/hour?module net::ERR_FAILED
2default_view:1 Uncaught (in promise) TypeError: Failed to fetch dynamically imported module: https://unpkg.com/[email protected]/src/moment.js?module
Promise.then (async)
loadModules @ lovelace-home-feed-card.js:25
HomeFeedCard @ lovelace-home-feed-card.js:20
fa @ create-card-element.ts:71
ya @ create-card-element.ts:98
value @ hui-view.ts:60
value @ hui-view.ts:334
t.addEventListener.once @ hui-view.ts:68
r @ fire_event.ts:76
(anonymous) @ create-card-element.ts:111
Promise.then (async)
ya @ create-card-element.ts:109
value @ hui-view.ts:60
(anonymous) @ hui-view.ts:286
value @ hui-view.ts:285
value @ hui-view.ts:214
performUpdate @ updating-element.js:526
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
initialize @ updating-element.js:268
initialize @ lit-element.js:95
O @ updating-element.js:98
V @ lit-element.js:46
r @ hui-view.ts:50
value @ hui-root.ts:652
(anonymous) @ hui-root.ts:492
setTimeout (async)
(anonymous) @ render-status.ts:2
(anonymous) @ web-animations-next-lite.min.js:15
requestAnimationFrame (async)
window.requestAnimationFrame @ web-animations-next-lite.min.js:15
r @ render-status.ts:2
value @ hui-root.ts:492
performUpdate @ updating-element.js:526
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
initialize @ updating-element.js:268
initialize @ lit-element.js:95
O @ updating-element.js:98
V @ lit-element.js:46
r @ hui-root.ts:66
_clone @ template-instance.js:84
__commitTemplateResult @ parts.js:244
commit @ parts.js:186
s @ render.js:44
V.render @ shady-render.js:251
update @ lit-element.js:166
performUpdate @ updating-element.js:508
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
set @ updating-element.js:166
value @ ha-panel-lovelace.ts:179
value @ ha-panel-lovelace.ts:143
performUpdate @ updating-element.js:524
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
initialize @ updating-element.js:268
initialize @ lit-element.js:95
O @ updating-element.js:98
V @ lit-element.js:46
o @ ha-panel-lovelace.ts:55
value @ hass-router-page.ts:271
value @ hass-router-page.ts:291
_currentLoadProm.c.then._currentLoadProm @ hass-router-page.ts:197
Promise.then (async)
value @ hass-router-page.ts:188
performUpdate @ updating-element.js:508
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
set @ updating-element.js:166
value @ hass-router-page.ts:259
async function (async)
value @ hass-router-page.ts:256
value @ partial-panel-resolver.ts:115
value @ partial-panel-resolver.ts:82
performUpdate @ updating-element.js:526
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
initialize @ updating-element.js:268
O @ updating-element.js:98
n @ hass-router-page.ts:49
n @ partial-panel-resolver.ts:65
_clone @ template-instance.js:84
__commitTemplateResult @ parts.js:244
commit @ parts.js:186
s @ render.js:44
V.render @ shady-render.js:251
update @ lit-element.js:166
performUpdate @ updating-element.js:508
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
initialize @ updating-element.js:268
initialize @ lit-element.js:95
O @ updating-element.js:98
V @ lit-element.js:46
r @ home-assistant-main.ts:36
_clone @ template-instance.js:84
__commitTemplateResult @ parts.js:244
commit @ parts.js:186
update @ template-instance.js:40
__commitTemplateResult @ parts.js:236
commit @ parts.js:186
s @ render.js:44
V.render @ shady-render.js:251
update @ lit-element.js:166
performUpdate @ updating-element.js:508
_enqueueUpdate @ updating-element.js:460
async function (async)
_enqueueUpdate @ updating-element.js:446
_requestUpdate @ updating-element.js:413
set @ updating-element.js:166
value @ hass-base-mixin.ts:49
(anonymous) @ connection-mixin.ts:137
n @ haws.es.js:1
(anonymous) @ haws.es.js:1
Promise.then (async)
c @ haws.es.js:1
u @ haws.es.js:1
subscribe @ haws.es.js:1
S @ haws.es.js:1
(anonymous) @ core.ts:77
Promise.then (async)
166 @ core.ts:71
o @ bootstrap:63
(anonymous) @ bootstrap:198
(anonymous) @ bootstrap:198
2lovelace-home-feed-card.js:39 Loaded custom-card-helpers module.
No proxy server here.
No, i donāt use any proxy serverā¦
I still get no card and more, trying to update to the latest via HACS it seems not working the process of updatingā¦ The files inside /local/www) are updated, but the UI HACS shows always the old release also after clicking on updateā¦
I had a similar issue with the update to 0.3.0 (non-beta). Iāve pushed 0.3.1 now, but it isnāt actually any different to 0.3.0. Try select 0.3.0b3 from the dropdown and clicking Reinstall or Upgrade and then try the upddate to 0.3.1 again.
Iām trying to find out why you may still be having issues with the CORS errors despite the cache being cleared.
Just updated to the .3.1 and still have the CORS errors on chrome.
I donāt have 0.3.0b3 maybe because iāve not set beta on options of hacsā¦
But solved uninstalling and installing againā¦ now i have 0.3.1 with the same problem as before releaseā¦
I have just released version 0.3.2. This makes the module imports local, rather than coming from unpkg.com, so should eliminate the CORS errors.
2 Likes
Thanks, finally all is working again!
Thanks. Mine is working also.
Hi, your card is great! thank you for sharing with you all. I have a problem when I use home feed card. I currently have a card with time and date (clock-card). The date is written in French (I am French). But when I add home feed card, the date is put in English. Someone would have an idea of the problem?
Thanks for your help
good work.
This looks like some sort of conflict with that particular card. I have temporarily changed my browser language to French and other built-in cards still seem to show the language as French even when they are on the same page as the home feed card.
Do you have a link to the card you are using so I can see where the issue lies? I canāt find it on HACS, and searching for clock-card is bringing back multiple results so I want to test with the right one.
okay thank you for your help, I use the tyrsen card (here: Palm Springs Theme) .I followed his instructions by creating a clock-card.js file and pasting his code. And create a file moment.js by translating the months written in English (january, february ā¦) by French (janvier, fĆ©vrier ā¦). It did not cause me any problem elsewhere. But I did not find another card that could show me the time and date with a logo as simple and beautiful.
thanks! (sorry for my basic english ā¦)
I forgot to mention that the date goes into English after several seconds to 1 minute
I think I have tracked down what is happening. My card also uses the Moment module and the way it imports it causes it to conflict with the moment.js you created. The version I import already has all the translations, but it wasnāt setting the locale based on the browser lanuage and so the translations werenāt working. I have just pushed a new release, 0.3.3 that should fix that. Can you update to this and see if it fixes the problem for you.
1 Like
After updating it works! thatās great ! thank you for your speed and your help
Hi!
How can I view the reverse order of feeds.
I have 10 items, but I would like to display only one, the last one.
Thanks.
Can you give me a bit more detail on exactly how you want the items to show? The current sort is by absolute time difference (ignoring the sign, positive or negative) between the entity time (state of timestamp sensors, modified time for other entities) and the current time. This means that items at the top of the list have a time nearest to the current time (past or future) and as you go further down the list the items are further into the past or future, which sounds like what you are looking for.
I could implement some alternative sort orders, are any of these what you are looking for?
- Time difference sort in descending order - same as current sort, but those items further into the past or future would be at the top
- Simple time sort in descending order - this would sort by the time value in descending order
- SImple time sort in ascending order - this would sort by the time value in descending order
Both the simple time sort options would cause issues if you have sensors which return timestamps a long way into the past or future, which could result in them sticking to the top or bottom of the feed.
Thanks for the reply. I think itās this:
Iām using this card for a feed that has a reverse order.
This is the link wikiquote
I wish I could view the entities by time in descending order.
In this way, if I put max_items: 1 will I only see the last one ?
Thanks again :0)