Michel Kohanim

Hi Barry, You can use /rest/subscriptions for a list of subscriptions. If you have a subscription ID then you should be able to find it. This said, however, there's no list that shows the IP address of the subscriber. You can also use IsSubscribed service to see whether or not a subscription ID is subscribed. Yes, all subscriptions are lost after reboot. With kind regards, Michel

Hi RichTJ99, No, I would not do that. Now that you are back to some normalcy, I do recommend calling the tech support to figure out the next steps. I would only restore devices that are not communicating but, even then, we need to first make sure that you can communicate with them. With kind regards, Michel

Hi trevorst, This is how ISY works: 1. You subscribe using REUSE_SOCKET, ISY keeps the socket open 2. ISY sends a heartbeat event every 120 seconds (you should look for these) 3. If the device does not ACK (TCP level) the event, then ISY tries 2 more times 4. If still no response from the device, then ISY assumes the device is gone and expires the subscription I suspect your iPad might be going to sleep and network connectivity is lost. What I suggest is: look for heartbeat signals, if the next heartbeat message is not received within the max-age duration, then assume that ISY is no longer considering you subscribed. In this case, you should subscribe again. All this said, the main question is why the device is not sending an ACK? With kind regards, Michel

Hi ravedog, Those that show two states (incorrectly) are scenes and not devices. With kind regards, Michel

Hi mbrossart, If you are not next to the beach, then use interior. It is used for calculating the amount of evaporation: /* * BaroAbsolute - Mean site barometric pressure In kPa * http://cagesun.nmsu.edu/~zsamani/papers/net_radiation_paper.pdf * KR = KRA * (Pressure/(101.3))^0.5 * KRA: * Empirical coeff: * 0.17 for interior regions * 0.20 for coastal regions */ region*sqrt(BaroAbsolute/101.3); With kind regards,Michel

Hello Carey737, Please look at the end of the events: Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Cannot determine device type Sat 08/23/2014 11:53:01 AM : [20 8B C4 0 ] Failed to add device It seems that ISY cannot determine the device type. There are two cases: ISY does not understand the type (it's old) or that the device is not returning a type that ISY understands. I suspect it's the 3.3.10 firmware. With kind regards, Michel

Hi ccclapp, That's the advantage! i.e. you know for a fact that when the next zone is called, the previous turns off. Very much like regular sprinkler controllers. With kind regards, Michel

Hi Techman, Query would not return anything (battery operated). It should only clear the state of those nodes. With kind regards, Michel

Hi DWalker, I am concerned that this won't work if you call Cycle Complete at the end of each program. Cycle complete should be called at the end when ALL programs have been run (Then path). With kind regards, Michel

Hi ScottAvery, I strongly recommend moving your PLM to a different outlet and retry. With kind regards, Michel

Hi Rich, I really do not think the issue is the PLM or ISY. Do you get any communication errors? Restoring PLM only should not take more than 10-15 minutes (the restore only changes PLM records in devices and nothing else). Restoring Devices may take hours depending on the number of devices you have and whether or not you have turned off the battery operated button. Again, the main question is whether or not you get any comm errors. With kind regards, Michel

Hi Rich, This is definitely not normal. What do you see in the event viewer? Any traffic? Do you get any comm. errors. With kind regards, Michel

Hello DWalker, thanks so very much for the details. When do you do Cycle complete? With kind regards, Michel

Hello osurh18, I think it would be best to contact support (links below). File extension is .zip and usually something like ISY-Backup-xxxx.zip where xxxx is the date. With kind regards, Michel

Hi Rich, PLM restore should not take that long even if you have 1000s of devices. I very much suspect the issue being communication issue. Has anything changed in your electrical system? Did you try moving the PLM to a different outlet? With kind regards, Michel

Hello osurh18, I am so very sorry. Please try http://isy.universal-devices.com/99i . (note the isy.). With kind regards, MIchel

Hello ccclap, Yes, correct. You can have multiple outputs on at the same time (outside of a scene) with EZIO. You cannot do that with EZFlora. With kind regards, Michel

Hi Mike, I am so very sorry to hear. Is this a 99 or 994. If 994, please upgrade to 4.2.8. With kind regards, Michel

Hi RichTJ99, Please try moving the PLM to a different outlet. Have you contacted our support? With kind regards, Michel

Hi DWalker, 1. Yes, irrigation module works properly but you may have too large of a irrigation requirement after two days 2. In the same cycle? If not, yes, certainly. Please note that irrigation requirements get updated if and only if: - You issue Cycle Complete ... - Amount of rain at the end of day ... So, you may want to do Cycle Complete only after you are done with the rest of the zones (not just sprinklers). With kind regards, Michel

Thanks Teken. This is what I want you to do: 1. Tools | Clear Error Log 2. telnet to ISY (open a terminal window and type "telnet isy's.ip.address", log in using your credentials. At the prompt, type DON followed by enter 3. Clear your Java cache: http://www.java.com/en/download/help/plugin_cache.xml 4. Delete ALL bookmarks to ISY's remote IP address. For this test, you can NOT use the remote IP address of ISY 5. Go to http://isy.universal-devices.com/994i/4.2.8/admin.jnlp ... this will install an icon on your desktop and brings up the Admin Console. If it does not, click on the Add button and enter http://your.isy's.ip.address. This icon is the one that you MUST use for this test and NO other methods 6. Wait for the Admin Console to hang. Once hung, either write down the error messages or screenshots PLUS what you were trying to do at that time 7. Restart the Admin Console 8. Go to Tools | Error Log and save it 9. Send me both the error log (# AND whatever you have created in #6 to support@universal-devices.com Thank you. With kind regards, Michel

Thanks Teken, Anything else? With kind regards, Michel

Thank you. Anything other errors above and beyond: Socket Open Failed java net Socket time out exception, XML Parse Error Proxy Device Process Event, With kind regards, Michel

Teken, I have already gone through the certificate popup reason with you on the phone. I am sorry if you don't like the answer but that's what it is. At the moment, ALL I need from you is the contents of the "nagging" errors you get. NOTHING else please please please please. With kind regards, Michel

Teken, Let's start with the 30%. Please let me know exactly what "... the never ending JAVA pop ups in various nag prompts appear" are. I do not need screenshots. I just need the errors you are getting. As far as ISY taking down GEM and Dashbox, well, that's pretty hard to digest. It might be the other way around as ISY does not send anything to GEM and Dashbox. Xathros, if ISY runs out of network buffers, you will see them in the error log. The last time I checked Teken's error logs they were pretty clean except for a few instances of queues being full (which points to infinite loop in programs). This said, the fact that restarting UI fixes the issue 70% of the time makes me suspect the network. With kind regards, Michel