MrBill

Reading this thread from the top makes me wonder if the SD card might have died.

related: essentially you can proceed as bumbershoot suggested, or you need to create a 'message', either email or Network Resource with each users friendly name. then a program for each different notification. The ISY doesn't store strings as variables.

I read it to mean the ISY Event log... nodeservers do dramatically increase event log entries being written to the SD card. I recently adjusted some of my nodeservers and eliminated a couple that weren't really being used for automatons. My event log was recycling 64000 rows about every 20 hours, with my changes the log now recycles in just over 48 hours. On the topic of micro SD cards, I think the answer is just have a replacement on hand, and don't buy cheap off brands, and look for the newer A1 rating.

I'd just take the batteries out, they will appear "out of range", then you can disable any programs that use them. At the start of the cold season replace the batteries and re-enable any programs you have that reference them. Less to re-do.

I just turned off a bunch of tags because I upgraded them for more battery life. After you unpair the tags via the phone app or https://my.wirelesstag.net/eth/ then 1) first close the admin console (if it's open), then 2) on POLISY, go to Dashboard, Wireless tags, click the DETAILS button, then the Nodes Button, scroll down and find the tags you deleted and click the delete button on the far right of the line. (note you have to click "Details" button, before the "Nodes" button--even tho you can see the "Nodes" button 1 screen sooner) With the node deleted, you can now re-open the admin console and it will be gone. Another approach is just change the update interval on those 5 tags to "every 4 hours" which appears to the be the maximum and leave them paired. --- I'll tag @Jimbo since he wrote the nodeserver to see if he has anything to add.

open a ticket with UDI, email support@universal-devices.com

there was a bug where the log didn't display in the GUI. Try to check for Polisy updates and then update, then reboot again. my version is 2.2.13 and I have logs again.

Here is a link to UDI's direct store: https://www.universal-devices.com/store/ I suspect that if "it's not always happy" you need to do some troubleshooting. Could be lots of issues from communications, to poorly written programs, to network errors. We can generally help figure things out but we need a bit more information to get started. tell us what the issues are.

Last nights release to 0.0.9 is amazing. I worked with it for a little while the morning and the addition of favorites is my favorite so far!

The box on the first tab is greyed out because it's not just a tickbox anymore. if you click change location there is now a dropdown at the bottom of the page.

I like it, no one will see it tho ???

Don't forget to use the Invisible Bold Red ink !! ??

If the blue light is next to Port A it's part of the 300 series Z-wave board. the 300 series board is only compatible up to and including ISY firmware version 5.0.16C. For all firmware after that version you need a 500 series board. See this link for more info on special pricing if you need to upgrade. You may need to have the device closer to pair, there may also be a need for establishing repeaters.... if you're new to z-wave we should get @lilyoyo1 to link his post on creating z-wave networks.

It's chris's fault... he used that invisible bold red ink.

You have a series 300 z-wave board. The first lines of the first post of this thread state: its fairly simple to upgrade the z-wave board. see here for special pricing: https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions If you do not upgrade the hardware you will need to stay on version 5.0.16C and not upgrade further.

Does your ISY have a BLUE LED on the back next to Port A (shine the flashlight on your phone on it if it's not lit).. If so it means you have a 300 series z-wave board and 5.0.16C is the highest version you can use. What version where you coming from when you got in trouble.

if you haven't opened a ticket yet email support@universal-devices.com

@Tedsan if you do have the blue light series 300 board that reports z-wave version 4.55 as mentioned by @DennisC then you should roll back to version 5.0.16c, that is the highest version number of ISY firmware that will work with series 300 z-wave boards.

did you add any programs to the ISY? If so please paste those also.

Duplicate thread: lets keep all the responses in the other one:

Good to know that it worked out for you. Let us know if you have more questions.

Not on topic for this forum, but the answer can only be found in the manufacturer's documentation. Some coils might be rated for continuous duty while others may only be made for intermittent use. Generally with door strike the models that are meant for continuous duty are quiet. If they are noisy (buzz) they likely are not for continuous duty.

that sounds more like a scene issue than an Alexa issue. Alexa uses the root scene configuration. what happens if you try to turn the scene on using the on button at the bottom of the admin console?

After you made changes in the portal, did you say "Alexa, discover devices"? Also she doesn't always deal with things that have duplicate names correctly. If you have duplicate names then delete both, and tell her to discover devices again. Also I find it easier to find duplicates by using a full web browser via laptop and logging into https://alexa.amazon.com if none of those help I'm out of suggestions.

yep... I use an ubiquiti ER-12 currently. I started with an ER-X but needed an upgrade when I switched the primary connection to 1gig. As I mentioned above Re: the tp-link I was needing a dual wan router, I use a second LTE modem as backup. The edgerouter line is solid, the DHCP and Routing tables with both take whatever you can throw at them (unlike consumer routers that have limited size in for both tables). Much like a certain automation controller we all love they have V1 firmware and V2 firmware... v2 was beta and had issues for years. I stuck with v1 which they may have now stopped updating (last v1 firmware was 1 year ago), I'm still resistant to moving to V2 tho. There is a learning curve. It's not exactly plug and play like consumer all-in-one units. Your wireless AP's are separate entities. There is a GUI, but several things are left out of it, or harder to configure, so you will likely learn to use the CLI. It's basically a dedicated version of debian linux with router software built-in. I added a couple of scripts so that the ISY could keep track of minutes per month that the primary WAN was down, and set it up to send me Pushover notifications when it switches between the primary WAN and Failover WAN. I haven't rebooted the router in 323 days.... It's rock solid.