Teken

This is the log from me trying to make a change. Then, me performing a Query Insteon Engine task. Teken . . . Thu 04/05/2012 06:05:10 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 1F 00 Thu 04/05/2012 06:05:10 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Thu 04/05/2012 06:05:10 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Thu 04/05/2012 06:05:10 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/05/2012 06:05:10 PM : [All ] Writing 0 bytes to devices Thu 04/05/2012 06:05:10 PM : [All ] Writing 0 bytes to devices Thu 04/05/2012 06:05:14 PM : [All ] Writing 0 bytes to devices Thu 04/05/2012 06:05:28 PM : [All ] Writing 1 bytes to devices Thu 04/05/2012 06:05:28 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 0D 00 Thu 04/05/2012 06:05:28 PM : [iNST-ACK ] 02 62 11.DC.42 0F 0D 00 06 (00) Thu 04/05/2012 06:05:28 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 0D 01 (01) Thu 04/05/2012 06:05:28 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/05/2012 06:05:28 PM : [11 DC 42 0 ] Calibrating engine version Thu 04/05/2012 06:05:28 PM : [11 DC 42 0 ] May not fully support i2, reverting to i1

Update went fine with out incident. However, the SwitchLinc Timer still does not function as it did before. I have appended a screen shot of the error message here. Performing the Query Insteon Engine does not restore the devices timer values. This *Ceiling Light* during install functioned just fine, and the 15 minute timer would operate as one would expect and also blink one minute prior to turning off. After some iteration of the 3.X.X this value changed to an insane value of 255 minutes which could not be changed. Now, with the 3.2.3 firmware release this device is locked at 0 minutes. Teken . . .

I just wanted to provide you with some insight and alternatives. http://www.smarthome.com/forum/topic.asp?TOPIC_ID=9624 Teken . . .

That would be greatly appreciated and most helpful. I look forward to a fix in these devices. Teken . . .

I was connected to a computer down stairs on the same network via a tethered connection. Still no go at this point, I will look into firewall settings, and port forwarding. Teken . . .

I wanted to chime in as well. I can not get this WOL to work either? I am using Windows Ultimate 32 bit edition. All of the above settings mirrors the other users . . . Can someone who has it working chime in because this is quite embarrassing as I come from a network environment. Teken . . .

Hello Michel, Performed the query insteon engine. It did restore the original values back to 0, 15, 255 minutes. Performing a restore device still does not allow me to change any of the 4 switches. I also removed and re-added the one device to see if it would correct the issues. All four devices still will not accept any changes in the timer values. Also, please note regardless of the values 0, 15, 255 minutes. None of them actually work any longer? Teken . . .

Fri 03/30/2012 05:03:16 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 1F 00 Fri 03/30/2012 05:03:16 PM : [iNST-ACK ] 02 62 11.DC.42 0F 1F 00 06 GOF (FLAGS) Fri 03/30/2012 05:03:17 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 1F 00 GOF (FLAGS) Fri 03/30/2012 05:03:17 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:17 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:17 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:23 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:30 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:37 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 20 04 Fri 03/30/2012 05:03:37 PM : [iNST-ACK ] 02 62 11.DC.42 0F 20 04 06 (04) Fri 03/30/2012 05:03:38 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 20 04 (04) Fri 03/30/2012 05:03:38 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:38 PM : [All ] Writing 0 bytes to devices Fri 03/30/2012 05:03:43 PM : [iNST-TX-I1 ] 02 62 11 DC 42 0F 20 05 Fri 03/30/2012 05:03:43 PM : [iNST-ACK ] 02 62 11.DC.42 0F 20 05 06 (05) Fri 03/30/2012 05:03:44 PM : [iNST-SRX ] 02 50 11.DC.42 13.24.E1 2B 20 05 (05) Fri 03/30/2012 05:03:44 PM : [standard-Direct Ack][11.DC.42-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 03/30/2012 05:03:44 PM : [All ] Writing 0 bytes to devices ===================================== You will note 0 bytes are being written to these devices. The various entries are me simply selecting different box's to see what is happening and also to gather more data for those to review. Teken . . .

Installed 3.2.2 with out incident. I however continue to experience problems with the SwitchLinc Timer(s). As some of you may recall I have four of these devices in various rooms with two specific firmware versions .38 & .63 A few months ago I noticed when the 3.X.X firmware was released that the 15 minute timers stopped working. Upon selecting the options button the ISY showed that some of the timers were either set for 0, 15, 200 minutes?? Changing the timer value always greeted me with errors and no change could be applied. Since this new 3.2.2 Beta release those values have all since changed to 0?? There is something affecting these 2476ST relay timers. In the interim I have made some programs to replicate the desired on / off times. For me this is not a long term solution as I require these devices in specific zones to have a level of redundancy with out the need for a HA controller being present. The other down side is that Smarthome in their infinite wisdom has killed off this device! Below are the screen captures along with the log entries. Insight Teken . . .

Thank you all for the programs. They will come in handy when I am ready to deploy all of the fans in my home later this summer. Teken . . .

Michel, I sent it off just a few moments ago. As always, thank you and the entire UDI development staff for their continued support and guidance. Beta, is exactly that and I take no offense or angst in things not working 100% during a developmental cycle. Up ward and onward . . . Teken . . .

OK, came home and the following were my observations of the ISY-99i Pro. All three green LEDS were lit solid on the left side. Power cycling the ISY and waiting 10 seconds before applying power brought the device out of lock up. Logged into the Admin Panel and half of the links would not turn on, or display the correct status. One very strange thing I also noted when turning devices on / off. Turning off a device which had a remote linc 2 in the same scene showed that the ISY also changed the status of the remote linc 2? I am not sure why the new firmware would even attempt to display the RL2 status when its clearly not possible. The status for the RL1 remained unknown as it should. I was not comfortable with the current state of the Insteon network so I decided to reload the 3.2.1 firmware. Upon shutting down the ISY I was greeted with another unresponsive system and the system just hung. The only recourse at that time was to go into the Task Manager and kill the process. Reloading the latest 3.2.1 firmware appears to have corrected any ghosts and gremlins in the system. I would like to note that before this whole incident that when I came home and POPO the ISY I was able to remotely login to the system. But, did note the above problems with the instability of the system. Since taking the time to reload the 3.2.1 firmware and deleting the Java cache, and also confirming the *Help, About* both platform and Admin Panel are correct. The system appears to be fully operational at this point in time . . . Teken . . .

Alright, great insight. Now, lets see if this is my problem when I get back home. Which if is the case high lights that *EVEN* if I had the ability to remote kill the power to ensure a hard reboot it may not recover due to a IP conflict. Teken . . .

Updated remotely from work. The update appeared to go fine. Upon clearing the Java cache and relaunching the browser to access the ISY. I am presented with no access? I will have to wait to get off work and hard reboot the ISY and see what happens. Figures the only time I remove my remote web switch from the network. Now, when I need to hard reset the device I have no ability to do so! Teken . . .

Late last year I was in the mist of incorporating the last pieces of home automation with respect to water safety and awareness to my home. One of the key elements in my home is having the ability to turn off all water supplies to specific appliances through out the home. Many of you have more than likely experienced some sort of water damage in your time. Having experienced many of the same in previous homes I was determined to never endure the same fate again! Below is a link to several video's of how I have incorporated the ISY-99i Pro platform into my Home Automation System. One of the key elements was having the ability to turn off a device when the presence of water was detected. This was done to ensure that electricity was not present while standing water was in the immediate area. I was very surprised, and aggravated to find out that there was no physical way, or method to program the Triggerlinc and the Appliancelinc to send a alert message, and at the same time turn off the Appliancelink! If it was not for the power and flexibility of the ISY to allow the user to taylor and customize the on / off conditions for an alert. This automated water system would only serve to turn off the water supply, but not have the ability to alert the user of the water event. So as I have stated many times in the past to all those who have asked. The UDI ISY-99i Pro is the single best investment in all aspects of the word. Teken . . .

Right click of the mouse, than select query. This should refresh the low battery status in the ISY Admin Center. Teken . . .

Teken, did you ever get this to work for your setup? Hoopty, For the interim I have simply replicated all five TSTAT using your original program. I do however have a couple of questions for you. So if you don't mind taking the time to break it down for me, it would be greatly appreciated. Heating ran for a total of 0 cycles today. <-- Why does this not show a value?? Total heating run time was 10 hour(s) 146325 minute(s). <-- Why does the minutes calculate to this amount?? I read the initial thread about the seconds and how you had to divide the numbers etc. But, some how this math doesn't add up. Your insight would be appreciated ! Teken . . .

Hoopty, Thank you so very much for providing the screen shots. I have some questions for you or anyone else who may know. I have five of these thermostats installed and all of them also have the humidity sensor in place. I have copied the original program from the one TSTAT. This copy of the program has been renamed and also the secondary TSTAT has been assigned to as the device to be queried. How do I track this TSTAT and the other ones?? Teken . . .

Would one of you please post up a screen shot of each of the tabs with the above programs / variables in their respective places for me to see and compare. I just can't seem to get this up and running. Teken . . .

Would you mind posting up the final code once its confirmed to be working. As I have the same needs and requirements as well. Teken . . .

I am subscribing to this as I am trying to figure out how to accomplish the same goal. I have four of these TSTATS deployed right now and want to know when they turn on / off. This will allow me more insight as to the state of the home. Teken . . .

I will be pulling these guys out of service and have them replaced under warranty. There is no head way on this matter no amount of resetting and killing the power has any affect on these things. I don't know why my gut keeps telling me there is a conflict with the newest ISY firmware that is causing this issue to appear. Unfortunately I can't roll back the firmware to find out in this case . . . Teken . . .

Hrmmm that is a good point ELA. 1.5 volts isn't a large margin for the battery to go low. But, I believe it could still be done if they wanted to. The basic principle is still the same to monitor the voltage drop. I did however place my thoughts in the idea thread in the SH forum. Even if its in vain, but hey at least its up there for others to ponder or at least know that these devices do not incorporate any such feed back electronics. Teken . . .

I am going to place that as the next upgrade that needs to incorporated into these devices in the SH forum. Its 2012 now, this should be part and parcel and basic 101 for such devices . . . Teken . . .

Really? Damn it !! Teken . . .