Uncaught TypeError: Cannot convert undefined or null to object about pvpc-hourly-pricing-card

[McGiverGim]

It seems that for some reason the card was not updated to version 0.3 and I was using a cached version. A reboot was not enough. I deleted it and added it again and now is working and it seems that the error is gone. Good work!!

I close this issue. If I see the error again I will reopen it.

[danimart1991]

Could you give me more info? still happens in the new version (0.0.3)?

[McGiverGim]

Yes, it happens with latest version too. Each time I go to the tab with the pvpc card produces this message.
I can see it in the developers tab, registry. But there is no more info on the log.
I will recheck my files to see if I have something wrong...

[danimart1991]

What browser and browser version did you use?

[McGiverGim]

I have tested it from the Android app, I don't know if it happens too from the computer with a browser. I will try to check it later.

[McGiverGim]

I reopen the issue, it has happened again, but in a different line, according to the error:

Logger: frontend.js.latest.202004072
Source: components/system_log/__init__.py:209
First occurred: 25 de abril de 2020 16:55:45 (1 occurrences)
Last logged: 25 de abril de 2020 16:55:45

https://myhost.duckdns.org/hacsfiles/pvpc-hourly-pricing-card/pvpc-hourly-pricing-card.js:1:27 Uncaught TypeError: Cannot convert undefined or null to object

[danimart1991]

I think that you are using an old version of the card or an old version of the card is in the browser cache. Are you using card versioning to fix this issue?

https://www.danielmartingonzalez.com/installing-lovelace-plugins/#versions

[McGiverGim]

No, I don't use versioning because I used the HACS installer that adds it automatically.

I will add it manually and monitor it to see if the error happens again. Is probably that you have reason. The error is different that the one from the beginning (point to different line in the code) but I'm not a python developer.

[McGiverGim]

I think is better to close (again) this issue. I have not seen the error again. Sorry for making lost your time with this ;)