MrBill

On a mac your best approach is to clear the java cache, and delete any files you have named admin.jnlp or start.jnlp and then save the admin console file from your ISY... http://<IP address of ISY>/admin.jnlp There's also the launcher, but you'll have better luck with the above. From windows the better solution is the ISY Launcher.

Try sudo service isy start and let us know what it says.

Have you double checked that you downloaded the correct version of the file (PLM vs Non-PLM)?

You can watch your Event Viewer window to see what's actually happening. You can also watch the Event Viewer afer the fact to watch how many retries are occurring. that said, if you're increasing retries to 5 and your system is very large you may be creating greater traffic collision issues. The real solution to the problem is to solve the communication issue.

1) Find the IP address via the router. 2) Download and install the latest Java from https://www.java.com (it must be that java, not some other version of java). 3) try using the launcher... on Windows this step will work, on Mac you may or may not have success with launcher), to use the ISY Launcher you basically download the start.jnlp file from https://isy.universal-devices.com/start.jnlp The first time you run start.jnlp it will install an icon on your desktop called ISY Launcher which you will use going forward. 4) the next thing you should see is an ISY Finder window. Finder may or may not Find your ISY on your network. If it did click the row and pick Admin Console (cloud). If it didn't use the Add button in the finder window to add an entry in this format: http://<IP address from step 1>/desc (don't include the <>, your entry should look something like http://192.168.1.33/desc) 5) report back your issues or status and we will go from there.....

Are there lights blinking on the ISY? Or is it just the Steady Blue power light. Can you log into the AT&T router and see IP addresses that have been assigned?

We can solve that without a factory reset tho. A factory reset is going to leave him with no clue what to do next....

What type of router? internet connection? Are you saying you can't access it locally? do you know the IP address?

Is it plugged into an ethernet jack? The ISY 994 doesn't have wifi. Have you restarted it? Don't factory reset at this point.

A word of caution... read the factory reset instructions as well and understand that they are similar. Holding the button too long graduates a password reset into a full factory reset.

no idea other than what @tmorse305 mentions which is available in the PG2 store. for nodelink see this post: and this website:http://automationshack.com/wp/nodelink I think logging is a function it has, but i've never used it.

Has he changed anything with his internet connection or router? did the cable get unplugged somehow? If the answers are no and no, then the next step would be to have him reboot the ISY. Once you can get into it, the error log may have clue about why it went offline.

sort of, but not completely. Even switches coming from the factory have garbage in the memory. first thing I do with a new switch is factory reset it it to zero the link memory out and bring all the option flags to a known state. I'm not sure why you thing adding to the ISY is a magic process that rights wrongs.

Have you read the Z-wave tips and tricks post yet? It's been linked above. Most of your questions are all answered.

This usually indicates that she's trying to operate the wrong device. I'd log into the Alexa app, or actually it's even easier to do if you log into https://alexa.amazon.com and delete all the devices and scenes that exist associated with the ISY, then tell her "Alexa, discover devices" Its not as prevalent anymore, but she used to get duplicates of devices and scenes fairly easily-- one would function and one would not. The remedy was as described in the preceding sentence. The other thing is watch out for similar names she used to say "sorry living room doesn't support that" alot... Took me forever to realize that the device she was referring to was the thermostat, once the thermostat was deleted suddenly she no longer told us the living room lights didn't support that.

No updates to the product via the app stores either. Wes still logs in occasionally. I assume that development has taken a backseat because UD mobile is being actively developed.

Well I did refer you to the UDI store for the dongle, but i guess I need to LINK IT for you too. If you don't have any z-wave devices now, then buy only 700 series devices from any manufacturer. Stay away from 300/500 series for a brand new network.

nodelink is similar to node servers, but a different platform that polyglot

The PLM needs to be booted up first. it must be connected to Polisy when Polisy starts or Polisy won't detect the port. Are you having trouble starting the admin console and getting connected to Polisy? Or was it simply not responding because of the PLM issue? If you need more admin console help tell us if you are using Windows or a Mac.

he's trying to tell you to use the letter lowercase L, not a 1.... ssh -l admin 192.168.1.1.21

No, you can use your Serial 2413s PLM with polisy. You need a different cable than you've been using with your ISY994 tho. The one you need is the one that came in the box with the 2413s, maybe you kept it, maybe you pitched it. If you got rid of it, there are several threads with replacement solutions. Ordering it, or ordering an adpater from amazon. Zooz 700. UDI sells them now. Or you can get one from Amazon. Doesn't seem like it to me.

I think nodelink has a provision for the type of logging you're interested in. I haven't used it. What I do, is create a notification via the notification Node server. I send it to a separate pushover "application" that I created on the pushover website called Log. I send it with a higher priority and sound disabled. When I want to look at it i just open pushover on my phone and pick the LOG entries.

Yes, that's what he was saying.

for the fastest assistance you might just open a ticket for this: support@universal-devices.com In some cases the answer may be to delete the file, in others it may be to reload the firmware manually.

Lets contain this conversation to the already running threads in the Smarthome section of the forum. Thanks!