First Alert ZWave Combo [question]

[ragenhe]

I've converted from Home Assistant native zwave support to zwavejs2mqtt.

So far so good. I hope to contribute to this great project.

Is the First Alert ZWave Combo Smoke / CO2 detector supported?

I have excluded it and included it without issue. I know it can take some time for a battery device to complete the query process, but I'm not sure if it is just taking a while to show it's details or if it is possible not supported.

Thank you!!

[robertsLando]

@ragenhe Need to see a log in order to tell you what's gouing on :) Go to store and export both zwavejs and zwavejs2mqtt logs

[ragenhe]

I looked through the logs and didn't see anything that jumped out at me for that node #.

I'll give it some time to show up and if not by tomorrow, I will come back and paste them.

[ragenhe]

After further review, I did see an error in the log. The device is node 20.

zwavejs_1.log
zwavejs2mqtt.log

[robertsLando]

@ragenhe Did you try to manually wake up your device?

[AlCalzone]

@ragenhe please set the loglevel higher. It seems that a response to something is missing, but I can't figure out why.

[ragenhe]

@robertsLando - I thought I did. Let me retry that.
@AlCalzone - My apologies, I had one at silly and one at info. Both of these are set on silly.

Thanks to you both!
zwavejs2mqtt.log
zwavejs_1.log

[ragenhe]

Update:
I went to node 20 in the UI. Node actions = refresh info/values when I had the device in front of me and manually woke it up.
Here are those results:

[ragenhe]

Post successful wake up logs.

zwavejs_1.log
zwavejs2mqtt.log

[AlCalzone]

Okay, we're getting no response to the WakeUpCC interview, so it aborts. I'm going to overhaul the interview procedure so it no longer aborts when we're missing a response, but that will take a bit.

[blhoward2]

Note that this device has always been terrible to interview under any hub. You generally have to remove the battery and close the door with the button down multiple times to complete the interview process.

There is another thread about issues pairing with this device. Summary:

Pair it as stated in the manual. It will go to sleep before finishing, and HA will report “initializing”.
Pull the battery tray out, wait a few seconds. Push test button and keep depressed, insert battery tray. Release button immediately when the device beeps.
Repeat step 2 until HA reports “sleeping” for the device. At this point, I only had a battery_level sensor.
Restart HA. You should now see _alarm_level and _alarm_type sensors for this node.

https://community.home-assistant.io/t/first-alert-smoke-detector-and-carbon-monoxide-alarm-setup/66761/42?u=blhoward2

[ragenhe]

Yes, it can be a pain, and I've tried from many angles. So much so the family is over me messing with the thing, LOL. I'm game to try anything, even a new hub, but this device and hub have been paired prior to using zwavejs. I'll be patient and wait. The project is great and I want to help it advance.

…

On Sat, Jan 23, 2021 at 7:34 PM blhoward2 ***@***.***> wrote: Note that this device has always been terrible to interview under any hub. You generally have to remove the battery and close the door with the button down multiple times to complete the interview process. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1466 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEW5L2UJ7YCWQOX3IFERRZ3S3NTKPANCNFSM4WM76KYA> .

[blhoward2]

I didn’t mean that there isn’t a problem here. I should have been clearer. That was a note for @AlCalzone that it may still be abnormal in the logs/procedure.

[ragenhe]

@blhoward2 - I didn't take it that way, no worries at all!!

[AlCalzone]

@ragenhe please try #1505

[ragenhe]

I updated my dev docker image. I then entered the container and updated via npm install [email protected].

I then manually woke the device up twice. I'll give it a little while and will continue the process.

Thanks!

[AlCalzone]

if it doesn't work, log please ;)

[ragenhe]

I'm going to continue waking the device and then waiting to see if the end result goal is reached.
Node 021

But here are the logs so you can see if it is reacting as expected at this point in the process.
zwavejs2mqtt.log
zwavejs_1.log

[ragenhe]

Because this device can be..... is..... difficult, I want to make sure I give you everything I have.

I again manually woke this device up twice and then restarted the container.

No progress towards in result goal. Logs are attached.

zwavejs_1.log
zwavejs2mqtt.log

[ragenhe]

Another manual wake up....

[AlCalzone]

Okay, I'll take a look at your logs later

[ragenhe]

The status in the screen shot it the same still. Here are the most recent logs.

No rush! Thanks so much!!!

zwavejs2mqtt.log
zwavejs_1.log

[AlCalzone]

13:52:01.268 DRIVER   version 6.0.2

@ragenhe doesn't look like your build is actually using the new version.

[ragenhe]

I ran this from within the container
npm install [email protected]

is this the correct approach to update?

[AlCalzone]

I don't think so. ==> https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/docker_custom_builds

[ragenhe]

I'm on it. Thanks!

[ragenhe]

@AlCalzone - I have followed those directions, but must be missing a step.

I never see the version # get to 6.1.1-0-pr-1505-0102cdc.

[AlCalzone]

With the custom build you have to set the branch name to use.
You should be able to find that in the PR header, something like "wants to merge branch xyz into master".

[ragenhe]

@AlCalzone - Sorry to be a pain. I attempted git checkout cc-no-response and there isn't one in either repo.

Can you see what I should be using instead of cc-no-responce? Please?

Edit: I've been evaluating the wrong # to compare to what version # I'm after. Sorry, I'm a noob at navigation this project, but glad I'm here. I'm building a new, local image (again) and will let you now what the results are when I'm done testing.

Thanks for all the patience with me!

[AlCalzone]

Oh yeah things move fast here. Try the master branch 😅

[ragenhe]

@AlCalzone - I finally have an update to report. Using the current (1/28/2021) master branch of both repos, I successfully included the ZCOMBO and with just one additional manual wake up of the device, it was detected 100% and all expected node entries were found on my MQTT broker.

Please let me know if you want to see any of the logs, or need more details.

EDIT: On the HA side I only have a battery_level sensor and a battery_low sensor, but I will continue working on it all until all sensors make it to HA.

Thanks for all the help!!
Ragen

[gregsheremeta]

@ragenhe I got mine to include, but like you I only see the battery sensors in HA. Did you get the actual alarm sensors working in HA?

[ragenhe]

I did. It all works as it should with the most recent version.

…

On Tue, Jun 1, 2021 at 3:55 PM Greg Sheremeta ***@***.***> wrote: @ragenhe <https://github.com/ragenhe> I got mine to include, but like you I only see the battery sensors in HA. Did you get the actual alarm sensors working in HA? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1466 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEW5L2RU6WMXYX6RQKL4I4DTQU3LPANCNFSM4WM76KYA> .