Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working after 0.88.0 upgrade #27

Closed
ltjessem opened this issue Feb 21, 2019 · 9 comments
Closed

Not working after 0.88.0 upgrade #27

ltjessem opened this issue Feb 21, 2019 · 9 comments
Labels
bug Something isn't working

Comments

@ltjessem
Copy link

2019-02-21 08:29:59 ERROR (MainThread) [frontend.js.latest.201902200] http://192.168.1.135:8123/local/simple-thermostat/simple-thermostat.js?v=1:5:10 Uncaught TypeError: Cannot convert undefined or null to object

@nervetattoo
Copy link
Owner

I know there is an issue with HA replacing a certain button component that the card relied on. I've yet to upgrade myself so I can't fully say if this is the only breaking thing. (zwave stack takes so long to initiate that I try to time upgrades for when I don't need to interact with anything for a long time 😸 )

I have a fix for this in the works that I'll publish very very soon, hope you can verify back after that if it works?

@ltjessem
Copy link
Author

Will do!

@nervetattoo nervetattoo added the bug Something isn't working label Feb 21, 2019
@nervetattoo
Copy link
Owner

@ltjessem
Copy link
Author

Still seeing the same error unfortunately

@nervetattoo
Copy link
Owner

Alright, I'll get back to this once I've upgraded myself :)

@JumpMaster
Copy link

0.18.0 has fixed the issues for me. It's working well again.

@ltjessem
Copy link
Author

My bad, I finally got it working again. Only way I could get it working again was to remove the .js, restart, then add the .js again. Odd, but solved.

@nervetattoo
Copy link
Owner

Good, I was unable to reproduce with 0.18 as well. Closing this.
You probably got a cached version in your browser though @ltjessem, did you bump the number in v=1 in the resources section when you initially attempted to upgrade?

@ltjessem
Copy link
Author

I didn't touch the version number, but it was definitely a caching issue. Thanks for resolving this so quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants