Guy Lavoie

Interesting, so a yolink sensor can activate a yolink output device locally, without needing web connectivity. That's an attractive alternative to the (expensive) local hub. I suppose that a Insteon IOLinc input could be triggered, in the same way you're triggering an alarm input zone. I imagine that triggering a vocal message on the speaker hub can also be done locally? Thanks!

I might add that the Venstar isn't a "smart" thermostat (ie: doesn't learn your habits, sense occupancy, etc) like the Ecobee and Nest units. It's just a very programmable conventional thermostat with the usual features like scheduled setback, varied connectivity options (including a local api), etc. It supports up to 4 stages of heat and 2 stages of cooling, and optional humidifier, dehumidifier, economizer modes.

Response speed isn't an issue for what I want to do: know the pool water temperature. That changes very slowly.

That's what I was hoping to read. Enough to get me to order a temperature sensor. Thanks!

Well ok, that's a starting point. Thanks! Anyone else with specific information and/or experience, chime in!

There is a well defined migration procedure to move from a ISY994i to a Polisy/eisy: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration The advantages are many: current (and supported) version of ISY, ability to use ZMatter dongle, and last but not least: extensive list of plugins to expand your capabilities.

No, no plan for the local hub at this point. I already have lots of Insteon leak detectors and door sensors. But does the Yolink Alexa integration allow asking the temperature of a temperature sensor? What does the plugin provide? Storing the temperature value in a variable? Single event triggers for things like water leak detected? Can you have the speaker hub say something via text to speech? Is there a list of the things the plugin can do, somewhere?

I just picked up a Yolink hub, speaker hub, and vibration sensor, all three for $10. I often read good things about Yolink on this forum so I'm thinking that this is a rather affordable way to try it out. My question is: how is the integration with Alexa? Specifically, if I have a yolink temperature sensor, can I ask Alexa the temperature value? Does the plugin create device nodes that are treated as switches, temperature sensors, etc? Thanks.

That's about as incremental as an upgrade gets. Still, nice to know.

As a test, I once did configure a Philips Hue bulb as a Zigbee device. It worked, but only with minimal features. Otherwise I use them with the hub and the Hue plugin.

Hold on... I was just looking through the Venstar plugin, and found these lines: id = "THERMOSTAT: hint = 0x010C0100 # Residential/HVAC/Thermostat ... id = "SENSOR: hint = 0x01030300 # Residential/Sensor/Climate Sensor

Where are these "hints" defined in a plugin?

I have a Venstar ColorTouch thermostat that's working well. There is a plugin for it too.

I don't think that clearing the java cache is always necessary. I've upgraded several times, and on three different controllers, and I needed to do that only once or twice. Only clear cache if you have problems.

That's the appeal of this plugin for me. It also makes a case for allowing a "minimal" mode where only a trigger is provided, allowing our own program to then do whatever logic we want. Additional baked in functions are nice, as long as their use is optional. I like that. Interesting that you came up with the onOnly function, literally 2 days ago I was reconfiguring a few Insteon motion sensors by adding jumper 4, to have them send On only signals. This is to allow retriggering the on timing in a program as long as there is movement. Having a virtual on only device will allow similar functionality with other types of triggers, nice. So it will produce On control events? I'm asking because I did notice that in the case of virtual switches, they don't produce control events, only status. At least if I switch one from admin console.

All my wall switches and plug in modules are Insteon. Nothing quite beats the scene versatility of Insteon. It's also the "mother tongue" of the eisy, around which everything is designed (controllers, responders, scenes, etc). Then I added ZWave for door locks. I have Weiser locks and they work very well. One thing with ZWave is that battery powered devices (such as these locks) don't act as repeaters, so I had to build up a repeater network using ZWave appliance modules. Fortunately a few local marketplace sellers had new-in-box Jasco ZWave appliance modules selling for $10 each, so I picked up several. A couple even ended up being used for kitchen countertop lighting. I also have a ZWave Watercop valve. Getting ZWave simply expanded my control possibilities. There are no Insteon locks or water valves. And just today, I picked up two used Yolink hubs (including a speaker hub) and a vibration sensor, all for $10. More possibilities coming.

Does the Moen Flo have a known communication protocol? Or an alternate way (such as dry contact input) to operate it?

Just tried 3.1.25. No luck. If you have a chance, do reach out to UDI and see if making it a thermostat device is possible. It certainly would be a useful addition. Thanks!

I'll certainly 3.1.25 a try. I have a test controller that's perfect for this. It would be really great if we could have a virtual device that Alexa could pronounce the numerical value of.

Also, is it part of any scenes? Check that too.

I've only been using the virtual switches up until now. Now for my dumb question: how are the temperature devices meant to be used (as opposed to just a simple variable)? I'm asking about this because I thought that maybe defining a virtual temperature device could allow Alexa to see the device as a thermostat, or something that could report and say the value (temperature or otherwise). This is something that's missing with Alexa: a way to have her say a number from a variable. This could be a temperature, level, percentage, etc. I tried creating a virtual temperature device and then adding it in the portal, but the device types offered don't include temperature or thermostat. I have Venstar thermostats and they do appear as thermostats, so the Alexa device type exists. It would be a great if a virtual device type that Alexa sees as a thermostat could be defined.

If replacing the physical switch still has the problem happening, I think you can pretty well rule out some kind of hardware or noise issue (though never say never...) . Do you have many programs interacting with this particular switch? Have you tried "updating" all references to it by editing each program, re-selecting the switch from the device list, and saving the program?

This discussion brings up a question: will the old 0.1.11 plugin remain available? For those of us who are fine with it and don't feel a need to upgrade?

Well, you get great support by UDI (isy994i is no longer suppoerted), free updates and ever increasing device support (Zwave, Zigbee, Homekit, Alexa, Matter still in beta), an upcoming web based console (eisy-ui), plugins for many popular devices or platforms (Hue, Elk, etc). Essentially, ongoing futureproofing.

To use the eisy with Zwave, you either need the ZMatter dongle, or a Zooz 700 series USB stick (not sure if it's still available). The powerline adapter (2413S or 2413U) is needed if you want to control Insteon or X10 devices. New ones are still available. Most eisy users have Insteon, which is very versatile with scenes, etc. All my own wall switches and things like IOLinc modules are Insteon. I do have Zwave locks, a few appliance modules, and a water shutoff valve. You can probably create an all Zwave setup if you want to. The ZMatter dongle also supports Zigbee. Yes, the programming is still very similar to the ISY994i. Not always sexy, but very functional.