DennisC

If you followed the steps correctly up to this point, then go to eisy.local, Nodes, and look for whatever you named your tag manager and select it. On the right side of the screen you should see a title for Monitor Tags and along side it a drop down arrow which you need to set to true. Afterwards, you might need to sign out and sign back in or you might need to restart the plugin. If you still have issues after doing this, then set the pg3 wireless tag log to debug and restart the plugin. After a few minutes check the log for errors.

Have you completed the instructions for setup on the configuration page: Installation Backup Your ISY in case of problems! Really, do the backup, please Go to the Polyglot Store in the UI and install WirelessTags. Add WirelessTags NodeServer in Polyglot Once it starts up, you should see a message in Polyglot Web which shows a "Active" link to click. Seems the wirelesstags certificate is not up to date, so in chrome you may have to click continue anyway (unsafe) selection :( The link points to https://www.wirelesstag.net/oauth2/authorize.aspx?... with necessary info Including a redirect back to the nodeserver's REST Server After you 'Grant' access you should see a message saying "SUCCESS, received our token, ..." in your web browser Open Admin Console (if you already had it open, then close and re-open) You should now have a node for each of your tag managers By default the "Monitor Tags" for each tag manager is turned off, if you want the tags to show up in your current ISY/nodeserver, then enable it. The nodeserver and tag manager must be on the same LAN since the tag mangaer sends updates directly to the nodeserver. Only one nodeserver can monitor the tags if you have multiple ISY/nodeserver's. This could be fixed by using Kumoapps, but not sure if it's necessary Once Monitor tags is enabled, you should see the tags be added to the ISY. Review the nodeserver log if they don't all show up, it may take a minute or so.

First, make sure you are using the correct IP address for Elk, the non secure port, the correct area number, and you have the address and port configured correctly in pg3 to match the help documentation for the plugin. If all that is good, open eisy UI and go to pg3 Dashboard, Elk plugin, Log tab. Set the log to debug and restart the plugin while watching the log entries. Do you see any errors? One other thing, only one connection can be made the the Elk at a time, so make sure you are not trying to connect to Elk with anything else (like RP2).

An alternative is to use the Notification plugin. You could use the built-in notification in UD Mobile for a limited number of notifications, or move over to the full Notification plugin and Pushover. Been doing this for a number of years now and have never had a failure.

The backup log wouldn't help with your problem. What is needed is a log package set in debug mode when the issue happens. As long as you accept the risks involved in posting potential sensitive information on the Internet, on a forum open to non-members, who could potentially create an account just to obtain that information, then by all means leave it. Most members try to help when someone posts about a problem. I apologize for trying to offer some guidance. If you only want response from the developer, send him a private message with information I stated above. He has posted before he is very busy with work and home life, but he will respond to you at some point. Best wishes resolving your issues.

First. I would suggest you remove your backup file from the forum. I'm reading this on a mobile device so can't view zip files. What is the connected state of Elk Plugin? In pg3, set the plugin log to debug and restart the ElkmPlugin. Any errors show up, does the plugin connect?

While nothing was mentioned, for the demo, it was built right in to eisy.local. We will need to wait to find out, unless @Michel Kohanim , can provide some insights? Runs on eisy and the interface is eisy ui.

The demo was very impressive.

Yesterday, I spent about an hour on Michel's Open ADR webinar. Not so much for the ADR portion, but the announcement intrigued me. Sure enough, it was time well spent. UD is expanding eisy UI to include AI AND it appears to bring plain English language to program creation, control, analyzing, and even troubleshooting. The announcement is here: Universal Deviceseisy meets AI!ai, ev, iot, matter, node server, plugin, powerwall, smartgrid, storage, teslaand ends with this: WHAT’S NEXTSoon after, we’ll have another webinar going deep into what you can do with YOUR own eisy and your configuration. Stay tuned for details. Sounds like big plans are in the works.....

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.