jrainey

Update ... I did some checking and decided to purchase the Eufy E340. It is currently available on Amazon (Canada) at 30% discount (CA$ 159.95), a black Friday deal. -dual camera - sees faces and doorstep -battery or wired. -motion activated LEDs for color image at night.

Looking into this myself. I checked out Eufy, and chatted with their support (bot?). Their Dual model has 8gig of memory on board, able to store 'events'. They also have a hub they call a HomeBase which has 16 gig of memory. The HomeBase integrates multiple Eufy devices. They estimate that the system with HomBase can record about 2 months worth of events, nosubscription required. Unfortunately, there doesn't appear to be any capability to record continuous video, as my Nest Hello does with the subscription service. The reason I am looking into this is Nest has upped the price of their subscription service by about 300%.

Thanks Peter, I feel the same, especially given that my existing devices are dual power.

Thanks Peter, I will check it out. The features of the Nest Protect that interest me are the voice messaging, co detection and emergency lighting. Haven't seen these features together yet in my so far cursory searching. I installed the Kidde detectors about nine years ago. I was disappointed at the time that I was unable to find any models by Kidde or first alert that had either z-wave or Zigbee comms. Hopefully, this capability has been added. Thanks Jack

Thank you for your response. I am not so much interested in matter itself, but I do find the thread protocol very interesting. It appears to me that it is (will be?) very robust and responsive, even more so then either Z-wave or Zigbee. Also, given the support that many major companies have announced for it (and Matter) I believe that a lot of devices will be coming on the market in the future. The reason for the questions is that I am sort of at a crossroads here. I have experienced a number of failures of Insteon devices, and will be looking to replace them. So I am wondering if I should replace them with Insteon, Z-wave (i already have a robust Z-wave installation) try out Zigbee, or go into Thread. I also ask because I love to tinker. What got me started on this particular line of thought is that I will soon be due to replace my smoke detectors. I have been admiring the Nest Protect line, and there has been speculation that it may become available with Thread compatibility. I would love to be able to integrate these (or similar) devices into ISY at some point it the future. Again, thanks for the response, Jack

Hi all Just completed replacement of my Zooz dongle with zmatter dongle. Only glitch was that I had to remove and re-add my three Zooz ZSE29 motion sensors. No problems elsewhere. I have since done a little reading on Thread and Matter, (only scratched the surface really) and I am interested in the future of this ecosystem. Which leads me to the question: Where is UDI planning to go with Thread and Matter? I understand from one of Michel's posts that they have successfully added Thread devices, but this has hurt the performance of the Zigbee network. Not to worry, I am sure it will be resolved. I am wondering, though, where polisy/eisy will fit in this architecture. Questions I have are as follows: -will zmatter act as a thread router? -will zmatter act as a leader? -will zmatter act as a border router -will I be able to share polisy/eisy controlled devices on the thread network? I will likely have more questions as I dig deeper. Just thought I would post this and start a discussion thread. (pun intended). One more question: Where would you like to see UDI go with this new landscaoe? Thanks Jack Rainey

Hi all. Been a long time since I have posted. I am posting because I believe that I am finally ready to migrate from my ISY994i to my Polisy. Current state is as follows: Current: -ISY994i @ 5.0.16c ... 300 series Zwave controller, 2413s PLM -16 z-wave devices, including 4 Yale door locks New: -Polisy @ 5.6.2 (thanks Michel) ... Zooz 700 S2 dongle, 2413s PLM (new-out of the box) I have spent quite a few hours going over as many posts and advice I could find concerning this migration. (special thanks to @dbwarner5 for the excellent guide) I have a number of questions that I expect I can resolve during and/or after migrating, but there is one I would like to clarify a little before I start. This advice comes from the eisy/polisy user guide: "Preparing for Migration from ISY-994 On your ISY-994 Make sure the ISY-994 is upgraded to 5.3.4, If you are migrating your Z-Wave network You must be using a 500 Series Board in the ISY-994" My question is this: Is this correct? Does the migration process actually require 5.3.4 and a 500 series board to be successful? Follow up question is what will happen if I try to migrate from v5.0.26C with the 300 series? Would appreciate any and all advice or hints you may have. Thanks Jack

I have been pondering the same issue for some time now. Finally decided to go with ISY on Polisy. The clincher for me was that our supplier (in Canada) is offering Polisy bundled with a PLM. Noticed this over the weekend, called this morning and yes, they have 10 PLM's in stocks, which they are only selling in the bundle. Sales rep says they are going like hotcakes. My plan is to migrate my existing ISY to IoP, then start to slowly (over years) replace what I can with z-wave devices. I have been unable to source some items, like the irrigation controller and a 240v load controller, but am sure other solutions will become available if it becomes absolutely necessary. (when my last PLM fails) That is my path, fwiw. Jack

Was looking into this topic earlier today. Seems that Mobilinc has switched from (abandoned?) their Mobilinc Pro product for a newer subcsription based product called Mobilinc X. Checked out reviews in the play store, and found that the subscription prices ranged from $9 and change per month, to something over $200 that might have been a lifetime subscription. Average rating was 3 stars, with a lot of 1 star ratings. Most of the low ratings appeared to be objections to the price, many of which had an answer from the company saying that there were a number of payment options available. For my part, I was unable to easily see how much it would cost by looking around the website, so I quickly lost interest.... Jack

Thanks Larry, Any idea where people are turning? Am considering getting rid of the whole works if there is no change. I have been disappointed for a while now, considering issues such as PLM lack of reliability, and other issues like intermittent scene failures etc. I have for a long time thought that the reliability of communication in this system comes nowhere near what is required of an industrial system such as a DCS or PLC.

Darn, I was hoping that maybe The Bahamas or Trinidad would buy us up!

Hi people, Just visited Aartech's website for the first time in a long time. Aartech is the official Canadian distributor for Insteon and Universal Devices products. I found inventory for products from these suppliers did not exist, and where the products were listed there was a note saying "NO ETA". Took a quick look around this forum, and couldn't find any info, so I thought I'd start a topic to find out. So what is happening? Are any of these companies going out of business? Are semiconductor supply shortages causing the issue? Are there any other Canadian suppliers around? It's got me a little worried as my entire house is equipped with Insteon devices. Comments? Thanks, Jack Rainey

Most routers have the ability to reset to factory default settings built into them. My suggestion is that once you have the new router up and running reset the old one to factory default before returning it.

Check out the topic "Strange problem - looking for ideas". This was PLM failure that progressed over many weeks. My suggestion would be to try a factory reset on the PLM, and go through the PM replacement procedure. I was finally convinced that my PLM had failed when it would not reset. Jack

Good point oberkc. There were two differences between the original program and my suggestion though. The first was, as you noted, the use of a scene. The second was moving the timing from the program into the built in timeout function in the motion sensor. I am not sure how aware people are of this feature, and wanted to point it out. Jack