Thanks! Hopefully so.

Welcome. Glad you are making progress. My 910's have been working flawlessly since the first couple of updates on the new zwave js stuff that HA is now using as default.

You're welcome! Glad it was helpful!

You're welcome!

You're welcome! Glad it helped!

True. I probably just overlooked that. When I do some of the vidoes, I've already played around in the system a bit and think I've done something I haven't. Thanks for pointing it out.

Glad you liked it!

Is this with using the individual polling setting in zwavejs2mqtt or being able to set a specific device configuration?

Setting a specific device configuration in zwavejs2mqtt. The default settings made the light sensor unusable. Specifically, the light sensing level and the light sensitivity level.

Excellent. Glad it's working for you now.

Thanks for the comments. I am still working on the zwave combo for JS. It shows because it was on the stick before but it shows as unknown. I probably need to remove and re-add it. I'll add the tutorial request to my list of videos. Thanks for the suggestion!

​@@mostlychris watched both videos, this and the live stream again, and got it working in HA nice and easy

Outstanding!

I forced polling in zwavejs2mqtt for now since the locks weren't updating when manually turned. Hoping to have they resolved soon. Poling = bad but it's a temporary workaround.

@@mostlychris I'll give that a try. Nice job on the video. You are about the only source out there for Zwave JS right now. Thanks for the hard work.

Thanks for the compliments!

@@mostlychris you may already know how to do this, but I was able to use alarm_type and alarm_level to determine the state of the lock. I created an entity in the "sensors" file that looks at these two values and gives the state of the lock. Works great with my 914 smartcode keypad lock, not as well with my "convert" lock.

here's my sensors.yaml entity: driveway_door_lock: friendly_name: "Driveway Door Lock Status" value_template: >- {% if is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type', '18') %} locked by keypad {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type', '19') %} unsecured with user id at keypad {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type', '112') %} new user code added {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type', '162') %} attempted access by user outside of schedule {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','22') %} unsecured manually {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','21') %} secured manually {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','27') %} auto secure sucessful {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','17') %} secured at keypad - jammed {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','26') %} auto secured - jammed {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','23') %} secured by controller - jammed {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','24') %} secured by controller successful {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','25') %} unsecured by controller sucessful - fully retracted {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','32') %} all user codes deleted {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','161') %} failed user code attempt at keypad {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','167') %} low battery level {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','168') %} critical battery level {% elif is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_level', '1') and is_state('sensor.kwikset_spectrum_brands_touchpad_electronic_deadbolt_alarm_type','169') %} battery level too low to operate {% endif %}

For me 2 reasons. 1) I already have it installed and running and 2) I use the console to change individual settings on some of my devices. Most recently, I changed all the LEDs on my Zen32 controller directly from the console. It also has a neetwork node map that is useful in some cases. Really, the UI is the best part.

@@mostlychris Thanks a bunch!

Typically, the devices are stored on your zwave hub. I like js2mqtt simply for the interface and being able to see things at a glance. If you are just starting, I'd recommend using js2mqtt for a nice view of your network..but again that is my personal preference. They both work equally well.

That should be a one-time issue. Once you have everything installed and named in HA you shouldn't have to mess with again. It's part of the migration process. In fact, the add-on doesn't have names either. It would be nice if it were able to be a one-stop name, but I haven't had to rename/name anything unless it is a new add since going to this setup.

That is an interesting idea. Question for you though. If you were to set that sound value, how long do you have to wait for it to apply before activating the siren? I would be concerned that it wouldn't always change the sound before the siren activated and then you would get the incorrect sound.

@@mostlychris Good thought. I have read through the instructions and specs and of course there is no mention of command delays. Empirical testing using the z-wave2mqtt GUI shows a second delay would work, thats as fast as I can change the sound and then activate it.

There have been some updates to zwave js since I made this video to address these older locks and I used bolt status until I started using the keymaster integration (watch my video on that). I've had to make a few changes to my automations based on changing zwave js iterations. That is to be expected as they work to bring zwave in HA up to date with current standards.

You will probably have to do a one time rename moving to js2mqtt. As a note, you can't run both at the same time. Verify you do indeed have port 3000 enabled and that the js2mqtt add-on is actually running.

You can install portainer and look at the port mappings used by each add-on. You can also just randomly choose another port. Then make sure you match the port you are pointing to in the extension to what you configured in the add-on.

@@mostlychris Perfect, thanks for update. I thought Z-wave JS is setup to be used on port 3000 only and no one else. Will try now some other port.

No problem.

Hmmm. Here is my zwave playlist: kzfaq.info/sun/PLFFSkDDgcMExTuw1BI5RqL0E2dMpOu_yt. What are you trying to set up in zwavejs2mqtt?

@@mostlychris As mentioned before, you mention a video at 1:10 for installing zwavejs2mqtt. I've looked at your playlist. I don't see any videos on the playlist, or when I search your videos, regarding installing zwavejs2mqtt. I see were you installed OpenZWave and when migrated to ZWaveJS but clearly these are not the video you are referring to.

@@Dorff_Meister Ugh. Let try and find it. I'm not sure what I was referring to then at 1:10. Maybe general zwave stuff at that point. Installing zwavejs2mqtt is just like installing other add-ons. You need to make sure that nothing else is using your USB hub before selecting it in the dropdown. Beware though that your zwave devices are all stored on the USB hub so zwavejs2mqtt should see them. However, they might require naming in HA itself and you'll have to point the zwave integration in HA to use zwavejs2mqtt and not the built in zwave js add-on. To do this, you'll need to delete and re-add the integration. As I type this, I remember making a video on this very thing. I'll keep looking for it.

I think it should be there on the latest update. Interesting that it isn't in there.

This is what I am using on my supervised system: Server URL: ws://a0d7b954-zwavejs2mqtt:3000. I assume you have port 3300 set in the configuration of the add-on?

Thanks for the tip David. I have learned a bunch about getting links, etc., into video and have done a better job since this video. Here is the one I was referring to: kzfaq.info/get/bejne/jr6TfbyEyNa5eHk.html

I believe that you would just delete the integration in Configuration -> Integrations and then re-add it. You would then tell it to use the WS server instead of the built in Zwave JS add-on. I'm not 100 percent sure but I think it uses the same names. What are you looking for using the other add-on? Is it the UI? Also, don't run both add-ons at the same time.

Does the zwavejs2mqtt panel show the zooz usb stick? Do you show it in the zwave js integration?

Integrations should get updated when HA updates. The add-ons should prompt you when there is an update available.

@@mostlychris Thanks!

I haven't tried it, but there is supposedly a migration tool available to move from older Zwave to Zwave JS. That might be what you need. I just took the hit and did this one time when migrating manually. It takes some time up front but then you're done.

@@mostlychris I tried the migration tool, but none of the names came over, so I sucked it up and renamed everything once already. Still kind of fresh in my head, so if I have to do it again, not the end of the world. At least I only have 16 devices right now. :-)

@@OblivionRatula Yeah. Good news is that zwave JS is the long term solution so you shouldn't have to go through it again.

I think we took care of this in Discord. If not, let me know.

Hey Frank. You can use either the zwavejs2mqtt add-on or the zwave js add-on. Either of them will get you the zwave you need and hopefully future proof it for you as JS is the way things are going in the Home Assistant world right now. The benefit of zwavejs2mqtt is that you have a UI to configure your devices if you need it. Some people don't need that functionality. Of course, there is the mqtt component but I have that turned off currently since the Zwave JS integration in Home Assistant can talk to the WS server on the zwavejs2mqtt add-on. The path is zwave device -> zwavejs2mqtt -> zwave js integration. A similar path would be zwave device -> zwave js add-on -> zwave js integration. You can choose either path. I do have a video on migrating from stock Zwave to OZW in Home Assistant. The concepts are the same for the most part.

That doesn't make sense. Maybe restart the one that isn't showing the add-on or go to supervisor from the left panel and click reload supervisor.

Check that the instance not showing the add-on is set to use "Advanced Mode" in the Profile settings.

@@xsirenonthe101x that's a good advice, however the advanced option is already ticked.

@@eolenet7529 darn. Was the first thing I thought of.

This add-on was removed temporarily for it's opt-in policy. That has been addressed and the add-on is now back available. You need to make sure you are running the latest version of Home Assistant and you'll see the add-on now. I have a community post on this very thing. Make sure you are subscribed to get updates ;)

There may be a setting that tells the sensor how often to update or at what temperature threshold an update should be sent. This is device dependent so you would need to read through the update options on the zwavejs2mqtt config for that device.

@@mostlychris hi, thanks for the answer. But that’s exactly what I did. You can choose if it should send temperature changes at 0.1 or up to 0.5. I tried every number. But I never got any automatic update of the current air temperature

​@@MikeSarhage Surprised YT didn't block that comment due to a class of drug reference. I did some searching and there is supposed to be a fix in these versions zwavejs2mqtt: 5.10.1zwave-js: 8.6.1. Make sure you are running the lastest js2mqtt and zwave-js (and home assistant) versions.

@@mostlychris updated the comment. Don’t know what I tried to type there… my Mobile supposed this should be this word. 😅 I’ll check the versions again. Thanks so far

Personal preference. The zwavejs2mqtt has a UI that allows me to set configs on devices. I don't use the mqtt part.

Hey Mathai. There are a number of ways to do this. A simple automation in Home Assistant UI should work. Navigate to Configuration->Automations. Add automation. Give it a name. Choose Time from Trigger Type. Set the time you want it to turn on in "At time". In Actions choose "Call service" from Action Type. Choose "Switch: turn_on" under Service and then in Targets choose your entity that you want to turn on.

It's back now. It was temporarily removed for opt in concerns.

@@mostlychris When I go to www.home-assistant.io/integrations#search/zwave and search for zwave - I don't see zwavetomqtt - it doesn't show in my integrations in HA - am I missing something?

Go into your home assistant add on store and search for zwave. You should have a number of zwave options. It should show up there. Make sure you are running the latest home assistant.

@@mostlychris Thanks Chris - Confirmed (for others) it took a core upgrade to HA that showed up this morning (4.3) to have it come back. Appreciate the quick response!

Excellent. Glad you found it.

Thanks for the tip. It is quite likely as you said-- there are some newer versions between this video and the latest version of JS.

Maybe it's time for a refresh. Things in the UI have changed quite a bit since I made this video.

@@mostlychris I finally got it working. I uninstalled all Z-Wave add-ons and reinstalled them. There were only one or two steps different from your video. Thanks for the instruction!

Excellent! Glad you got it working!

The comment thread doesn't show me what this is in response to--or YT deleted some other comment. What is the reference here?

Are you running the latest zwave add-on and latest Home Assistant? Are these all battery powered devices? How long have you waited once everything restarts to restore a snapshot?

@@mostlychris Thanks for responding! I believe everything is current (core-2021.5.5 supervisor-2021.04.3 Home Assistant OS 5.13 Z-Wave JS Driver Version: 7.5.2 Server Version: 1.6.0 Z-Wave JS to MQTT Current version: 0.17.0) 17 Battery devices 38 Non-Battery powered devices. I have only waited a few minutes to about 10 minutes after restart, but they always come back after a snapshot restore. How long should I wait before attempting a snapshot restore? Windows sometimes restarts to perform updates and VirtualBox gets shut down in the process. I have the VirtualBox HA session automatically start after Windows reboots. That's when I loose the devices. The devices are listed but don't respond and Manufacture and Product IDs are unknown. I waited 10 minutes and restored Snapshot and devices come back.

@@louismartino3241 Some things to try. Wait longer--like an hour or more. I would think this stuff should load from cache as noted in some conversations I've read. However, there might be a lot of polling going on that would result in things not showing correctly until the network settles down. The more stuff you have, the longer it takes for your network to become availalbe after a zwave restart--or in your case a whole PC restart. One of the benefits to running zwave in a container now is so that HA restarts don't cause the whole network to have to restart and "rebuild". The ideal situation is to put your zwave on something that doesn't restart. Again, I would have thought things would at least load from the cache files upon restart but that doesn't seem to be the case. Have you tried just restarting the add-on? Have you tried restarting HA itself? I have had issues lately after an upgrade in which my network was not showing any responding devices and I had to restart HA itself for this to work.

@@mostlychris Last night, the Z-Wave network was not responding and I lost all devices. The Manufacture & Product ID's were listed but no confutation data was listed in the dropdown. The only way I could get everything back was to reboot the Windows 10 computer and then restore a recent snapshot? Not sure how to troubleshoot this.

@@louismartino3241 Unfortunately, I don't know either. One other thing that *might* be an issue is the selection of the device in the dropdown. Is it possible your OS is changing the name of the USB device alias and you are relying on that alias? Make sure you are using the actual device ID for the USB stick. Rebooting the host might free it up and allow HA to grab the USB stick. Just throwing that out there.

Hey Benoit. I try to either show a link in the video while I'm talking about it or put it in the video description. Apologies if I didn't do that this time. Here are links to my other zwave migration type videos: kzfaq.info/get/bejne/jr6TfbyEyNa5eHk.html and kzfaq.info/get/bejne/nJldY6mQntqypHk.html

@@mostlychris thanks 🙏

You're welcome! (Thought I already replied). The comment system on here is quite the experience to manage.

I create content based on what I think is relevant and helpful at the time of creation. This video highlights the migration from one Z-wave solution to another. It does not imply that it is a solution for every situation out there. I have installed multiple versions of Z-wave on both my production system all the way from no Z-wave to the latest add-on. I have recently done the same on my test raspberry pi and this had no other Z-wave stuff on it. There is a video in my Back to Basics series talking about that install. I am not sure what your screen is showing and how it differs from the video since you didn't provide any details nor did you explain what issues you might be having. I would be happy to do my best to assist you if you can explain what problem(s) you are having.

Are you running more than one instance of zwaveJS? You can only run one since you can't share the USB device. Do you have your USB device correctly selected?

@@mostlychris I am hitting a very similar issue. New install on a new Pi. only thing plugged in is the Aeotec zstick gen 5. I can see it is /dev/ttyAMA0 but I can not get past this step. Been slamming my head against the wall for about 3 days now. They sure dont make this easy... EDIT: AH HA! Seems that the Pi doesnt like to run these sticks directly, they need to be plugged into a powered hub (though its not because the pic doesnt have enough power to work with...) "Hi all. Just an FYI. I’ve been working with Aeotec engineers on the New Z-Stick Gen5 that fixes the problem with the current Z-Stick not being recognized by the Raspberry Pi 4 when connected directly to its USB ports. The workaround has been to use the Z-Stick plugged into a USB hub attached to the Pi. I can confirm that the New Z-Stick Gen5 works directly connected to either the USB 3 or USB 2 ports on the RPi 4. Specifically, I have a 4GB RPi 4 running HA 0.111.4 on HASSOS 4.10 off a 64GB SD…" posting here just in case it can help anyone else!

@@matthewswan1873 That's interesting since I used to run this stick directly on the pi without an external hub. I was using a Pi power supply that have full juice though. Maybe something changed.

Brightness?

Yep. Lots of things have mDNS now and will allow connections to hostname and not have to use IP. Unfortunately, some things don't work that way in an IoT world.