tome

Michel, I am using https to access the remote ISY. Then I just select "Manually Upgrade My Lighting" and select the file on my machine locally. I am completely unable to get it to complete. It gets anywhere from 3% up to 39% done and then fails with the messages above. You shouldn't! You should design the device to be remotely upgradeable reliably. I have many consumer-level devices that I update all the time remotely. Routers, weather stations, file servers, Ecobee thermostats, to name just a a few. They download their images, they verify the integrity of the downloaded file, they do the upgrade and voila. Any device today should be able to be updated remotely. Of course there are risks, but most can be mitigated. I make purchase decisions based on the capability. I will choose a remotely upgradeable product over a product that is either fixed (non-upgradeable) or only locally upgradeable. Just my $0.02.... Tom

I continue to not be able to upgrade a remote ISY-99 from my Mac. This is only if I am remote, local to the ISY it works fine. This has been going on for years now. I have many devices on my network(s) that I update regularly with nary an issue. The ISY is always a problem. Can this be fixed? This was talked about in this thread (and others): viewtopic.php?f=57&t=4379&hilit=upload+failed&start=15 Also, using CWT on the ISY to set the timeout values does not help. I have tried many values 10000 and above for both http and https to no avail. Tom These are the error messages I get:

Lee is right, it is the small load. There is only a single small strand of lights on it, perhaps 24 little leds. If i add something else to it, it comes on just fine. The funny thing is I first tried a small (5vdc output) wall wart. That causes it to flash on off at about 5-10 second intervals. I am sure the switching supply in that wall wart isn't drawing much either. I put a 12vdc output one on and it works fine. I think, however, we will find another decoration or something. Seems a shame to have to suck power for no reason, but at least we can have something festive to show for it Thanks again for the responses. Tom

Removing it from Scene8 didn't help. It just shut off again. Is it due to being too lightly loaded you think? It didn't do this last year and I think we had the same load on it... Tom

It is a very small led lit christmas tree. When the Lamplinc is off the leds are very very dimly lit. They won't go fully off. Tom

Hmm, don't see a reason as to why I have it in the scene with 14.1D.DD (which is another Lamplinc)? It is listed as a responder to that 14.1D.DD in that scene. Can you even have a Lamplinc be a responder to another Lamplinc? I don't know why it is in that scene so I am going to delete it from there and see if that fixes anything.... I updated the software several times in the last year and, most recently, just before plugging back in these Lamplincs. I wonder if something got confused between all the updates and then introducing the Lamplincs after a long absence. Thanks for everyone's help. Tom

The log above is one of the on/off events. Tom

I don't think it has an X10 address, I didn't configure one anyway, and I usually reset each device before installing it. Here is log output where I turned it on, and half a minute or so later it turns off:

I have a couple Lamplincs that I bring out during the holidays for various lights. They are 2457D2 type. One of the two keeps shutting off after a while. I am not really sure what is triggering it, I have just been turning it back on when I see it is off. I have done a restore on it a couple times. It is in three scenes and is turned on/off either manually at a Keypadlinc or by a program that just runs from sunset (on) to 11:59pm (off). How can I tell what is shutting it off? The device links table shows: The ISY links table shows: Thanks, -Tom

FWIW, I updated two ISY99s both running 2.8.16, one on my local lan the other remote, to 3.2.2 early this morning without a problem and I just updated them both to 3.2.3 again no problem. Thanks, Tom

But if /tmp is cleared on reboot then the list of devices will never be static. That is annoying. There must be a place to store something that will live through a system reboot...? Tom Ps: My friend said: "If an application needs to store persistent data, ie. that needs to be around the next time it runs regardless of reboots, it should store it in ~/Library/Application Support if it is for just that user, or /Library/Application Support if for all users. I should note that calling tmpdir is not something that should be done for persistent storage. Tmpdir, as its name suggests, is for temporary data that is typically invalidated after the application stops running and can freely be deleted by the system any time (such as reboots)."

Michel, Two things. One: Since /tmp is cleared on a reboot, shouldn't this data be put into the user's home directory somewhere? -Djava.io.tmpdir=/Users/home/tom/thingdir Two: http://www.thekua.com/atwork/2011/02/ja ... ac-jdk1-6/ Tom

Michel, Is it possible to get the java source code? I have a friend who suggests that there is a java platform independent call to get the location of a non-destructive temp directory which may be missing. He asked if I could show him the source.... Tom

Michel, There is no directory "user/temp". There is /tmp but I would hope nothing is stored there, being a temporary directory in unix after all means it is cleared at reboot. In fact, I just tested and a reboot will always remove the non local ISYs from the list Perhaps they ARE actually stored in /tmp? Tom

Sorry I meant 2.8.16. Both ISYs I have are at 2.8.16. I believe I used this url to get the Admin Console app: http://www.universal-devices.com/99i/2.8.16/admin.jnlp but as I said this has been happening for a very long time. Is there a way to debug this? Also, this may be a feature request, when I go to one of my two ISY (either local or remote) and then exit it, the app quits. Why can't it go back to the connection screen (with the list of ISYs) so that I can connect to the other one? I have to quit the one I am using, then restart the application, then select the other device, etc... Tom

I have been meaning to ask about this for a long time but it kept slipping my mind. Tonight I finally got frustrated enough about it to remember... I have a remote ISY that I log into using https://myhostname.dyndns.org:443 from the Admin Console java app on MacOS (Snow Leopard or Lion). When I put host in the list, I then have to quit the app and restart it for it to be usable. That is annoying, but not the real problem I have which is that it will stay in the list of devices for a short period of time. I don't know exactly how long it takes to disappear but just sleeping the Mac overnight and then trying to use the host the next day will sometimes reveal it is gone and I have to add it back. I am running 2.8.15, perhaps this is fixed in a new revision? This has been happening since I began using the ISY (and Admin App back at 2.7.something. Tom

Thanks Michel. Tom

I believe Trigger Reverse is specific to how the IOLinc reports on the connected sensor, i.e. my sensor to determine if my garage door is open uses this to turn ON a KPL6 key when the sensor circuit is OPEN rather than CLOSED and vice versa. I'm guessing this is what Oberkc was referring to as well. Yes, I think you must be right. I am not using the sensor in this case so Trigger Reverse has no effect (as I found). That's what I get for assuming... Tom

Lee, Thanks for this explanation, this makes perfect sense. Interesting, I thought I had tried each one by itself and I couldn't get it to work from my countdown kpl unless I had both set. From your explanation setting it on the kpl alone should have worked for me. Perhaps something else was going on. Thanks, Tom

Thanks again Lee. That fixed it! To be specific, I needed to do two things. I had to set the On Level for the I/O Linc Relay to 100% in the scene itself (called MasterBathFanControl in my case), but I ALSO had to select the Countdown KPL within the scene and also set the I/O Linc Relay to 100% there as well. It didn't work if I did one or the other, just both. Also, 100% seems to make it behave has expected (N/O is N/O until an On is sent) and 0% makes it behave backwards (N/O relay is N/C until an On is sent). Seems to me like the ISY should default to the 100% setting, but I am just happy it is working as I would expect. Thanks, -Tom

I have an I/OLinc that I want to use to trigger a remote bathroom fan. I have a Countdown KeypadLinc in the bathroom. The IOLinc has a N/C and N/O terminal and a Com. I put my meter across N/O and Com. It is open (no short), as it should be to start with. I push one of the timed countdown buttons (lets say 2 minutes), and I would expect that the N/O would shut. But it doesn't. I then push the Off button on the countdown timer and the IOLinc fires (now N/O is closed). Now when I push timed button it opens again - hmm seems backwards. Ok, I could live with that and just wire my fan across the N/C contact and Com. But let's just say I am picky... So, I go into the settings for the IOLinc-Relay and set Trigger Reverse. I am also in Continuous Latching as I want it to stay latched until the timer expires and sends an Off. Trigger Reverse seems obvious, yes? But it doesn't work. I get the same behavior as above. Ok, I say, I must have a bad IOLinc. So I try another (I bought this setup for two bathrooms), same behavior. What am I missing here? Tom

What does this message mean? I was about to configure my IO/Lincs when this came up, but it could be that the Admin Console app had just come up and it is not associated with the IO/Lincs specifically.... SSL-Insteon.tiff

Thanks Lee. I punted for this circuit and moved the IO/Lincs to a different one to configure them. Ultimately they will be on yet another circuit so I will wait until I get them there and see how they behave. Debugging the one that was working a week ago and now isn't will be a PIA so I will wait to do it when I need something there. Tom

Thanks Lee. Why would this have changed between the old PLM and the new? Nothing was added/removed from the power line between having linked the IO/Lincs to the old PLM and then installing the new PLM. The only change is that the ISY is now powered through a separate wall wart which is plugged into a UPS vs having been getting power directly from the old PLM. Could that cause a problem? Tom ps: I should also add, that I just went through all of my other devices connected to the network and they all work MUCH better with the new PLM vs the old in terms of reliability (always seem to fire) and speed (seem to come on/off quicker). Now I am really baffled.

I updated my PLM to a new dual band version (2413S). I had two I/O Lincs that had been linked to the old PLM but not yet used. I couldn't communicate with the I/O Lincs after the upgrade for no apparent reason. So, I removed them from the ISY. I can no longer link with them. I am running 2.8.16 and when I go to Link Management -> Start Linking, nothing happens when I push the button on either I/O Linc. Also, I cannot add them by address. Not really sure where to go from here... Tom ps: here is output from event viewer while trying to link one of the OILincs: Wed 08/17/2011 07:10:45 PM : [LNK-BGN ] 02 64 01 00 06 Wed 08/17/2011 07:11:22 PM : ---- Initializing the linked devices ---- Wed 08/17/2011 07:11:22 PM : ---- All Linked Devices are now initialized ---- Wed 08/17/2011 07:11:22 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Wed 08/17/2011 07:11:22 PM : [All ] Writing 51 bytes to devices Wed 08/17/2011 07:11:22 PM : [F 52 86 1 ] Using engine version i1 for 'BathroomFan-MBR' Wed 08/17/2011 07:11:22 PM : [F 52 86 1 ] Link 3 : 0FE0 [E2031971B8000003] Writing [E2031971B8000003] Wed 08/17/2011 07:11:22 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:23 PM : [iNST-SRX ] 02 50 0F.52.86 19.71.B8 23 28 0F SET-MSB(0F) Wed 08/17/2011 07:11:23 PM : [standard-Direct Ack][0F.52.86-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Wed 08/17/2011 07:11:23 PM : [iNST-ACK ] 02 62 0F.52.86 0F 2B E0 06 PEEK (E0) Wed 08/17/2011 07:11:33 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:42 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:46 PM : [F 52 86 1 ] Link 3 : 0FE0 [E2031971B8000003] *Failed Writing [E2031971B8000003] Wed 08/17/2011 07:11:46 PM : ---- Initializing the linked devices ---- Wed 08/17/2011 07:11:46 PM : ---- All Linked Devices are now initialized ---- Wed 08/17/2011 07:11:46 PM : [All ] Writing 51 bytes to devices Wed 08/17/2011 07:11:46 PM : [F 52 86 1 ] Using engine version i1 for 'BathroomFan-MBR Wed 08/17/2011 07:11:46 PM : [F 52 86 1 ] Link 3 : 0FE0 [E2031971B8000003] Writing [E2031971B8000003] Wed 08/17/2011 07:11:46 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:46 PM : [iNST-SRX ] 02 50 0F.52.86 19.71.B8 27 28 0F SET-MSB(0F) Wed 08/17/2011 07:11:46 PM : [standard-Direct Ack][0F.52.86-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Wed 08/17/2011 07:11:46 PM : [iNST-ACK ] 02 62 0F.52.86 0F 2B E0 06 PEEK (E0) Wed 08/17/2011 07:11:48 PM : [iNST-SRX ] 02 50 0F.52.86 19.71.B8 23 2B E2 PEEK (E2) Wed 08/17/2011 07:11:48 PM : [standard-Direct Ack][0F.52.86-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Wed 08/17/2011 07:11:48 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:57 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:11:59 PM : [iNST-SRX ] 02 50 0F.52.86 19.71.B8 27 28 0F SET-MSB(0F) Wed 08/17/2011 07:11:59 PM : [standard-Direct Ack][0F.52.86-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Wed 08/17/2011 07:11:59 PM : [iNST-ACK ] 02 62 0F.52.86 0F 2B E1 06 PEEK (E1) Wed 08/17/2011 07:12:08 PM : [iNST-ACK ] 02 62 0F.52.86 0F 28 0F 06 SET-MSB(0F) Wed 08/17/2011 07:12:12 PM : [F 52 86 1 ] Link 3 : 0FE0 [E2031971B8000003] *Failed Writing [E2031971B8000003]