search

custom-cards / dual-gauge-card

Dual gauge custom card for Lovelace in Home Assistant
MIT License
188 stars 41 forks source link

Problem with Home Assistant 0.106 #24

Closed vencakratky closed 4 years ago

vencakratky commented 4 years ago

Hello, after update 0.106 dual-gauge-card not working dual-gauge

nick2k3 commented 4 years ago

here too:

Schermata 2020-02-26 alle 22 54 46

Using version 0.5.1 on Home Assistant 0.106.0 .

GitHubxtsnl commented 4 years ago

same problem here. Cannot assign to read only property 'min' of object '#<Object>'

rhoppel commented 4 years ago

image

I also get problems on all of my dual gauge instances. with 106.0

coltonrb commented 4 years ago

JS console confirms that line 22, where it attempts to assign a value to this.config.min, is the problem. Possibly related to this frontend change? Not quite sure - maybe someone with a bit more experience can chime in.

tomlevels commented 4 years ago

This is due to changes in version 0.106, also see https://github.com/custom-cards/dual-gauge-card/issues/22

ghost commented 4 years ago

Is there a solution for that problem or you we only "know" what the problem is?

fudu commented 4 years ago

I get same error and another...: Cannot assign to read only property '0' of object '[object Array]' Cattura

cerebrate commented 4 years ago

Until there's an official fix out, per #22, you can replace line 19 of dual-gauge-card.js with

this.config = JSON.parse(JSON.stringify(config));

as a workaround.

vencakratky commented 4 years ago

Until there's an official fix out, per #22, you can replace line 19 of dual-gauge-card.js with

config = JSON.parse(JSON.stringify(config));

as a workaround.

For me not working

cerebrate commented 4 years ago

ETA: oops, my bad. See my fixed version above.

You may also have to delete the dual-gauge-card.js.gz file to be sure your modification loads.

rhoppel commented 4 years ago

Until there's an official fix out, per #22, you can replace line 19 of dual-gauge-card.js with

this.config = JSON.parse(JSON.stringify(config));

as a workaround.

This works!!! Be sure to delete "dual-gauge-card.js.gz ".

vencakratky commented 4 years ago

So, i tried this: 1.) edit /config/www/dual-gauge-card.js: configdual 2.) Download this edited file 3.) Via "File Editor" in HA delete dual-gauge-card.js 4.) Reload Core (in File Editor) 5.) Upload again edited file dual-guage-card.js to /config/www/dual-gauge-card.js 6.) Again Reload Core or Restart HA

Now dual-gauge-card are back ! :-) Please try somebody else this procedure. After i close this issue

ghost commented 4 years ago

No chance here, sorry! Tested it with HACS and manual installation (www and www/community folder)

There is no difference between before!

owenostrander commented 4 years ago

So, i tried this: 1.) edit /config/www/dual-gauge-card.js: configdual 2.) Download this edited file 3.) Via "File Editor" in HA delete dual-gauge-card.js 4.) Reload Core (in File Editor) 5.) Upload again edited file dual-guage-card.js to /config/www/dual-gauge-card.js 6.) Again Reload Core or Restart HA

Now dual-gauge-card are back ! :-) Please try somebody else this procedure. After i close this issue

Your procedure worked for me, I have my card back! Thank-you.

vencakratky commented 4 years ago

There was still a problem with Home Assistant APP under iOS. You have to "Reset frontend cache" in Application setting and restart HA app

hoburgt commented 4 years ago

I updated yesterday evening and got the same error afterwards. This fix did the trick so thanks very much!!

McGiverGim commented 4 years ago

I tested the fix:

  1. It works
  2. If I write by mistake an entity name bad, the complete TAB does not load (not only the card). I don't know if this only happens to me or if this problem was there before.
  3. The Android app had the same problem, I needed to erase all the data from the app to make it work (I have not seen the "Reset frontend cache" option in Android).
ner0tic commented 4 years ago

Upgraded to 0.106.1 last night from 1.105.x (i forget which, but the more recent) and also encounter this issue. This fix did not work for me. I removed thegz file, cleared my cache, tried a "fresh" browser.

ner0tic commented 4 years ago

Upgraded to 0.106.1 last night from 1.105.x (i forget which, but the more recent) and also encounter this issue. This fix did not work for me. I removed thegz file, cleared my cache, tried a "fresh" browser.

After some tinkering... I changed the this.config = JSON.parse(JSON.stringify(config)); to config = JSON.parse(JSON.stringify(config)); and it worked.

Lymkin commented 4 years ago

config = JSON.parse(JSON.stringify(config));

Worked for me.

vencakratky commented 4 years ago

If i try" config = JSON.parse(JSON.stringify(config));" , become error config error

PonyOny commented 4 years ago

On latest version if you set the top line as mentioned above this.config = JSON.parse(JSON.stringify(config)); you will have to also remove this line as it's setting it again with the parameter and the new line you added would get overridden. image

eugr commented 4 years ago

BTW, if you have ssh access to HA, no need to delete the js.gz file. Just change to that directory and run gzip -k dual-gauge-card.js

Don't forget -k modifier otherwise it will delete the js file after compressing it into gz

lebherz commented 4 years ago

Will somebody push the fix to github? so that we all get a new version? thx!

fmonday commented 4 years ago

That fix works, thanks all!

lebherz commented 4 years ago

... now wait for merging..........................................................................

lebherz commented 4 years ago

Sorry @Rocka84 to contact you in office. We all try to get in contact with you :) and it was not transparent, that this Plugin was a private thing. I apologize!

best regards rené

Rocka84 commented 4 years ago

Hi! This issue was fixed with #29, thanks again @lebherz @lebherz again: Apology accepted and sorry if I my answer was a bit harsh. After all you were right, I really should have taken more care of this project.