Morris Hansen

Upgraded without any issues

Thanks for the information. When the ISY boots up, it seems to know whether there is a PLM attached which is probably due to some communication the ISY does when first booted. Maybe if the ISY did some sort of hello message/poll to the ISY once a minute, the ISY would be able to determine communication status.

Not sure I understand needing an another power supply. Pinging the router may indicate loss of power but then the router would be down and the ISY would not have network connectivity for notifications. Would it not be possible to use the existing power supply on the ISY and plug it into a ups that would have the battery backup? Plug the router and cable modem or dsl modem into the ups as well. Plug the PLM into a non-ups outlet. With loss of power, the PLM would go down along with all other Insteon devices. The ISY and other network equipment would still be powered via the ups. The ISY would lose communication with the PLM and would just need the ability to send a notification based on this loss of communication. I would think there could be a Condition available in the "If" section in a program. Something like "PLM Communication Status is: Established or Lost" All other logic is already available to do notifications. Make any sense or am I missing something?

I am also looking for a way to detect loss of power for a remote building. I would have the ISY and other networking equipment on a UPS so I would have the ability to send emails and/or access the ISY. What is the simplest way for the ISY to detect the loss of power? It would be great if the ISY could detect loss of communication with the PLM and be able to send a notification. In this setup, the ISY would be on a UPS and the PLM would not be. I know the ISY shows safe mode when accessing the admin interface without being connected to the PLM. Being able to detect this in real time would solve this problem fairly easily. Any other forms of detecting loss of power with a contact closure connected to a IO Linc gets ugly because the ISY and PLM and IO Linc would have to be powered by the UPS during this power outage. The main concern for me is not that there was a brief power outage and what happens to programs, etc when power is restored. It is around the lost of power causes the loss of heat which could lead to frozen water pipes and property damage. Would be interested in what others have done.

Nevermind. I just remembered that my keypad in that location does not have a built in temperature sensor.

Under the Elk/Areas/All Areas section, I noticed today that one of my 4 Elk keypads is not showing the correct temperature. It shows -40. This keypad is in a different Area than the other 3. I recall something similar in an earlier release but not sure if it was resolved in 3.1.16 which is what I am running. Is this a known issue?

While I haven't tried this yet, it looks like it should work well. I am getting ready to replace both of my water heaters and will be ordering this soon. It comes with a timer but my plan would be to hook it to my Elk and let it control the water heater just like I do my HVAC systems. http://www.gaswaterheatertimer.com/index.php

I would like to see a release quickly to resolve the error log. Logs would be helpful in finding other potential issues. Maybe do a 3.1.8a release or something. Thanks for your continued support.

Also tried from a Windows Vista machine. I get the subscriber error as earlier indicated.

I upgraded without issue and I am getting the errors when trying to access the Error Log. Doing this from a Mac right now.

My system upgraded without issues a couple days ago and seemed to be working fairly well. today/tonight I used ElkRP to make some changes and then noticed that the ISY is no longer accessible via the web. This is very similar to what happened before 3.1.7. The only way I was able to recover is to reboot. I will hold off rebooting in case we need to do some troubleshooting. Anyone else having problems with their Elk and 3.1.7?

Upgraded from 3.1.6 using a Mac. Seemed to work pretty easily. Will test to see if I get Elk connectivity for more than a few hours. thanks, Morris

In the past when this happens, I was never able to access the ISY via the browser. I didn't try it this time. The only programs I have are for Fast On / Fast Off to control some scenes. 90% of my logic is in the Elk. I have emailed my error log. If you need access, I can provide that as well.

I upgraded a couple days ago without any issues. Tonight I got home and noticed my Elk was not triggering the ISY. It worked earlier today but seemed to stop. I had to reboot ISY to recover. I did not access ElkRP at all since the update. Any ideas?

I am still having issues with IP connectivity. Is anyone else having these problems? I noticed that I still have ISY programs that are working, I just can't browse to the ISY, ping it and my Elk integration is totally broken. Only comes back after a reboot of the ISY. I have verified the network side of things.

I upgraded from .15 yesterday and it seems I have a problem similar to one I had several revisions back. It seems that after the ISY is running for some period of time, I lose IP connectivity to the ISY. It works after a power off/on but then notice it will stop responding to any requests. What information is needed to help isolate this instead of just powering it off and back on? Thanks.

He has 2 devices. One is a 2476D and the other is a lamplinc. I had him reset both devices. I also had him create a link between the 2 to make sure that communications was actually working in his home. That works fine. It appears that anything involving the PLM is either not functionally or very very flakey. We did more troubleshooting and the end result was if the PLM and the lamplinc were plugged together, he was able to add the device. If he took the lamplinc down the wall to the next outlet (which doesn't mean it is on the same circuit or phase), it would stop working. At no time was he ever able to add the switchlinc. The devices do not respond at all to a SCAN PING. We thought the PLM was faulty until we had the limited success. Nothing else seems to help. We moved the AP to the same outlet as the PLM. He does have CFL's but I asked him to make sure these were all turned off. He also is not plugged into any outlet strips. All of this equipment is brand new. He talked with Smarthome tech support and they were not much help but thought maybe the PLM was faulty so they are sending him a replacement. His PLM is version 72. Thanks for your help.

Thanks. He ended up directly upgrading to 2.6.8 and it appears to have upgraded fine. As for trying to add a device, still getting the same error. The device does not respond to a SCAN PING and when using the shell to add a device it comes back with: Cannot write high water byte FF8 : 0 : device E BC 98 1 I have had him do all the standard steps, no outlet strips, plug the PLM directly to the access point, etc. This is a new network so there is only 1-2 devices he is trying.

I am helping a friend with a new Insteon install. He has a 99i that still has 1.0 firmware on it. He has one switch so far and I get "request failed" when adding the device. I am not physically in front of the equipment so I am trying to do this remotely. Can I upgrade directly to 2.6.8 from 1.0? Thanks,

My memory is not what it used to be. I reviewed what I posted before and it was accurate. My 1.75 labeled PLM is version 63. Must be a typo on the sticker. Thanks everyone for your help.

I had 2 PLM's that came at the same time. Both labeled 1.75 and with firmware version 62. It appears that others that have 2.75 have firmware version 63. Still seems odd to me and not consistent.

Thanks for sharing. I used that tool and it shows firmware version 62 for the PLM that has Rev 2.6 printed on the back. It shows version 63 for the one that has Rev 1.75 printed on the back. So it appears that version 1.75 is newer than Rev 2.6.

Is it possible to connect Hyperterminal directly to the PLM and send some command to get the version or at least when the PLM boots it would send out something?

I think this as been discussed somewhere but could not find it. Is there a way to tell other than the version number? Is there a way to poll the PLM to get the necessary information?

I have a PLM that I purchased in January that shows Rev 2.6. I just received a couple new PLM's and they are Rev 1.75. Did Smarthome change their numbering? Which one is newer and does one of them have the new capacity, etc.?