Teken

What are the hardware production date, revision, and ISY firmware of these MS units? Ideals are peaceful - History is violent

He is not seeing the low battery node show a on status. Ideals are peaceful - History is violent

That's a huge jump from 3.XX to a Beta 5.02 which has a huge change over. [emoji53] Ideals are peaceful - History is violent

On the program just right click and select copy to clip board. Then come to this post and right click and paste. I thought you meant an image from your Admin Console

Assuming its still present in the search field type in *Snipping Tool*. If its there you can launch it and it will allow you to perform a image capture.

Are you on Windows 7? Ideals are peaceful - History is violent

Understood, don't get me wrong I was never one of those people on the X-10 HA train. I knew from watching others there was lots of baby sitting and failure rates never mind a lack of reliability. My comment to you and others was purely from a technology stand point (good or bad) X-10 ushered in a period where the average Joe could have something operated remotely with very little technology back ground or programming knowledge. It was the next best thing to the clapper, no? LMAO . . .

Can you offer more back ground as to how your home is set up to use the GDO I/O Link? I see you have a KPL assigned to the unit is this case? Also, can you shed some light as to any programs / scenes have the GDO included.

I was more curious about why the log shows a query for the GDO I/O Linc: Overhead garage door-Relay Status Query Fri 2016/01/08 02:57:16 AM Program Log

I agree and the next step is to really eye ball to make sure this device is indeed NOT part of this scene at all. Is it fair to say this never happen before and this program has been active for awhile and no previous issues have been seen?

Next step is to do a visual confirmation the wires leading into the various I/O ports are properly seated and no bare wire is present. I've seen lots of installs where the bare wire was too long and some random movement caused the two adjacent wires to connect and initiate a random open / close. Don't rely on simply looking at it plugged in, wiggle the wire and see. If nothing happens unplug it and really look and pull on the wires to make sure all of them are seated and tighten down.

Go to the node in the Admin Console and select options. If its checked then yes its enabled if not at least we removed one area from concern.

Do you have trigger reverse enabled in the I/O Link?

I am not sure whether or not you're on 4.4.2 Beta firmware but it should be noted this release resolves the iMeter Solo's reset button not functioning. I would suggest you upgrade to this level of firmware and report back success / failure. You should probably hard reset the device prior to adding it back to the 994 Series Controller. Ensure you clear the Java Cache and select all option box's and down load the correct Admin Console for 4.4.2. Verify via the Help -> About that both UI / Firmware indicate the same.

Hello Mike, I believe you're in the wrong thread as this one is about the HUB II, ECHO, ISY Integration. If you're using UDI's Portal Services to connect your Amazon Echo. I think this reference thread will offer more insight and given you the opportunity to call out any unique words or phrases: http://forum.universal-devices.com/topic/17632-device-list/

Can you elaborate as to what isn't working?!?

Hello Peter, If this device is like many other Insteon products should you feel so inclined perhaps try and replace a few of the capacitors with in the unit. A few $0.50 parts may very well restore the device if not send it my way.

I posed this exact same question in one of the beta firmware releases and going off memory it was in 4.4.1. Essentially there are two types of queries which I never knew existed until I had this problem. The 3:00 AM Query (I am generalizing here) say for example checks for three things. Where as a manual query initiated by the user checks for say five things. Again, I am offering an example of what I was told and the value I indicated should not be used as a reference. But, simply as an example that there are two distinct queries in the system. So that goes back to your question a 3:00 AM Query will not in fact reset a low battery node from on to off. I know this because I've watched and documented this for more than four years. The only time the low battery node will go away completely is from a reboot or loss of power etc. This is why there are so many people asking *How do I reset the low battery node* in this forum. Clear as mud?

Larry, A 3:00 AM Query will not in fact reset a low battery node state . . .

For the record, your not bothering anyone as this is helping lots of other people down the line later . . . The code addition I added there simply repeats the e-mail message that you crafted that a motion sensor is in a low battery state. You can change that repeat value to what ever suites your personal needs. I wanted to call it out and add it in there as I recall you wanted to be reminded just in case you were not in range of cell or the e-mail got dropped etc. Having the 994 Series Controller do that hard lifting for you and repeat that condition seems to me like a good fail over, no?

Yes, but you could simply add this extra line to obtain what you had asked for before. If Status 'Outdoors / Front Door Motion-Low Bat' is On Then Repeat Every 12 hours Send Notification to 'Kent Txt' content 'Low Battery'

I believe if cost is an issue and you're mechanically inclined and have all the proper tools than the repair is a good first step. If however you wish to take your chances on another piece of hardware that has another 2 year warranty. That is a personal financial choice you need to decide on your own. Keep us in the loop regardless . . .

Is it safe to say you're talking about waaaaaaaaaaaaaaaaaaaaaay back in the day? Because if that is the case way back in the day X-10 did in fact offer the public on a very modest price point incredible power and was the first iteration of HA. I can't honestly say throwing rocks at the company who probably single handily created HA for all of us could be considered a failure. Now, if you most recently bought X-10 in 2010 onward. Well, that's on you! Ha . . .

I believe a little clarification needs to be called out for anyone else just starting to read and use Insteon products. Some people like Larry / Stu have various firmware and hardware motion sensors that apparently does not show or lock the low battery node to a on state. Where as others like LeeG and myself do . . . Regardless of what you see in the Admin Console like others have stated above. So long as you have a e-mail program set up to send you an alert you will know this condition does exist. Now, as stated above by Larry some use variables to keep a more accurate count and state of the low battery status / condition. Whereas others simply want to be notified of that fact. Everyone should just determine their use case and needs and move forward with the implementation of their preferred choice.

To your question about the battery low on status. Once you change the battery you need only right click on that low battery node and select query. That will return the on status to a off state. I am unsure why a low battery on would not be present in the admin console unless something was toggling it off or the system was rebooted which than causes all the nodes to show a blank state just something to consider. [emoji4] Ideals are peaceful - History is violent