Guy Lavoie

I created another test today: copying the temperature (of the temperature sensor) to a variable. I triggered it with the s_yolink_trigger variable as shown in my programs above. The value was correctly copied into the variable.

Well even in 6.0.0, Matter is showing as Alpha Test Version. We're basically being offered to try it out and discuss our findings. I personally enjoy being included in the test phase. It'll come along.

Does anyone even use the wifi capability of their eisy? The biggest single improvement of the new R2 is probably the reduced power consumption. There have been reports of these little boxes getting quite hot when installed in confined spaces.

Ok, I'll try and do that either later this evening, or tomorrow. 6.0.0 does seem to have affected some plugins, as we've seen on the forum.

Well if the switch works from admin console, then it's linked properly. Try listing the program here (copy text to clipboard) and post it here.

I installed the Yolink plugin and configured the UAID and secret key. I currently have a vibration sensor and a weatherproof temperature sensor (set up for testing). The nodes came up fine, and the status display for each device appears to be correct. But I'm trying programs and things aren't working as I would have thought. I created two test programs, one for each device. 1- I created a test program for the vibration sensor (configured as a DON/DOF device), first to detect a control event: yolink vibration test - [ID 00BF][Parent 0001] If 'Vibration Sensor' is switched Vibration Detected Or $s_yolink_trigger > 0 Then $s_yolink_vibration += 1 The "Or s_yolink_trigger > 0" statement is just to test that the program is running ok and that the variable display in admin console is updating in realtime. The sensor detects vibration ok (LED blinks), and triggers a Alexa message that I set up in the Alexa app, but the s_yolink_vibration variable doesn't increment. As if the plugin wasn't seeing it. Even if I wait 10 minutes or more for the time to go beyond the "last poll time" in the Yolink Setup node (shows as online and ready). I then modified the program to look for a status change instead. yolink vibration test - [ID 00BF][Parent 0001] If 'Vibration Sensor' Vibration State is No Vibration Or $s_yolink_trigger > 0 Then $s_yolink_vibration += 1 The first quirk is that no matter if I choose "Vibration" or "No Vibration" for the Vibration State status and click on update, the program line always shows "No Vibration" as above. There are also two "Vibration State" statuses to choose from in the list, but both only show "No Vibration" when you update the line. Ok, so I tried making it "if is not No Vibration" a double negative... But no matter what I try, the variable never increments. 2- I thought I'd then try the temperature sensor. Created the following test program: yolink temperature test - [ID 00C0][Parent 0001] If 'Temperature Sensor' Sensor Temperature > Updating (may take up to 1 hour) Or $s_yolink_trigger > 0 Then $s_yolink_hightemp += 1 The first quirk is that in the program editor, what I actually entered is if the temperature is > 26, but the program always shows as "Sensor Temperature > Updating (may take up to 1 hour)". I can't get it to display the temperature value I programmed, though it seems to save it correctly because if I go back to the program editor, the value I entered is still there in the bottom part of the screen. So I have no idea what IoX is seeing. But the program doesn't detect the temperature going over 26 C, even though I do see it update correctly if I view the temperature sensor device node directly. So the device nodes seem to be working, but not when referenced in programs. Another quirk is if I edit the node names and reboot the controller, the default names come back. I'm testing this with IoX 6.0.0

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.

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.