DennisC

While I don't use this sensor, I use other Yolink devices and have been pleased with them. I have had occasion to use their customer support and that has been good. They have even replaced a device outside of warranty that wasn't working like it should have been. There is a plugin for Yolink that works well and has excellent support. Take a look at this device and you would need one of there hubs: https://www.amazon.com/YOLINK-LoRa-Smart-Window-Sensor/dp/B085HTMGYV

I noticed you mentioned trying a reset. If zwave sensors, you may need to do an exclude, before including to get them to add correctly. Have you tried that?

Of late, the whole upgrade notification method currently in use by UD, is less than ideal. Besides the issue with UD Mobile notifying you daily about an upgrade, the upgrade notice in eisy, eisy.local/system/upgrade, just doesn't work. It rarely shows upgrade available when there is one. Case in point, I waited for two weeks when others on the forum indicate that the latest firmware was available before I upgraded. The upgrade status page in eisy never showed it was available. It was much better when staff made a post in the forum that and upgrade was available and gave some details about what changed.

UD is moving to single sign on solution across all of their platforms. That's why we are seeing logins with portal credentials. Using port 3000 is a local login. When eisy.local, UD Mobile, or pg3 is signed in with a local account, certain plugins stop (because they are using portal credentials) and then restart ( so they are visible with local credentials). I don't recall the list of plugins this impacts off hand, but I know one of them is Elk. There have been several posts in the forum from members complaining about plugins stopping and restarting.

Out of an abondance or curiosity, does https://eisy.local open eisy UI? Note: If you previously used port :3000, make sure it is NOT at the end of https://eisy.local before hitting enter. Sometimes browser cache comes in to play and you do not want to start eisy UI using port 3000.

My explanation might have been an over implication. From Wikipedia: Multicast DNS (mDNS) is a computer networking protocol that resolves hostnames to IP addresses within small networks that do not include a local name server. t is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name System (DNS). It was designed to work as either a stand-alone protocol or compatible with standard DNS servers. When an mDNS client needs to resolve a hostname, it sends an IP multicast query message that asks the host having that name to identify itself. That target machine then multicasts a message that includes its IP address. All machines in that subnet can then use that information to update their mDNS caches.

I understand what you are saying. But, reinforcing my previous disclosure about not being a network guy, I don't think eisy.local relies on DNS. I "think" eisy advertises itself on your local network using mDNS (Multicast DNS). It is not a "real IP address". It is just yelling out "is there anybody called eisy.local" and eisy replies. I also don't think its the same setup as IoX Launcher.

Have you tried it? I'm not a network guy, so I am sure others would be able to explain it better then I could. But I thought eisy broadcasted it's name across the network. Oh, all routers I have had in last 10 years had DNS built-in. Just use the router address if needed.

Glad you got it working. I will offer up one more suggestion, for what it's worth. If I was in your situation, I would create one or more programs, including devices that make sense for your layout, either having no IF statement, or having a time based IF statement. For the THEN portion of the program, have the listed lights turn off. Next, I would leave the program disabled and when needed, either just run the THEN statement from UD Mobile, or if time based, enable the program. You could take it further and have the time based program set back to disable after running. If you end up with more than 1 program you could use 1 program to run a bunch of them. Doing this from UD Mobile it becomes much wiser then looking for lights or devices that are still on and turning off individually. Oh, it won't hurt anything to turn off a device that is already off.

The best way I know to see at a glance what is on and what is off it to create a favorites page with a folder for lights. Create tiles for the lights you want to monitor and then add Advance Status Configuration and a formula to change the icon color when the light is on. This will stand out and let you see quickly what is on. I would think the bigger question is why or how are you needing to review what lights are on? If you have lights on that shouldn't be or you don't want to be on, why? If it is the result of programming not working or something else, maybe that need to be addressed?

Well, that's why I asked the question. Is that the button he is holding or is he doing something different? If he is doing it correctly, it's odd that it's not working for him. Any time I have tried, I never had an issue.

For starters, what device device are you attempting to reset the login on? When you say physical button, what button are you referring to?

If you haven't run upgrade packages in awhile, try doing that. There was a recent version that caused some issues with certain plugins. It's best to get to at least v6.4.

If you are already on at lease v6.0, UD has suggested in other posts to do further upgrades from eisy.local.

Yes, from the menu you can select what is wanted. In the menu do you have a Home tab? You can click on Home and add what you want to the main page - sorta like favorites. There should be a gear icon in upper right that lets you modify the page.