Guy Lavoie

Does the login box say "use your IoX login name and password". If not, does it ask for your portal login (email) and password ? Just make sure you're using the right ones

Have you tried doing a factory reset and then a device restore in IoX?

You would need to create a program to detect the status change of the two switches, and turn on the light. Something like this: If icon status is On Or keypad button status is On Then Turn on switchlinc Operating the secondary switches manually has them send out the comnands due to links, but status changes caused by external commands (between the controller and secondary switches) only update them, not having them send out commands.

Let us know how it goes.

Well, it couldn't stop the isy service because it wasn't running...which corresponds to your problem. Otherwise it says it's restarting it. So try connecting again to the admin console. It it still doesn't work, you'll probably need help from UDI.

So the eisy is there. Harmless thing you can try: redo the ssh command and enter "admin" as the password. If that doesn't work, try your IoX admin password. When you get to the $ prompt, try restarting the isy service: $ sudo service isy restart You should see messages like shown below, if it restarts ok. Any error messages might give you a hint as to what might be wrong.

Ok, have you tried a connection to it with ssh? From a windows command prompt, enter: C:\ ssh admin@eisy.local Does it connect and ask you for a password?

Yes, that's how I typically capture a value from a sensor into a variable, by running a test that's always true. I'm not planning on using the high/low limit values or event triggers from the temperature sensor. That s_yolink_high_temp variable was just for testing purposes, to increment that variable by 1 every time the sensor temperature went over 26 C (I'd trigger it by holding the probe in my hand). The second way that would work here is by capturing the value in a variable and then testing against that, as I indicated in my later post. My intended use is for two things: First is to be able to ask Alexa what the pool water temperature is. This works, directly with the yolink's Alex skill (the connection to eisy isn't even needed). The second use will be to update my solar pool heating setup by capturing the water temperature to a variable, and also the temperature in the enclosure where my solar heating coils are on the roof with a second temperature sensor (I have 1200' of hose, in glass covered enclosures). Currently what I have up there is just a mechanical on/off thermostat, giving me a contact closure when it's above 80 F. In my updated version, I want to compare the water temperature against the enclosure temperature, ideally the water temperature where it exits the enclosure, and turn the valve to activate the solar heat when the water up in the enclosure exceeds the pool temperature by a certain margin.

Are you sure that the IP address you're pinging is the eisy? Do you have the IP address reserved for it in your router? If you didn't, something else might have taken the address. Check the MAC address.

This is the one you need: https://www.amazon.com/Adapter-Standard-Computer-Overclock-Quieter/dp/B0CFH98CTT/ref=sr_1_4?crid=GDYBNQPDUP61&dib=eyJ2IjoiMSJ9.sf0GiA3PTCJLEmuSfrfWLijf41NLO_8ZXideBCz6g0A0yMpO88mR1YkdoisM8Ks8J9Sezzi9lS3nGmEueOvlf8kDm27aYcMkNR_NEU1ugjT7h-Z_Xqj6TKbBI_y0vw1IDpMaRda1ZCs9N1crLIG9pr323yNfTmiDgLFSDA0mqj7qNruNr5YJBUdLsZVznsG4mii6o0LZ7jHY42eROUHMEDcrp7owd5c49pbKUy60hp8.68MO_g1RTmKvPjNM5xid_JEUoHJO4pEA9PZCFCgOzcU&dib_tag=se&keywords=mele+mini+pc+power+supply&qid=1763137625&sprefix=mele+pc+power%2Caps%2C105&sr=8-4

That must be geek mode!

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.