Teken
-
Posts
10601 -
Joined
-
Last visited
Everything posted by Teken
-
RK, Since you already did a delete and add you can try these last two things. 1. Do a device restore 2. Delete the device from the controller. Factory reset the device per the users manual. Than add it back and let us know what happens.
-
Reboot the ISY Series Controller. Sent from my iPhone using Tapatalk
-
If its not there I gather you deleted it and its not related to the 3:00 AM Query. You can prove this by using these two programs to track both the up time and the reboot. Controller Run Time: ISY Uptime - [ID 0265][Parent 012A][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'GMX' content 'ISY - Uptime Counter' Wait 5 minutes and 30 seconds $i.ISY_Uptime_Counter = 0 $i.ISY_Uptime_Counter Init To 0 Run Program 'ISY Uptime' (Else Path) Else Wait 1 hour $i.ISY_Uptime_Counter += 1 $i.ISY_Uptime_Counter Init To $i.ISY_Uptime_Counter Run Program 'ISY Uptime' (Else Path) This program will track the ISY Series Controllers operating uptime. It will increment every hour the controller is running. A e-mail will be sent upon the ISY being rebooted. This program is set to run at start up and this is how it knows the controller has been rebooted. The (init) value is set to (0) zero so it knows the system has been rebooted. Current Controller Up Time: Current Uptime - [ID 02F3][Parent 012A] If Time is 11:50:05PM Then Send Notification to 'GMX' content 'ISY - Current Up Time ' Else - No Actions - (To add one, press 'Action') This program emails the running uptime of the ISY Series Controller daily at 11:50:05 PM.
-
In the programs tab it will be listed at the very top. A better option is to disable the query and see what happens. How do you know the ISY Series Controller is rebooting at 3:00 AM? Did you set up a reboot email in the system to inform you of that fact?
-
When I downloaded the logs to view them, the time frame prior to that event wasn't there as the log was full. Meaning it stopped capturing any further events in the system. Apparently my system has lots of activity and thus fills up the logs and there isn't anything to be seen when I need to review them.
-
Logs were full so nothing could be gleaned from that unfortunately. I do not use 127.0.0.1 for any NR's as this is known to tie up and bring down the controller. As an aside, since this error message came up the system has auto-magically restarted every *Disabled Program* in my system. Programs that I disabled more than five years ago just came on line and started sending random emails.
-
At the very end of the body is there at least one curly brace?
-
OK, also is the code including this -> amzn1.ask.account.
-
Well, I'm not sure we can say its 100% on my end as I am having some controller issues. Not related to your skill at all just this controller is being stupid. So, I couldn't stand to wait and decided to press the link you provided just to see how it operates. Alexa made a sound and the color ring turned orange. Upon asking her what notifications were pending she indicated one message and than started saying *Hello World* Just awesome . . . Can you provide a edited version of how the code strings are appended in the body. I think there is a curly brace I deleted or left and that might be why it didn't work. Unless there is that 90 minute delay for this?
-
Doh!!
-
Trying to set up a new NR for the Notify Me Skill for what ever reason pressing the save button was taking forever. When it was done thinking this is what I was presented with?!? In all the years using the ISY Series Controller I have never seen this specific message.
-
Who is the email coming from can one of you give me a image capture from the email header. Just got back home and tried the new link from Randy but don't see anything. I also disabled and enabled the skill too but still no joy.
-
Aha! I do in fact reside in Canada! One thing I will check to see is if my USA address that Amazon assigned to help resolve the lack of API support is still in place. If so I will check if logging into my USA account enables me to continue. If not I shall await your fix next week! Thank You! Sent from my iPhone using Tapatalk
-
Email to authenticate came instantly to enroll the new skill. But I have not received the password / secret code and have checked both junk / spam folders.
-
Sign me up PM heading your way.
-
Sign me up would love to see how this works.
-
Please follow what I asked you to do and reply back as to the outcome.
-
Do you have any dual band plugin modules in the home? If so bring one as close as possible to one of the doors even if you need to use an extension cord. Wait the customary time and report back success / failure regarding heart beat capture. Sent from my iPhone using Tapatalk
-
Yes to both . . .
-
The 99 is no longer made and has been replaced by the 994 for many years. You can purchase the 255 version and upgrade to the 1024 when ever you need to later. You need to purchase the ISY Portal to enable Google Home which also comes with the network module.
-
Just to be clear when you enrolled this new device which method did you use? Also how many nodes are present two or three as older open-close (trigger lincs) did not have a heart beat node. Also, one of the other nodes does not change state that requires the jumper to be removed / jumpered which enabled dual mode. Very few people use the dual mode but it has a use case for some. Newer open-close sensors have removed the jumper and the only method to access that mode is via software. As far as I am aware no controller supports this feature including the ISY Series Controller. Lastly, your controller should be using the last official release of firmware 4.6.2. Anytime a new piece of hardware is purchased best practices is to always hard reset the device to a OEM state to ensure any test links, programming, etc are removed.
-
Hi Michel, I will review the logs but don't suspect they will prove very helpful as my system fills up quite fast due to the energy / weather modules. Even having expanded the logs via Telnet it doesn't seem to offer enough capacity to store those logs if and when needed. The primary reason for this post was to let the team know such an event did happen. Next, was to inquire how and why the system let the time become corrupted. In my mind it defeats the whole purpose for a on board RTC and NTP if the ISY firmware can just circumvent it. Some of the systems I work on have independent and separate clocks which act as watch dogs. Their only role in life is to ensure time keeping is accurate and to compare it to other clocks in the system. If there is ever a discrepancy a flag is thrown and alerts sent out for user review / inspection. I would hope this might be something the team may consider in the future as the ISY Series Controller essentially is a very smart clock that crunches numbers very well. Just my thoughts on that point . . .
-
Eager to know also considering it defeats the purpose of having a on board RTC which also connects to a NTP Server!
-
Disable simply tells the system to ignore the device and not declare any faults. Unlinking removes all related links / scenes from all devices in the Insteon network. What exactly is the problem you're trying to solve?
-
A few weeks ago I was Alpha testing some new firmware for my energy monitoring system. During the testing stage it was found high REST calls were impacting the ISY Series Controller. Regardless of that fact what happen next really surprised me. Systematically, all of the Insteon leak sensors declared a value of 2 no other battery operated device had any faults. This happen several times over the course of a week and rebooting the ISY Series Controller did not solve that issue as noted above. The strange part is the fact the controller was sending out emails listed into the future?!?! As seen in the image captures here they are dated for 7.6.2021 ~ 5.6.2022
