Merlin

I was thinking more along the lines of someone who purchased one of these remote shutoff valves, and then replaced it with another model. It would be nice to understand why and what worked or didn't work. For example, I see a lot of folks posting about how they moved away from the Moen Flo to other devices (or got away from an automatic shutoff completely). Though I suppose folks with more than one home (or rental property) might also have a use case for having more than one type of shutoff valve and would allow a comparison. Wishful thinking perhaps?

I'm curious if anyone has done any comparisons between the Zooz Titan and the EcoNet/YoLink Bulldog Valve Robot in terms of reliability, etc. I am still entertaining the idea of getting a mechanical ball valve connected to a relay, but it feels like that may be overengineering the solution to a simple problem if there are simpler options available.

Yeah, it looks like YoLink has a couple different models, including their own implementation of the Bulldog Valve Robot. I'm going to be taking a more serious look at their stuff soon. I have a plumber coming in next week to take care of some other issues, so I am thinking I will have them swap out the gate valve for a ball valve either way. That way I have more options for adding an external valve operator that is easier to deal with if something fails. I'd also like to add a water pressure gauge while I'm at it, but I don't see any monitored pressure gauges... not that I really need it to be. It would also be nice to have a flow meter on there, but unless I'm writing my own monitoring apps, I don't know how valuable that would be.

Thanks for the advice. I got the Kasa node server trial up and running today. I only have 1 Kasa device that I'm using right now, but it's a good test and is helping me get used to PG3x. Doubly so since the initial Kasa install wasn't working, so I've been learning more about how to stop/start and delete/reinstall node servers, etc.

Same for me.

I am having the same issue here. I just upgraded to IoX 5.7.1, PG3x 3.2.16, with a fresh install of the Kasa 3.1.1 trial. The log just shows the Kasa python app restarting over and over because it cannot find the kasa module when trying to initialize the service... 2023-11-28 02:06:13,696 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.5 Starting... 2023-11-28 02:06:13,698 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902670b_1/kasa-poly.py", line 12, in <module> from nodes import VERSION,Controller File "/var/polyglot/pg3/ns/0021b902670b_1/nodes/__init__.py", line 9, in <module> from .SmartDeviceNode import SmartDeviceNode File "/var/polyglot/pg3/ns/0021b902670b_1/nodes/SmartDeviceNode.py", line 8, in <module> from kasa import SmartDeviceException ModuleNotFoundError: No module named 'kasa' Since there is already a ticket, you can just +1 me to that.

Seems straight forward. Once I better understand how PG3 works, I'll need to give it a go.

So using YoLink still requires a YoLink Hub in addition to the eISY node server for YoLink? The price is less of an issue than where I'd put the thing. But, I assume that means that one can use the YoLink app in addition to the eISY to connect to the YoLink stuff. But it also sounds like it won't work if the internet is down since it requires cloud access. I have UD Mobile installed on my phone and I have tested that it works, but I don't have any notifications set up. When I go into the IoX admin portal, under Node Servers -> Configure, all 100 entries say "Empty," so I assume I don't have anything configured. I have been looking at the Wiki to try and figure out how to use Node servers, and like most of the wiki, it isn't very straightforward. I know PG3 is used for node servers and there is also an Occupancy node server, but I don't see what the difference is, or how to set things up on the eiSY. I see some examples for the ISY994, but I am sure that is dated. I have some Kasa EP25 smart plugs that I had from my old house, that I really only use for one-offs like controlling xmas tree lights. I currently use the Kasa app and/or Apple Home to control them, but I'd like to add them to the eISY as a node server test as I am told there is a Kasa node server.

Sorry, I only recently upgraded to the eISY from the ISY994 and am not really completely up to speed on the node server stuff aside from an understanding that it exists and allows the eiSY to communicate with non-natively supported devices. I asked earlier if there was a node server for YoLink to allow it to be used with the eISY but I didn't see any responses, so that is why I was asking for clarification. My assumption is that the node server allows the eiSY to speak to the YoLink devices as if it were a YoLink hub and that it otherwise operates as if it were a native Insteon or Z-Link/Zigbee device from the perspective of the eiSY, yes? Given that, it sounds like it would be worth getting a device or two to try them out. Though I suppose the next question is how do we add/remove YoLink devices if we are not using one of the native protocols? I'll need to check the wiki to see what I can find there.

I'd be happy to try out the YoLink stuff. I took a look online and found a bunch of really professional looking devices, but if they are not interoperable with the eISY, I am not sure what the point is. I don't want to deal with multiple independent systems. I already have water sensors and other automation devices I'd want to be able to use with whatever I end up with for water flow monitoring and/or water main shutoff.

Hmm, I don't have any experience with YoLink. I've found the Aeotec and Zooz stuff seems to work pretty well, so they are my go-to for Z-Wave stuff, but I'm happy to take a look at other brands. Looking at the YoLink water leak sensor, it looks like it requires its own hub and isn't Z-Wave compatible. Is there a node server for them or something? Maybe I'm looking at the wrong device? I see that YoLink also has a smart water valve controller that adapts to the existing ball valve by replacing the handle with a motor. But again, requires a YoLink hub to use. That said, I did just order another Insteon leak sensor since it was like 35% off. The one I have now has been working fine for years. Though I've heard others saying they stop working after 3 years or so. But you're right, it would be nice to get a battery level report.

I didn't even know Aeotec had a ball valve actuator. I'll need to look at that one too. As for the Insteon Leak Sensor, you're right... I see it on the Insteon site now. It wasn't there when I last looked (granted, that was a few months back) so that is handy to know. I may pick some up given the current sale going on. Though I'd also like to find a moisture/leak sensor with a wire lead that I can route into places where a flat/floor sensor, like the Insteon, wouldn't work. Thanks!

Well, I am currently using an Insteon 2852-222 Leak Sensor, which is wireless. I plan to pick up some more leak sensors, but with the Insteon model discontinued, I will likely get the Aeotec or Zooz Z-Wave leak sensor for the other locations I want to monitor. So, that is always going to be a potential issue. After reading all the horror stories about using in-line "smart" valves (like the Moen Flo) I am leaning away from getting an in-line valve and just installing a traditional ball valve with an external valve controller, like the Zooz Titan to make it easy to remove/replace if it fails down the road. That said, my home uses hydronic heat, with each zone operated via 24V Taco Zone Sentry valves. So, I would be more comfortable using one of those for the water main as well. I know they work well and are designed to last for years. I'd just need to find a 24V remote activation module (one that supports ethernet would be nice, though the one you linked is no longer available). Yeah, after reading all the horror stories in the reviews of other "smart" valves, I have come to the same conclusion. But yes, if I were to get one, I'd add it before/after a manual shutoff in case of failure. I am considering the Zooz for ease of operation and replacement though. What are your thoughts on the Titan? Thanks! I'll take a look. What are your thoughts on the Zooz Titan? I'm still weighing my options, but I really appreciate the feedback folks!

Hi IM, I picked up 3 of the Aeotec Multisensor 7's. So far they have been working great. They included on the eISY properly the first time and there have been no problem with them responding to commands. They also have a ton of nodes, most of which I have no use for, but I think that is just the way the [e]ISY operates without a database for every piece of kit out there. They include two CR123A batteries if you want to put them in a remote location, but they can also be USB-powered, which is how I am powering the units I have. They also operate as a Z-Wave repeater in that configuration. As for the ZSE44's, I think I may end up returning them. Between the communication issues and the lack of a mount, they aren't really going to work for what I need.

I am running an eISY with a mix of Insteon and Z-Wave devices, including a couple of flood sensors, but no automation for the water shutoff if a leak is detected. My water main currently uses a traditional gate valve so I assume I'll have to replace it to add any automation. If I replace the existing gate valve with a ball valve, then I could use an external valve actuator like the Zooz Titan. However, there are also "smart" valves out there, like the FloLogic and Flo by Moen which provide water main closure automation integrated into the valve itself. My question is, if I have to replace the current valve anyway, what do others here use/recommend? I'd prefer something that is interoperable with the eISY so I can make it work with my existing flood sensors. But, I am okay with going a different direction if needs be for reliability. The Zooz is Z-Wave, but I've heard it can be unreliable. I know that both the FloLogic and Moen devices have WiFi capability and connect to their own mobile apps, so I imagine a node server may exist to communicate with them. I don't know much about them otherwise. I imagine there are other devices I am unaware of. I welcome any advice/suggestions. Thanks!

Hey folks, I recently moved from ISY994 to EISY and noticed that I'm having issues properly adding Zooz Z-Wave devices to my network. I have a ZSE29 Outdoor Motion & Light Sensor which I picked up a few months ago. After some initial issues migrating it to the EISY, I managed to get it working properly after exclusing and reincluding. In general, it has been working pretty well overall. However, I just picked up a pair of ZSE44 (firmware 1.30) Temperature/Humidity sensors. I ended up having to include and exclude the first one a few times before I got it to add properly. I initially used S2 authentication, but it didn't add any nodes, even after a resync update or replace with interview a few times. Using S2 unauthenticated solved that problem, allowing me to add both without issue. They both finished their interviews completely, according to the XRay DH Command Classes report. However, both devices still show the green "1011" symbol. All attempts to write changes never complete, despite telling the ZSE44 to wake up (using the 4 button clicks) repeatedly, before during and after the write command. I also tried using the Wake Up node to set wake up interval to 15 seconds, and setting the keep awake on; neither of which appeared to work. Does anyone have any other idea for how to get these to update properly? Before anyone asks, I added both ZSE44 devices within 5 feet of the EISY, and the ZMatter/ZWave USB dongle has both antennas attached. I am running IoX 5.7.0 if that matters. On the bright side, both devices appear to be properly sending temperature and humidity updates. Which is good, but it would be nice if I could get them to wake up long enough to accept writes so the 1011 goes away. I saw others on the forum have had a similar issue, so it may just be an issue with the ZSE44 devices themselves. Additionally, I noticed that both devices added 12 nodes: Heat Alarm - node 1 Moisture Detected - node 359 Multilevel Sensor (Temperature) - node 118 Overheat Alarm - node 166 Underheat Alarm - node 168 Weather Sensor (Humidity) - node 373 Weather Alarm - node 317 Wake Up - node 199 4 x SC Basic Assoc 2-5 - nodes 252M002-005 I really only care about nodes 1, 118, 373, and 199; IMO, the rest of the nodes don't seem like legitimate nodes for this device, or at least, they are practically useless for a temperature/humidity sensor. Plus, I don't know how to configure the alarms. The configuration info in the manual doesn't even mention them. Aside from just throwing those nodes into a folder for useless nodes, is there any way to adjust the device database to tell it which nodes we want to use/create when including devices and which to ignore? I have a few Aeotec Multisensor 7's coming tomorrow. That will be my first experience with Aeotec, and I'm curious to see how they compare to the Zooz. If they work better, I may end up sending the Zooz back and getting the Aeotec Temp+Humidity sensors instead. Thanks!

As a followup, interestingly enough, despite the two devices not being able to communicate. I was able to remove via exclusion and re-add (under a new ZY id) without issue. Of course, now it doesn't appear to want to wake up long enough for me to write updates to it, so I still have some tweaking to do. I still haven't figured out how to poll Z-Wave devices via ISY to get their current parameter settings so I can set them manually. Previously, I was able to change some parameters blindly, but I don't know if those parameter changes persist after excluding and including the device again.

I've already tried sync/update with interview, but the SZE29 doesn't appear to be listening/transmitting to the Z-Wave/ZMatter dongle. I'll wake it back up and try one more time, but then I'll just plan to remove it. I'll try excluding first (assuming the - Remove a Z-Wave Device from the menu bar puts the EISY in exclude mode) and then re-add. If that doesn't work, I'll remove the node manually via Remove a Failed Node and factory reset the ZSE29 so I can re-add it. Yeah, that is what I expect I'd have to do. Not worth the time/effort. My only worry is that I read something about being a max of like 200 Z-Wave node ID's or something. As long as it wraps around and re-uses the unused nodes in the lower ID ranges if it hits the cap, then I don't care. I am trying to lean more toward Z-Wave where I can, in case Insteon v2 ends up suffering a similar fate to v1 down the road. So I plan acquire more ZW devices in the future. Maybe experiment with Zigbee and Matter down the road as well since I can now. Thanks!

Hello! I just completed migrating my ISY994i to EISY. My network has around 40 Insteon devices and 4 Z-Wave devices. The Insteon devices all migrated without issue, as did 3 of the Z-Wave devices (which are all powered Z-Wave Plus smart outlets from GE Enbrighten). However, the Zooz ZSE29 outdoor motion/light sensor refuses to come along for the ride. Its nodes still show as (Placeholder) in my eISY node list after more than 24 hours. The SZE29 has been working fine for the last couple of months on my ISY, waking up every 30 minutes to check in, and sending real-time updates for motion (and 15 min updates for light levels). Following the migration guide, I assumed it would interview/sync within 30 minutes when it next checked in... but according to the event viewer at level 3, it has yet to do so. I left it running for 24 hours to see if it would sync on its own, but it hasn't. So I went up on a ladder to bring it down and removed/replaced the batteries to get it to wake up. But I'm not seeing anything on the event viewer. I did it again and had the eisy sync -> update with interview at the same time in case, but nada. At this point, I am assuming that the ZSE29 didn't migrate properly and that I need to re-link the device somehow. Perhaps it has something to do with security as the ZSE29 uses S0-S2 security by default; though I think the ISY only supports S0. So it's time to re-link. I'm still a bit new to the Z-Wave stuff and the wiki manual on the UD website isn't incredibly helpful. From the Z-Wave dropdown on the sensor, I have the option to remove a failed node, replace a failed node, or synchronize to update/replace with or without interview. I can also try to exclude and remove the device that way. Synchronize -> Replace seemed like the right choice, but it seems like that just deletes and recreates the nodes for an existing device, with or without an interview. Speaking of, will this assign a node a new ZY number or just remove and rebuild it in place? Replace a Failed Node seems like the next best option, but it says that just deletes and replaces the ISY nodes for a malfunctioning device, much like the previous option. I'm not sure what this does. It seems like it is similar to the above, but if a device is malfunctioning/not responding, what is the point of recreating its ISY nodes? Either way, that won't help. Exclusion... looking at the manual for the ZSE29 for exclusion, it says I need to put the ZW hub into exclusion mode first and then toggle the tamper switch 3 times to remove the device. Should I assume that – Remove a Z-Wave Device from the Z-Wave main menu puts the eisy into exclusion mode? The wiki doesn't use the word exclusion, but reading through it, that sounds correct. Remove a Failed Node seems like the only remaining option. It says this should only be used when a ZW device cannot be removed via exclusion. I imagine this is what I need to do, since the ZSE29 isn't speaking to the eisy. In this case, I assume I will just need to factory reset the ZSE29 and repeat the inclusion process to get it added back again, yes? Though with a new ZY node number. Speaking of ZY node numbers... beyond factory resetting the Z-Wave/ZMatter dongle and re-adding all my Z-Wave devices, is there a way to reset the ZY node numbers so they start at 1 again? Right now my Z-Wave devices range from the high single digits to the mid double digits due to experimentation. It would be nice to get them so they are using nodes 1-4. Obviously, it isn't a huge deal (assuming the unused node numbers get reused if we go over the limit), but it would be nice to be able to reset them. Thanks!