Dean

I was able to get it to go into pairing mode by pressing the "Action" button 3 times very quickly. I looked back and another Aeotec device gave instructions to press 3 times fast. So, it's now inside. Also, the Aeotec guide said to not add this device securely. Therefore, under the Z-Wave Drop Down Menu, I temporarily turned off the Secure Inclusion parameter. It added it as unsecure. I'll now go back and turn security back on for the Z-Wave. Thanks for all the help!

All good points and thanks! I do have z-wave support checked and also tried to "exclude", but the device is not communicating with the eisy z-wave. I do think that I don't have the device in "pairing" mode. I've tried a single press, long press, etc., but the dialogue box with looking for z-wave device stays on the screen. So, I think the question in my mind is, how do you get it into pairing mode. Aeotec just doesn't make it clear.

I'm looking to add a new Energy Meter via Z-Wave to my eisy. I'm using the standard process with include the device, then pressing the "Action Button" on the back of the Aeotec device. I've tried pressing the button in different ways, but it never registers with Z-Wave on the eisy and the "looking" dialogue box stays on the screen. Can anyone tell me how your device was added to Z-Wave, what buttons you pushed, how long, how many times. The Aeotec documentation doesn't seem to go into the details very well. Thanks in advance.

Great advice!

Bob, Weatherbit did restart sending data to Polyglot again. Thanks for your help!

That is a great idea! Thanks for sharing!

Hopefully, the detector is loud enough. At least I can use them to signal the lights to all come on for safety and the doors to be unlocked. Maybe I'll get a siren that I can trigger. Thanks for everyone's input.

Thanks! I didn't change the settings that had been there for months, but they could have just begun to enforce. I changed the forecast days to 5 and the polling to 1800 and 42300 as suggested in the node. Let's see if it updates.

I saw some information about an issue with Weatherbit. Today, I have no values coming over to the nodes. The nodeserver is showing online, but all values are 0's. I've deleted and reinstalled in the same slot, but no change. Has Weatherbit changed something?

Interesting observation. First Alert mentions that it can interconnect with a hub, but I'll have to look farther to see if there is anything I can do. This may be something @Michel Kohanimand his team need to weigh in on. I assume all of the nodes came over when adding to eisy. https://support.firstalert.com/s/article/Z-Wave-alarms Z-Wave is a wireless protocol that uses radio waves to help smart devices or appliances communicate with one another. The benefit of these alarms is that they can relay alerts to Z-wave compatible smart home hubs like SmartThings or Ring Alarm Security (not included). The alarm links to your smart home hub via Z-wave wireless protocol, while the hub connects to the internet and provides notifications. If your smart home hub supports Z-wave protocols, a Z-wave alarm is probably right for you.

I have the zwave First Alert smoke and CO combo. All works well with eisy. However, I would like to write a program that cause all other detectors to send an alarm if one of the detectors detects smoke or CO. The nodes are a little different in a couple of devices (version). There is no clear definition of each node, so I'm a little clear as to which should trigger or be triggered if smoke or CO is detected. Basically, what I want to do is this: A detector senses and sets off its alarm. At that point, I want to send the signal to all devices to set off its alarm. I can write the IF statement fine. I think those nodes are clear. However, moving to THEN, the nodes are not clear to me as to which to use. The "Smoke Alarm" action only allow Query, Set Configuration and Write Changes. Most other nodes are Query only. Am I missing a basic programming issue with the actions? You can see from the IF code below how some of the nodes are named differently. Smoke Detected - [ID 00A3][Parent 0086] If 'Smoke / DS TV Area -Smoke Alarm / DS TV Area -Smoke Alarm (S2 A' is switched On Or 'Smoke / 1st Floor Hall-Smoke Alarm / 1st Floor Hall-Smoke Detected' is switched On Or 'Smoke / Guest BR-Notify Sensor / Guest BR-Smoke Alarm2' is switched On Or 'Smoke / Guest BR2-Smoke Alarm / Guest BR2-Smoke Detected' is switched On Or 'Smoke / Guest BRHall Smoke Alarm / Guest BRHall Smoke Detected' is switched On Or 'Smoke / Storage-Smoke Alarm / Storage-Smoke Detected' is switched On Or 'Smoke / MBR Smoke Alarm / MBR Smoke Detected' is switched On Or 'Smoke / ZY 061 Smoke Alarm / ZY 061 Smoke Detected' is switched On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Pardon my ignorance! I bought a number of Z-wave First Alert Smoke Detectors and thought I had installed the ones downstairs that I tried to add to the system! I had not! After taking a fresh look this morning, I realized they were the old "wireless", but not z-wave. Opened up a new package and everything worked perfectly. Duh!

I've converted everything over to eisy and for the most part, all went well. I am having problems with the zwave First Alert smoke detectors. I had several installed on the Polisy, but only one came over in the migration. After a few tries, I was able to get the system to interview and update the detector. However, when I try to remove or add the other detectors, it will not see these. I have done a factory reset on the detectors. I saw that Chris had found the bug and it was updated. I am up to date on all packages, so I would think I have the latest. Can anyone give me any guidance on how I might include these in my eisy?

I made this a dedicated IP address. Is there anything I need to do to coordinate the host address with the real address?

Ive just migrated everything over to eisy from Polisy and mostly have seen what others have reported. One thing I don't understand is that when the Polyglot autodiscovers the ISY, it finds it at 127.0.0.1, but all configurations show it on my internal network at the ".2" address. I can manually enter this real address into the configuration, but its not connecting. Autodiscover finds it at 127.0.0.1 and then shows it as connected. Am I missing a basic network principal or how is this configuration handled in how eisy reports its address?