Jump to content

drw

Members
  • Posts

    81
  • Joined

  • Last visited

drw's Achievements

New

New (2/6)

0

Reputation

  1. Good news is that the temperature reading returned overnight. Now reading 68 deg. I do have a routine that sets the time on the thermostat (using 'synchronize clock' command). This might have restarted the temperature readings. The remote thermostat is not reporting temperature but that is not a problem since it is a slave unit. Smokegrub, agreed that cycling power would fix the problem...this would require cycling the power to the furnace which provides the 24v power to the thermostat. But I am not able to do that remotely.
  2. I have a 2441TH thermostat which is reporting temperature 0...after a power failure. The thermostat seems to be working normally otherwise..as reported by the ISY. This thermostat has been working correctly for several years...and it has a slave 2441ZTH which is also not reporting temperature. I am running v4.5.4 of the ISY software...this software has been running correctly for some time. Is there any way to remotely reset the thermostat to get the proper temperature reading? I am not able to do a reset/power-off of the thermostat in person.
  3. Thank you for your help. I had checked the cable between the ISY and PLM and it seemed fine. I re-powered the ISY and PLM in your specified order. No change. The PLM link count was 0...no links were shown. I did a restore PLM. This is somewhat of a job because I have more than 15 wireless devices - some in difficult places to reach for putting them in program mode. After doing the PLM restore, I had 340 links. The system seems to be working normally...status of wireless devices is now registering at the PLM. I have ordered another spare PLM.
  4. I replaced the PLM with a new one marked v2.2 1629 in early November. Everything worked correctly until today. Wireless insteon devices (mostly door open/close 2421 triggerlinc) cannot report their status to the ISY. I have reset the power to the PLM/ISY several times. On one occasion I received the message "ISY is in safe mode...not communicating with the PLM"...after another power reset the ISY and PLM seem to be communicating...but wireless device status is not available to the ISY. Is my PLM failing? (again)?
  5. Is there a way to force a 'default' state for a triggerlinc after a power fail? A triggerlinc shows a 'blank' state at the ISY after a power fail. I understand that the ISY cannot query the triggerlinc (to save power at the triggerlinc). I have triggerlincs on entry doors and would like for them to default to closed after a power fail.
  6. I have also discovered that my (wireless) mini-remotes have quit working....putting them in programming mode and doing a restore...seemed to fix them. And my motion sensors (wireless) have quit reporting. This is more wireless devices that have quit reporting their status changes. I assume the date code 1425...means 2014 and week 25. I thought more recent PLM units had the problem 'fixed' by using higher rated capacitors
  7. It's a 2413S, rev2.0, 1425 (date code?). Green led is lit. I understand that wireless devices save power by transmitting only when there is a state change (something to report). But why would all of the wireless devices stop working at the same time? There are over a dozen of them, they can't all be bad simultaneously. I have lots of Insteon dual band devices so the wireless network is probably good. The PLM is the common point of failure. It's like the PLM 'forgot' all of the wireless devices - a restore of a wireless device caused it to report to the ISY normally. This has all been working for some time (years) and nothing has changed recently....well I take that back...I recently (2 weeks ago) updated the ISY to v4.5.1 firmware from v4.3.26.
  8. I have a number of triggerlinc (2421 v4.0) devices. They have worked correctly for some time. This morning none of them were able to communicate with the PLM (running v4.5.1). Requesting a 'query' of a device gives no result. I have many other devices (switchlincs, keypadlincs, appliancelincs, access points) that seem to be working okay. I did put one of my triggerlincs into programming mode and did a restore. The triggerlinc started working normally and was able to communicate with the PLM. This is a short term solution but some of my wireless devices are water sensors located in the crawl space (and difficult to access). I would like to understand how to fix this problem permanently. Could this be a PLM going bad?
  9. drw

    cannot backup ISY

    I have found the solution. Go to Safari/Preferences/Security/Internet Plug-ins/Website Settings For Java/IP-address-ISY select "run un-trusted" Close all the windows and Safari. Re-open the admin console and the backup should be able to be done normally. I have done this setting before, but it must have been lost in an OS X update.
  10. drw

    cannot backup ISY

    I am running 4.2.18 (latest official release) on a Mac (OS X 10.10.3 latest) using Safari. I also recently (a few days ago) did a Java update to version 8 update 45. I make small changes to my programs from time to time and do a "backup ISY" each time. This morning I have done a small programming change but cannot do a backup. I see an incomplete open file dialog box, choose the Documents folder. I receive a message "cannot create zip file". I did do a complete delete of all Java temporary files after the recent Java update.
  11. drw

    ISY-994 Hangs

    LeeG, No RX light on. The first occasion (after being locked-up for several days) the Power LED was on - no other LEDs lit. The second occasion (several weeks later), Power LED was constantly lit, the Error and Memory LEDs were blinking. I've had a few other lock-ups since then, but did not note the LED states.
  12. drw

    ISY-994 Hangs

    I've had a similar problem. viewtopic.php?f=27&t=12794&p=106356#p106356 I've had several more occurrences of the lock-up since then. It is believed to be some kind of buffer overflow when the ISY is flooded with some kind of UPNP (universal plug-n-play) packets transmitted with some media servers. (I don't think I have any "media servers" but I do have media devices.) I put my ISY power supply on an external household timer (shutting the power off for 1 minute every night) - that is a temporary solution. My home was left with lights on for several days when one of the failures occurred because I could not get control of the ISY. I would really like to avoid having lights on for days on end - it doesn't enhance security. It has been pointed out that the external timer covers up the solution of the problem. I have removed the timer and a couple of lock-ups have happened. I am very interested in solving this problem and would cooperate with any experiments/reports that would be needed by universal-devices support.
  13. drw

    ISY 994 failure?

    Michel, I will be happy to participate in any observations/experiments that you need to identify this problem. I have taken my ISY off the timer so it will be running continuously. I assume assume you will want error logs immediately after a "freeze-up". Please let me know any other information that you need. As I mentioned earlier, I recently changed from AT&T DSL service to Uverse service. I have no TV service from Uverse. I did have to change my modem/router to an AT&T provided 2wire 3600 HGV. I do not use the routing capability of this router - I continue to use my Asus router (which I have used for some time). The 2wire router does not appear to support UPnP - I can find no settings for it - and various forums seem to indicate that there is no UPnP support. The first "freeze" occurred around Thanksgiving time before I changed internet providers - so perhaps the change is not a factor. Also, I do have various "media" devices but I don't think they are media servers that would be emitting UPnP packets.
  14. drw

    ISY 994 failure?

    For the second time, my ISY 994i quit working a few days ago. It was not issuing Insteon commands and was unresponsive on the IP-side - I could not login to the admin console. Powering the ISY off and then on revived the system. After the first occurrence, I changed the firmware to 4.1.0 as suggested. It is my understanding that some kind of media-server packets could possibly flood the ISY and cause the lockup. Version 4.1.0 fixes this? I am not entirely sure that I have any "media-server" type devices. I have several media-consuming devices...AppleTV...Panasonic TV...blu-ray player. I do have a Silicon-dust network HDTV tuner which can send an HDTV stream out to a client (media server?). The only device that could be considered a "media-server" would be an Iomega NAS but the media capabilities are turned-off. I have no DirecTV equipment and I am not on Verizon FIOS. My ISP is AT&T Uverse. The problem roughly corresponds with a change to Uverse. I do not have Uverse TV service...I have the 2wire 3600HGV gateway. I don't use the router in the gateway...I am continuing to use my Asus RT-66AC router that I have used for some time. As mentioned in a previous post...I have put the ISY on an external household timer that cycles the power every night...this gets the ISY working again. I would like to fix this problem because the nightly reboots cause me to lose variable storage. I have some furnace running values stored in variables and would like to be able to see them over a longer term than one day. Is my ISY intermittent? Should I consider a replacement? Are there any error logs that I should consult?
  15. I believe that I have found a way around this problem by using scenes. Set up a scene containing the "thermo main". Configure it the way I want the thermostat to be set- all the settings are available. By turning the scene "on" the thermostat seems to be reliably set into the modes I want.
×
×
  • Create New...