@Mariusthvdb what is that you are showing there?
its a more-info on one of the GitHub sensors
automatically listed using:
- type: custom:auto-entities
card:
type: entities
style: |
ha-card {
box-shadow: none;
margin: 0px 0px 0px -36px;
}
filter:
include:
- group: group.github_repos_in_use
options: &github_options
tap_action:
action: more-info
hold_action:
action: navigate #url
navigation_path: /ui-settings/weblinks
# url_path: >
# {{state_attr(config.entity,'latest_release_url')}}
type: custom:template-entity-row
style: |
:host {
--paper-item-icon-color:
{% set id = config.entity.split('.')[1] %}
{% set repo = 'input_boolean.' + id %}
{{'gold' if is_state(repo,'on') else 'green'}}
;
state: >
{% if states(config.entity) is not none %}
{% if state_attr(config.entity,'latest_release_tag') %}
{{state_attr(config.entity,'latest_release_tag')}}
{% else %} {{states(config.entity)}}
{% endif %}
{% else %} Unknown
{% endif %}
secondary: >
{% if states(config.entity) == 'unavailable' %} Unavailable
{% elif states(config.entity) is not none %}
{{state_attr(config.entity,'latest_commit_message')}}
{% else %} Unknown
{% endif %}
sort:
method: name
2 Likes
Flood sensor and smoke sensor dont show when they trigger
Just wanted to express my thanks to the developers of the ZWaveJS integration. Have just moved over from open zwave and it was soo pain free. I think ill enjoy zwave again!
4 Likes
Could someone please tell me how to downgrade HA Core from 2021.2 to 2021.1.5? I’m on a nuc, debian 10, supervised.
I need to do this until I find out what went wrong with my old zwave.
Is it safe to assume now, after all these releases, that the Mikrotik device-tracker integration will not evolve back into what it could support? - Namely, multiple independent hubs, rather than depending on less useful (in some cases) CAPS?
I’ve been waiting for a year now, and even though there were some discussions around it, I see nothing migrated into the main branch.
I like that you’re working on a vision, but it was working well until it was “fixed”. Now, it’s not even being discussed I guess…
Any ideas, roadmap etc???
After going to 2021.2 my Ikea tradfri integration is gone too! How can I downgrade to 2021.1.5 on supervised, Debian 10? Please?
Finally!!! THANK YOU JS!!! my trouble are over! I love you all!!!
I guess it’s just me. Everyone else seems ecstatic about 2012.2. I, however, have to sleep on the couch and hope my wife doesn’t kill me and go back a stupid-house
I am running into an issue on Home Assistant Blue where I get the following errors after the upgrade:
Error during connection setup: (sqlite3.DatabaseError) database disk image is malformed [SQL: CREATE INDEX ix_states_old_state_id ON states (old_state_id)] (Background on this error at: http://sqlalche.me/e/13/4xp6) (retrying in 3 seconds)
5:54:06 PM – recorder (ERROR) - message first occurred at 5:53:30 PM and shows up 10 times
Error executing query: (sqlite3.DatabaseError) database disk image is malformed [SQL: CREATE INDEX ix_states_old_state_id ON states (old_state_id)] (Background on this error at: http://sqlalche.me/e/13/4xp6)
5:54:06 PM – recorder (ERROR) - message first occurred at 5:53:30 PM and shows up 10 times
Adding index `ix_states_old_state_id` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!
5:54:05 PM – recorder (WARNING) - message first occurred at 5:53:29 PM and shows up 10 times
Database is about to upgrade. Schema version: 10
5:54:05 PM – recorder (WARNING) - message first occurred at 5:53:29 PM and shows up 10 times
I waited, tried reloading, rebooting, removing the db (typical provided solutions). I then decided to just restore the snapshot but that is not working either. I get this error:
21-02-03 23:59:25 WARNING (MainThread) [supervisor.jobs] 'SnapshotManager.do_restore_partial' blocked from execution, system is not running
If I try to restart Supervisor I get the following:
21-02-03 23:58:40 WARNING (MainThread) [supervisor.jobs] 'Supervisor.restart' blocked from execution, system is not running
Any suggestions? Command line snapshot restore doesnt work either (created/downloaded a snapshot just before upgrade). This is on the Home Assistant Blue. Thank you.
Edit: Supervisor seemed completely dead but I was able to join the Beta channel and upgrade to that. That allowed Supervisor and snapshots to work. I was then able to restore the snapshot from right before I upgraded to 2021.2.0. Then I went back to the stable version of Supervisor. Not sure how or why but recorder and history were missing from the latest snapshot. That may somehow have caused the entire issue with the update to 2021.2.0 core but I am not sure about one way or the other.
1 Like
Is there any work being done or though for xiaomi devices integration. But a functioning one, not one where you need to find a non existing token?
There is so many devices of xiaomi 
To go back you should be able to just restore from backup. It sounds like your zwave config file might got corrupted. This happened to me a few times. If you have a backup try to first swap zwave config file its in your config folder something like zwcfg_XXXX.xml .
The other issue what might have happend is the usb path device name changed. In your main config under zwave for usb_path make sure you use full path like “/dev/serial/by-id/usb-0658_0200-if00” instead of something like “/dev/ttyACM0” . More on how to get that usb path is here
Hope this helps.
It looks like the format of zwave network key might have changed for zwave js.
Excellent update again, no issues to report at this stage.
This update broke my system. I used the addon ‘Check home assistant configuration,’ and it reported no errors. However, now it is stuck on rebooting waiting for HA to finish restarting. I reboot the host, and the same thing. I cannot restore back to previous version, because
ERROR (MainThread) [supervisor.utils] Can't execute restart while a task is in progress
There are at least three places to check logs, so where do I start?
UPDATE: One of my addons (that I wasn’t really using anyway) docker container never started. I uninstalled it, and everything started up fine. I have (maybe now fixed) some issues with CT100 Zwave thermostat. I couldn’t set the temperature from lovelace, but could from control UI.
I have to say that the new control UI in Zwave JS 2 MQTT is SOOO much better than the OZW one. The old one looks like a barely functional Windows 95 window. The new one is really powerful, and nicely laid out. Kudos to the developers.
1 Like
Details on how to enable support for pico remotes with Lutron caseta are here
1 Like
This team is just bloomin’ awesome - thanks for all the hard work - looking forward to DHCP Discovery, deCONZ logging, and seeing Tasmota is out of beta give me confidence to sever some server ties
Thanks
Since the installation of this version my memory usage has gone to 80% instead of 30% and nothing has changed in the installation only this core update are more people affected by this?
I have tried restoring from backup and my zwcfg looks fine. I restored the entire config directory structure, which I make a backup of every night, but HA still is 2021.2 and no problems are solved.
How can I go back to 2021.1.5? I’m on a NUC, debian 10, supervised