oberkc

Do we have a level of confidence that the YoLink node server works with the new hub?

I thought that UD Mobile could be used without the portal. If used inside the house, on the same wifi network, I did not think it was any more difficult than adding the internal IP address for the ISY in http: settings. Maybe things have changed?

I get up there a couple of times each year. Unfortunately, I am stupid and do things backwards. I go south in the summer and north in the winter. We like the good snow at Boyne Highlands.

"Control on" is triggered any time on is received, but not triggered on off/dim/bright/etc. If a device (motion sensor in this case) is already on, a control condition will still trigger a program evaluation even though no change in status occurred. An off command will not trigger a program execution. A control condition is true only during that point when the expected condition is received. "Control on" is false at all other times. "Status on" is triggered by ANY change in status, and is true at all times when the status is on. If the device is currently on and it transmits another "on" command, a status condition will not trigger since it is not a change in status. Use of control versus status is based upon the desired logical result.

If your desire and intent is to ise insteon swithes, I know of no options other than to rely on the wireless communication of insteon. It may require some strategic placement of something like a couple of range extenders or similar type devices. I do not recall that there is a way to link multiple PLMs or multiple ISYs together.

What kinds of devices do you want o control in your shop? What do you use in the house? (Insteon? Zwave? Zigbee? Matter? Other?)

While not a complete answer, most such devices I have tried retain their settings when unpowered, so I just plug them into an insteon or zwave module and control power only.

When you “hit” the new scene, did you mean turn it “on”? What is “existing keypad” and why did you expect it to urn off? If I may speculate, perhaps you are relying onutually exclusive relationships. Be aware that mutually exclusive relationships are only enforced when keypad buttons are controlled directly. If controlled via a scene they will not be enforced. If you want a device (such as a keypad button) to turn off in response to turning ON a scene, you must incude that device in the scene and set the responder level to zero.

Secondary buttons on a keypad cannot be controlled directly. If you want the ability to turn on/off a single button (not the load-controller) you must first put the button into a scene, thn control the scene in mobilinc. (This is not unique to Mobilinc…it is the nature of keypadlincs.)

I have given up on the current iteration of matter over thread. It does not work for me.

I am unsure whether your intention is to use the PLM from the vacation home or the former main home. If from the main home, I would be extremely tempted to perform a factory reset before installing it in the new location. I would be almost as tempted to do the same on the EISY, except for the portal license. The license, of course, can be added back but would require some effort with Universal Devices.

Where do you live? You might get lucky an be close. to someone who can help. I am not sure whether I am remembering correctly, but the app software that you eventually must load to your computer might be dependent on the firmware version on the ISY994. There may be someone around here that remembers how to access via a terminal window and detrmine the firmware version. Is your ISY connected to your network via ethernet cable? Are you able to identify the IP address associated with the ISY? Did the previous owner provide login credentials (may be set to default)? Ultimately, you may end up here to downlaod the launcher for your ISY994 (it claims to be for all firmware versions): https://www.universal-devices.com/resources/#isy

Yes, weird. It is hard to understand how the program is different before you made changes to the "dimming and timing".

Interesting. I have had a couple of LG TVs and I thought they also had the ability to disable the CEC feature, or whatever they call it.

I think the parentheses comments are a possible issue, but not the cause of your lights coming on at sunset, and sunrise. Your progrm will run the ELSE path any time the program is triggered (sunrise, sunset, switches controlled on) but evaluates false. Your program will always run ELSE path at sunrise and sunset, because it will always be false at those two trigger points. When that happens, the master am scene will turn on. I understand that you may want to accomplish your goals in a single program, but this may not be possible.

Thanks for doing this.

I have no need for the beta until the hub is available.

A little clarification might be needed. I understand that you can log into the portal, go to ISY web access, and see/control the lock. However, when you go to the portal and then to the connectivity>google home, the lock does not show up as an available device to expose to google home. Is this essentially correct? I can confirm that my Schlage zwave lock shows up in the portal/connectivity which suggests (in my mind) that it is not a zwave issue. I wish I could offer a solution to this, but the only thing that is coming to mind is that something has become out of sync and that a reboot of the EISY or portal might help.

I sure do. I sense that you are a bit more ahead of me. I am almost certain that google would not have controlled it. When I originally did this, I did NOT have a thread-capable nest hub. Since that time, I have added a gen2 hub which has thread. I have since reset the bulb and added to the new nest hub and shared with Alexa (also worked without any problem that I could recognize). I have since reset the bulb several other times. Will do, but it will be a week. Heading to Utah for some skiing.

Yes. I shared it from the Alexa to the google home app. I do not recall any errors. I do not recall any mention of a thread network, but this may be my failure to recall. When I originally added it to Alexa, I did not, and still do not, have the nano leaf app. Perhaps that is a variable I should play around with.

I have the echo hub and have successfully added the nanoleaf bulb as well to alexa. I could also share it with a google nest and control the bulb from either device. I have also originally added the nanoleaf to the google hub and shared it with the alexa devices. In all the various combinations I have tried, the nanoleaf would loose connection eventually, sometime reconnecting, sometimes not.

For a standard (matter) that purports to be universal, why would there be? Why would there need to be? There was not setup or configuration information regarding "works with Alexa" or "works with google", either. Are they going to prove the comic to be prescient?

Yes. Agreed. I even tried a few variations. I reset the nano leaf bulb and tried adding directly to UD Mobile (android). No luck. I reset the bulb, moved it closer to the nest hub (gen 2) and added back to google home. I then shared the bulb from the google home app (android tablet) to UD Mobile (also android). No luck. I have tried variations of this using iOS devices with similar lack of success.

Well...just tried adding a couple of matter devices. One is a Cync bulb and wifi. The other is a nonoleaf bulb and thread. Both were prior added to google home and shared with apple (but not yet amazon). I now shared both via a qr code from google home. Both appeared to add (certainly got no errors). The thread device is taking a relative long time and is adding as I type this. Edit: and I come back after 5 hours of "adding" the thread device and find that it has not added and is stuck on the screen saying "adding matter device". The matter wifi device added fine. I may try some different approaches soon.

OK. I will assume that the upgrade took hold and will try some matter devices soon.