-
Posts
5102 -
Joined
-
Last visited
Everything posted by Techman
-
Hi Michel, If your referring to the timestamp on the climate module it shows as current. I don't know what it was when I first noticed that it didn't update. There are some "140005 CLI-HW" and "140000 api.aerisapi.com" errors that occurred on 27th and 28th which was most likely the last day the climate module updated itself. I'm not using a static IP address. I've attached a copy of the error log for the last week. Regards Techman
-
RE post #30, I re-entered the location ID (KSMO) and now the data showing appears to be correct. Seems that the HamWeather data wasn't updating in the ISY as the last time we had thunderstorms was on Sunday July 27th and it was still showing that data this morning, Tuesday July 29th.
-
Glad to hear it's fixed. You can also add a date and/or time variable to the body of the message to show exactly when each device was activated.
-
I'm also showing light rain and thunderstorms however the sky is clear and there has been no rain. The reporting station is KSMO
-
You might want to double check your remaining notifications, stage 2, 3, and 4, to make sure that the fields are correctly populated. The program looks OK. Can you post a copy of one of the notifications that isn't working.
-
LeeG, This is the string I previously used but it doesn't return the current temperature. Did I miss something? Temperature: ${sys.node.1F 0E E8 1.ST}
-
What is the correct syntax to send the current temperature of an Insteon thermostat in an email?
-
Grace Digital just released their new tuner GDI-IRCA700 which has a large color display, it's something you may want to check out.
-
-
also when using HAMWeather you'll need to search by city name as it doesn't recognize zip codes. It's best to upgrade to the current ISY firmware as it addressed some climate bugs.
-
You'll need to upgrade your firmware to 4.2.5 as HAMWeather is better supported beginning with that release (see the release notes for bug fixes).
-
Thank you. I did the restore and went from a 950 link count down to 306. It's hard to believe that I had so many dead links in the PLM, that's quite a significant memory recovery. The restore screen went up to about 13% then closed. Hopefully everything got restored.
-
You might be getting a voltage drop when the fan starts up due to a poor electrical connection. . How many watts are your lights drawing? What type of bulbs are you using, CFL or incandescent? When the lights are on and you turn the fan on does the fan speed seem to initially lag?
-
If I do a restore to an existing PLM do I still need to put all the battery operated devices in link mode as the restore PLM pop up window requires? I have 9 of them. What will be the outcome if I don't? Can I write to them after the restore by individually triggering them and setting the 994 pro to auto write?
-
K5MAP When you refer to the 0-15 I assume you're referring to the LED brightness levels on the KPL buttons as that's the only 0-15 option for the KPL. If you want each of your buttons to control a different scene then you need to place that button into the scene as a controller along with the device(s) you want the scene to control. You don't need to change the action of the buttons, they should be in the toggle mode assuming that you want to toggle your scenes on and off. Hope this helps Techman
-
MustangChris04 The contact should be CLOSED and the green status LED on the I/OLinc should be ON when the garage door is open, the LED should be off when the door is closed. If that's the case then you're properly wired. Make sure that you don't have trigger reverse enabled on the I/OLinc
-
see following post
-
MustangChris04 The bulb is not connected to a switch or dimmer, it is being controlled directly by the ISY Brian H I have numerous LED bulbs connected to various Insteon controllers and none of them flicker when dimmed except the Insteon bulb. Smarthome said when the bulb is connected to a Insteon Hub it didn't flicker so it's possible I have a defective one.
-
I just installed one of the 9 watt bulbs and noticed that when I dim or brighten it flickers during the process but is steady once it reaches the intended brightness. I spoke to Smarthome who said that when using the Insteon Hub they didn't experience any flicker. I'm wondering if I have a bad bulb or if the ISY algorithm is causing the flicker.
-
Catch up schedules is NOT checked Query at restart IS checked
-
I just added the climate module and about two minutes after the ISY rebooted everyone of my devices turned on. The ISY didn't reflect the on status of the devices. Is this a coincidence and/or is my PLM on the way out? This is the first time I've experienced this.
-
-
I originally had it that way and was getting SMTP errors from one of the ISP's so I divided them into two groups. I'll try combining them once again to see what happens.