Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

junkycosmos

Members
  • Joined

  • Last visited

Everything posted by junkycosmos

  1. Updated to 3.1.12 today with help from Rand and Daryl (thanks again guys!) while troubleshooting a very strange slow network (tcp/ip not insteon) performance in Admin consul and Mobilic over last day after running 3.10 for few weeks. The slowness issue is gone and appeared to ghost away from Daryls call and turning off windows defender however I can not reproduce the issue turning defender back on so it remains a bit of a mystery. I do have two questions regarding errors I see now (and did so in 3.10): A. on occasion I see a popup in the consul of system busy FileOpen ] Open failed for [/CONF/ELECMTR.CFG] ®. B. checking error log I see a lot of entries, some mentioning UDQ: Queue Full: LOG. Any input on what these are about would be great. thx much J (non ELK ISY 99ir/pro) Mon 2011/11/21 02:55:47 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:05 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:15 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:25 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:35 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:46 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:56 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:55:08 PM System -5 Start Mon 2011/11/21 02:55:24 PM System -170001 [Network] Established Mon 2011/11/21 02:55:27 PM System -80004 n/a Mon 2011/11/21 04:03:49 PM System -100 No network connection Mon 2011/11/21 04:03:53 PM System -170001 [Network] Established Mon 2011/11/21 04:32:56 PM System -5012 28 Mon 2011/11/21 04:51:41 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:51:53 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:04 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:14 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:25 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:51:07 PM System -5 Start Mon 2011/11/21 04:51:24 PM System -170001 [Network] Established Mon 2011/11/21 07:01:46 PM System -140005 CLI-WBug Mon 2011/11/21 09:12:56 PM System -10011 n/a Mon 2011/11/21 09:27:37 PM System -5012 27 Mon 2011/11/21 09:28:04 PM System -100 No network connection Mon 2011/11/21 09:28:12 PM System -170001 [Network] Established Mon 2011/11/21 09:28:32 PM System -100 No network connection Mon 2011/11/21 09:28:36 PM System -170001 [Network] Established Mon 2011/11/21 09:29:01 PM System -10011 n/a Mon 2011/11/21 09:29:26 PM System -100 No network connection Mon 2011/11/21 09:29:31 PM System -170001 [Network] Established Mon 2011/11/21 09:31:24 PM System -100 No network connection Mon 2011/11/21 09:31:29 PM System -170001 [Network] Established Mon 2011/11/21 09:34:24 PM System -100 No network connection Mon 2011/11/21 09:34:29 PM System -170001 [Network] Established Mon 2011/11/21 09:36:13 PM System -5012 30
  2. Thank you (again) Lee. Adjusted as you suggested and works. I was thinking of this from a scene perspective and not who controls the scene level (the motion sensor). Corrected day program If From Sunrise To Sunset - 1 hour (same day) Then In Scene 'Sensors / SunPorch-Sensor' Set 'SunPorchbyFR' 10% (On Level) Else - No Actions - (To add one, press 'Action')
  3. Q here for those knowledgeable on "scene adjust" Can I control on level of a scene that is directly called by a motion sensor ? I have a scene "Sunporch" that contains four members. 2420M motion sensor 2486D keypadlinc dimmer button B 2485S keypadlinc relay button B 2476D switchlinc dimmer v.38 "SunPorchbyFR" The switchlinc is wired to entrance way light. I have all four linked directly to this scene as controllers, motion sensor included as so there is no delay in turning on the light via ISY program. What I would like todo is set "on level" for this scene to 10% during the daytime hours and at 50% or so during evening time hours. I have programs below set and running ok but the actual on level of the light when motion sensor sets the scene on does not change. In the admin consul clicking on Scene "SunPorch" I can see the On Level changing but clicking on the member of that scene "SunPorchbyFR" the On Level [Applied Locally] does not change. Was looking at using these two programs: DayProgram If From Sunrise To Sunset - 1 hour (same day) Then In Scene 'SunPorch' Set 'SunPorchbyFR' 10% (On Level) Else - No Actions - (To add one, press 'Action') NightProgram If From Sunset - 1 hour To Sunrise (next day) Then In Scene 'SunPorch' Set 'SunPorchbyFR' 50% (On Level) Else - No Actions - (To add one, press 'Action') I have been successfully using nearly the same for a bathroom setup that dims at night however that setup has the ISY calling the scene when control of motion is turned on. Thanks for any input. J
  4. Upgrade of files went smooth. ISY took a long time with initial a status bar scroll after 1st reboot (3-5mins). All start up programs ran quickly in background during scroll and it completed fine. ****** Very nice addition on the Remote Linc2 support - thank you ! small stumbles I had adding Remote Linc2 1st time I tired to add (via add device, specified address and device) I forgot to put RL2 into linking mode. Did not receive warning message to place RL2 into linking mode but instead received error of "Failed writing the high water mark, Node not added - failed removing links". On my 2nd try I started with putting the RL2 into linking mode than did add device ... This time ISY placed new device names in My Lighting but they had i/o/i/o/i/o green mark. Clicked green button at top of screen to automatically write to devices, received nice pop up message informing me to battery powered devices into linking mode. 1 sec after clicking OK all green marks cleared (super quick). Device added 8 entries in My Lighting; small note that devices are numbered slightly off to start instead of lettered. No big deal to rename but order stays slightly off in list. remote linc = controlled by button B remote linc - 2 = controlled by button A remote linc - 3 = controlled by button D remote linc - 4 = controlled by button C remote linc - 5 = controlled by button F remote linc - 6 = controlled by button E remote linc - 7 = controlled by button H remote linc - 8 = controlled by button G ****** Thermostats: Confirmed the query V2 Thermostats for Fan Mode and Heat/Cool status is also working nicely with two Tstats on v.92. Thank you again. Noticed set the "Set Options" button on the Tstat page which reveals option to report humidity. On the default setting here: One Tstat had the option checked by default (TstatUp) but the other Tstat has the option unchecked (Tstat Down). Will we need to check that option now to have HUM updates to ISY ? ****** Agreed with prior posters here about how good this product is both from the continued updates and excellent support. Thank you and nice work UDI Team
  5. Hi Michel Good news to report here on the motion sensor and -2 errors. Since I deleted and successfully re-added to ISY above I had seen no more -2 errors from that motion sensor. One item I failed to note prior was that I accidentally renamed my motion sensor the same name it was prior to removal. Had not thought much about it but later I noticed that the re-added motion sensor seemed to be automatically recognized by a few previous programs (batt low and dusk). Said otherwise the programs did not state "unspecified device" like I am used to seeing when a device is removed. Almost as if the programs automatically recognized the old previously deleted device and placed it back into the program when I re-added it. No big deal but I wanted to mention. Separately I'll note that I do continue to see a few other -2 errors which date back long time from other units so I am curious actions I could take to clear those up eventually. Sensors / MOfficeM2-Sensor Tue 2011/09/06 10:46:31 AM System -2 Sensors / MOfficeM2-Sensor Tue 2011/09/06 01:17:05 PM System -2 ((removed and re-added MOfficeM2 sensor)) JeffOfficeFan2 Tue 2011/09/06 02:57:24 PM System -2 MOfficeR Tue 2011/09/06 04:27:37 PM System -2 Sensors / SunPorch-Sensor Tue 2011/09/06 06:07:54 PM System -2 Sensors / DwnMotion-Sensor Tue 2011/09/06 06:26:50 PM System -2 Sensors / MasterBath-Sensor Wed 2011/09/07 07:22:00 PM System -2 GarageMotionLight Wed 2011/09/07 08:04:38 PM System -2 Sensors / DwnMotion-Sensor Thu 2011/09/08 04:09:18 PM System -2
  6. junkycosmos replied to Goose66's topic in ISY994
    With the minor annoyance of the prior issues with the stat 2441 stat adaptor aside (SH issue with firmware) I have been very happy with our 2 zone setup. I went with a honeywell zone controller board in between the t1900s for some measure of safety after seeing a few horror storries of wireless going wacky. Might be isolated case noted here http://forum.universal-devices.com/viewtopic.php?f=25&t=4727&hilit=fried+ac but prior to zoning I also encountered something similiar of a "bouncing loop" with my own T1900 turning my humidifer on and off I would also note that the support guy at Venstar was very helpful but in the end we found no good explaination. Current setup with 2 t1900s both with a 2441V works great and the ISY makes programming simple while the zone controller by honeywell has reasonable safety limits and lock outs. Zone board has both overheat and overcool limits. Noted I did go with the higher end zone board with more than needed zones since it has options for multi stage heat that can be locked out by preset outdoor temp. I.E. Leaving windows open at night and the furnace will not kick into 2nd stage heat trying to warm the yard. Hope the links don't offend anyone but I have ordered from this place with success, unit appeared new non gray market. HZ432K https://www.pexuniverse.com/honeywell-t ... -panel-kit C7089U1006 https://www.pexuniverse.com/c7089u1006- ... oor-sensor J
  7. Michel, understood and agreed tried adding device 3rd time .. this with remove links, specified address, and specified unit (10.01 2420 Motion) and received a weird failure.. Took the motion sensor out of linking mode and retried the exact same steps as 3rd try above and it added quickly (6 seconds or so). Now that sensor is re-added I will place back in original location and see if errors persist.
  8. Hi Michel Thanks for the reply. Just removed the device and attempted to re-added it (remove links, auto discover type, specified address of 11.9F.F4). After about 1 minute I was given the error "Node not added - failed restoring device" Please see screen shot as it also mentions CLI WBug Tried second time to add unit back in and received similar error, again after 3 scrolls of status bar. Do I need to specify the device type ? Noted too that I only recently added this particular sensor to the ISY about a wee back to replace one that completely died. This unit is "new" but was in the closet for a while and is a v1.1. The other units which show the occasional -2 have been on the network for a few months.
  9. Michel, Correct. Looking back I do have a few prior warning emails from April of this year. Sometime after that I did have three units die of dead batts with no warning. Looking now in the ISY current state of battery status is blank on all of them except for the one I just queried that now shows "off". Could it be that after a power cycle from prior version upgrade that the batt status just stayed as blank and never triggered to "On" ? Entirely separate note on the -2 errors noted in log. I have one motion sensor that is giving these pretty regularly. Few other devices on occasion give -2 but none give regular errors like this one. Noted that this Motion sensor is only linked to ISY, is about 10 feet from ISY's PLM, and has a few lithium batt. Sensors / DwnMotion-Sensor Tue 2011/09/06 06:31:45 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 06:58:36 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 07:35:53 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 10:07:10 AM System -2 Sensors / DwnMotion-Sensor Tue 2011/09/06 10:08:07 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 10:46:31 AM System -2
  10. Hi Michel, I have seven of the motion sensors 2420M. Long time back they used to alert in ISY with Low Batt signal before going completely out but now they do not anymore. I cannot recall exactly which ISY version used to display the low batt indicator. This was also way back when the low batt "on" would stay stuck in ISY after changing the battery in the motion sensors. My sensors are a mix of old and v2.0. ISY usually receives their on/off status updates (maybe 90% of the time), motion sensors directly linked to switchlincs or kpls trigger near flawlessly (99.5% of the time). would be great to increase the consistency of ISY reading motion sensors and would be great to have the low batt warning back If I can help test something for you all here just let me know. thx J (isy99ir pro 3.1.6) here are a few of the errors I noted from log related to motion sensors Sensors / MOfficeM-Sensor Sun 2011/09/04 12:46:53 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 01:18:57 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 05:23:36 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 06:49:45 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 10:07:47 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 11:51:45 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 12:51:40 PM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 01:00:39 PM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 05:26:36 PM System -2 Sensors / DwnMotion-Sensor Sun 2011/09/04 08:47:41 PM System -2 GarageMotionLight Mon 2011/09/05 07:10:08 AM System -2 Sensors / MOfficeM-Sensor Mon 2011/09/05 07:54:23 AM System -2 Sensors / MOfficeM-Sensor Mon 2011/09/05 08:22:37 AM System -2 Sensors / DwnMotion-Sensor Mon 2011/09/05 11:18:52 AM System -2
  11. same here; I did note some prior errors in separate thread http://forum.universal-devices.com/viewtopic.php?f=27&t=6556 Two nights ago I ran into issue with ISY also locking up. Noted I am still on 3.14 and this is maybe the 2nd lockup I have ever experienced in 3yrs of running betas etc. For me, my lockup occurred when I had admin console open on 1PC and was trying to open mobilinc (fresh install of) on iphone. Mobilinc was working on syncing my devices (I had clicked tap to sync) and I was doing no action in the admin console on PC. After about 2 mins with no response on sync I noticed the flag on bottom left of Admin was red. Tried closing admin and rebooting iphone just to be sure no connection was still open from client. Tried to relaunch Admin on PC and received no response from ISY. Gave up for a while then came back and noted that both power and tx light were locked on in the ISY. Power cycled the ISY and all came back just fine. When I look in my log I see a lot of -5011 rows all at same time stamp prior to the hang. Also I do have very regular errors from wBug. If anyone wants the log or has questions I can send. thx J Tue 2011/08/02 12:56:16 AM System -140005 CLI-WBug Tue 2011/08/02 01:00:17 AM System -140005 CLI-WBug Tue 2011/08/02 01:24:29 AM System -5012 n/a Tue 2011/08/02 01:30:56 AM System -5012 n/a Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:35:10 AM System -5012 n/a Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 02:52:36 AM System -5 Start Tue 2011/08/02 02:53:00 AM System -140005 CLI-WBug Tue 2011/08/02 02:53:57 AM System -140005 CLI-WBug Tue 2011/08/02 02:54:45 AM System -5012 n/a Tue 2011/08/02 02:59:17 AM System -170001 [uDSockets] RSub:26 error:6 Tue 2011/08/02 02:59:23 AM System -5012 n/a Tue 2011/08/02 03:01:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:03:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:06:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:16:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:18:04 AM System -5012 n/a Tue 2011/08/02 03:39:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:44:53 AM System -140005 CLI-WBug Tue 2011/08/02 03:50:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:58:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:05:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:09:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:15:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:18:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:23:53 AM System -140005 CLI-WBug Tue 2011/08/02 04:28:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:32:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:35:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:38:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:51:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:52:52 AM System -140005 CLI-WBug Tue 2011/08/02 05:08:52 AM System -140005 CLI-WBug
  12. Question on support of load status for the 2477SA2 220v normally closed load controller. I searched and found a few discussions on here regarding support for load sense but never saw full conclusion. There are a few entries in the beta 2.17 and 2.18 asking how the ISY displays what might be considered "node2" or load sense for this device. I have verified that the recent version unit received from SH (r1.0 2910 received 2wks ago) had load led that follows load status pretty well when 2477SA2 main relay is off. Closing and opening the load circuit while the main 2477sa2 is off had the load led follow correctly. Toggling 2477sa2 relay on/off quickly can cause the load led to getbstuck on however doing a status querry by isy of 2477sa2 always resets the load led. Having 2477SA2 main relay powered on results in load led staying on regardless of load circuit state being open or closed. So we might say load status led works half of the time: when the 2477SA2 main relay is powered off. Would still be of value to have the load status node reported in ISY even though it only works during power off. There are a few scenarios where it becomes useful to know the controlled load is calling for power when the 2477SA2 is off. This would be especially useful since relay of 247sa2 does not automatically follow load sense led: I.e. Isy could be used to decision when load calls for power run a program to turn on 2477SA2 relay or send notification etc. I see from this forum thread that others have been able to manually link insteon devices to 2477SA2s load sense viewtopic.php?f=27&t=5449 Is there a way to have the load sense report in the ISY ? Thanks much J
  13. Michel, No prob on any delay at all ... I did the two requested changes (program to :15 and template update). Noted I did not change my main template (yet) but rather I used "Copy" button to copy my template, renamed it to MyTemplateSprinklers and then added requested fields. Also updated all of the sprinkler programs to use this template. Good news, this AM program ran and sent correct notification at correct time. Interesting though that in the email the ISY is adding a row of dashes that are not in the template. here is a copy of the email with only from and to addresses changed .. ******** ---------- Forwarded message ---------- From: Date: Sat, Jul 2, 2011 at 5:57 AM Subject: ISY EZRain2b Drive To: myaddress@gmail.com A Schedule was met at 2011/07/02 06:00:16 EZRain2b Drive A Schedule was met at 2011/07/02 6:00:16 AM. ---------------------------------------- At: 2011/07/02 6:00:16 AM Program: EZRain2b Drive EZRain2b Drive ********** here is template "MyTemplateSprinklers" subject field ISY ${alert.program.name} body field ${alert.event} at ${alert.date} ${alert.time24} ${alert.body} ${alert.program.name} ********** side note to prior poster: Irrigation Settings on Configuration Tab >> Climate sub tab
  14. Hi Michel Thx for reply on my template and I follow your easy suggestion for adjustment. However I am still confused as to why the info from an event in a program with no notification (instanthot on) is mixing into event info from a seperate program with notification (sprinkler 2b). Indeed I have not touched my templates since pre variables and aprecieate your suggested change but I am curious to fully understand too. Thanks J
  15. Hi Michel Thx for reply on my template and I follow your easy suggestion for adjustment. However I am still confused as to why the info from an event in a program with no notification (instanthot on) is mixing into event info from a seperate program with notification (sprinkler 2b). Indeed I have not touched my templates since pre variables and aprecieate your suggested change but I am curious to fully understand too. Thanks J
  16. Just noticed something slightly strange with recent email communications from programs. I have one program “InstanHot On†that is not set to send any notice which appears to be crossing into notice for my sprinkler program. upgraded 3.13 on 6/7 around 9am (from 2.8.16) 3.14 on 6/27 have been using these sprinkler programs since 6/1 Noted that the “InstantHot On†program is set to run 5 seconds after the sprinkler program “EZRain2b Drive†program which is picking up its status. I do have another sprinkler program “EZRain1b Front†that ends at 6:00:00, code at bottom just in case that could be part of it. Also noted that 1st email after the upgrade to 3.13 on 6/9 was ok but others since were not Email from sprinkler program on the following dates was correct: 6/1,2,3,5,6,7 and 6/9 ********** From: Date: Tue, Jun 7, 2011 at 5:56 AM Subject: ISY EZRain2b Drive To: myaddress@gmail.com A Schedule was met at 2011/06/07 06:00:16 ********** Email from sprinkler program on the following dates was INCORRECT 6/8, 6/14, 6/17, 6/29, 6/30. Instead of referencing sprikler or schedule it notes InstantHotDisposal. ********** From: Date: Thu, Jun 30, 2011 at 5:56 AM Subject: ISY EZRain2b Drive To: myaddress@gmail.com 'InstantHotDisposal' Status set to On at 2011/06/30 06:00:06 ********** Template Name: My Template Subject: ISY ${alert.program.name} Body: ${alert.event} at ${alert.date} ${alert.time24} ********** PROGRAM "InstantHot On" If Program 'NHome_NotHome' is False And Time is 6:00:00AM Then Set 'InstantHotDisposal' On Else - No Actions - (To add one, press 'Action') PROGRAM " EZRain2b Drive" If From 6:00:05AM To 6:30:00AM (same day) And Status 'JeffOffice.C' is On And Status 'io lincs / RainSensor-Sensor' is On Then Set 'Sprinklers / EZRain 2 Driveway' On Send Notification to 'All' content 'MyTemplate' Set 'Sprinklers / EZRain 2 Driveway' Query Else Set 'Sprinklers / EZRain 2 Driveway' Off Set 'Sprinklers / EZRain 2 Driveway' Query PROGRAM “EZRain1b Front†If From 5:30:05AM To 6:00:00AM (same day) And Status 'JeffOffice.C' is On And Status 'io lincs / RainSensor-Sensor' is On Then Set 'Sprinklers / EZRain 1 Front Yard' On Send Notification to 'All' content 'MyTemplate' Set 'Sprinklers / EZRain 1 Front Yard' Query Else Set 'Sprinklers / EZRain 1 Front Yard' Off Set 'Sprinklers / EZRain 1 Front Yard' Query Let me know any questions here. Thanks Junkycosmos
  17. Had noticed this a while back and am still looking to find exact source of what these messages are about. Cleared my error log yesterday and as of today contents are below. Not too concerned on the semi regular errors about weatherbug although there are a bunch. What I am curious about the repeating -5011 errors. I did see that they are listed as "Process Device State Change SID Not Found from wiki http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages#System_Errors but what exactly does that mean ? Time User Code Message Mon 2011/06/27 03:33:24 PM System -5 Start Mon 2011/06/27 03:33:49 PM System -110022 /CONF/IRRIG.PST Mon 2011/06/27 03:34:17 PM System -5012 n/a Mon 2011/06/27 03:39:00 PM System -5012 n/a Mon 2011/06/27 03:44:07 PM System -140005 CLI-WBug Mon 2011/06/27 03:59:03 PM System -140005 CLI-WBug Mon 2011/06/27 04:01:03 PM System -140005 CLI-WBug Mon 2011/06/27 04:08:46 PM System -140005 CLI-WBug Mon 2011/06/27 04:11:46 PM System -140005 CLI-WBug Mon 2011/06/27 04:13:51 PM System -140005 CLI-WBug Mon 2011/06/27 04:14:45 PM System -140005 CLI-WBug Mon 2011/06/27 04:37:45 PM System -140005 CLI-WBug Mon 2011/06/27 04:43:45 PM System -140005 CLI-WBug Mon 2011/06/27 05:03:45 PM System -140005 CLI-WBug Mon 2011/06/27 05:37:44 PM System -140005 CLI-WBug Mon 2011/06/27 05:45:44 PM System -140005 CLI-WBug Mon 2011/06/27 05:47:44 PM System -140005 CLI-WBug Mon 2011/06/27 05:51:46 PM System -140005 CLI-WBug Mon 2011/06/27 06:00:46 PM System -140005 CLI-WBug Mon 2011/06/27 06:40:46 PM System -140005 CLI-WBug Mon 2011/06/27 06:41:46 PM System -140005 CLI-WBug Mon 2011/06/27 06:59:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:05:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:14:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:27:50 PM System -140002 CLI-WBug Mon 2011/06/27 07:43:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:49:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:50:45 PM System -140005 CLI-WBug Mon 2011/06/27 07:57:45 PM System -140005 CLI-WBug Mon 2011/06/27 08:03:16 PM System -5006 n/a Mon 2011/06/27 08:03:19 PM System -5012 n/a Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:19 PM System -5011 uuid:00:21:b9:00:00:1e,29 Mon 2011/06/27 08:03:24 PM System -5012 n/a Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:24 PM System -5011 uuid:00:21:b9:00:00:1e,30 Mon 2011/06/27 08:03:50 PM System -140005 CLI-WBug Mon 2011/06/27 08:05:46 PM System -140005 CLI-WBug Mon 2011/06/27 08:12:45 PM System -140005 CLI-WBug Mon 2011/06/27 08:25:45 PM System -140005 CLI-WBug Mon 2011/06/27 08:27:45 PM System -140005 CLI-WBug Mon 2011/06/27 08:35:46 PM System -140005 CLI-WBug Mon 2011/06/27 08:42:46 PM System -140005 CLI-WBug Mon 2011/06/27 08:45:46 PM System -140005 CLI-WBug Mon 2011/06/27 08:55:45 PM System -140005 CLI-WBug Mon 2011/06/27 09:04:45 PM System -140005 CLI-WBug Mon 2011/06/27 09:05:45 PM System -140005 CLI-WBug Mon 2011/06/27 09:16:46 PM System -140005 CLI-WBug Mon 2011/06/27 09:27:47 PM System -140005 CLI-WBug Mon 2011/06/27 09:29:46 PM System -140005 CLI-WBug Mon 2011/06/27 09:35:46 PM System -140005 CLI-WBug Mon 2011/06/27 09:41:51 PM System -140005 CLI-WBug Mon 2011/06/27 09:43:46 PM System -140005 CLI-WBug Mon 2011/06/27 09:47:46 PM System -140005 CLI-WBug Mon 2011/06/27 10:02:50 PM System -140005 CLI-WBug Mon 2011/06/27 10:08:47 PM System -5012 n/a Mon 2011/06/27 10:09:46 PM System -140005 CLI-WBug Mon 2011/06/27 10:15:47 PM System -140005 CLI-WBug Mon 2011/06/27 10:19:47 PM System -140005 CLI-WBug Mon 2011/06/27 10:24:47 PM System -140005 CLI-WBug Mon 2011/06/27 10:30:50 PM System -140005 CLI-WBug Mon 2011/06/27 10:35:10 PM System -5012 n/a Mon 2011/06/27 10:37:50 PM System -140005 CLI-WBug Mon 2011/06/27 10:40:28 PM System -5012 n/a Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:28 PM System -5011 uuid:00:21:b9:00:00:1e,38 Mon 2011/06/27 10:40:50 PM System -140005 CLI-WBug Mon 2011/06/27 10:52:50 PM System -140005 CLI-WBug Mon 2011/06/27 10:55:51 PM System -140005 CLI-WBug Mon 2011/06/27 10:59:46 PM System -140005 CLI-WBug Mon 2011/06/27 11:11:46 PM System -140005 CLI-WBug Mon 2011/06/27 11:22:46 PM System -140005 CLI-WBug Mon 2011/06/27 11:33:47 PM System -140005 CLI-WBug Mon 2011/06/27 11:41:47 PM System -140005 CLI-WBug Tue 2011/06/28 12:01:48 AM System -140005 CLI-WBug thanks for any input J
  18. wow great on news 3.14 so quick! Just updated from 3.13. Install of files went smooth as usual. Relaunched Admin consul, I had not cleared java cache, however all launched fine (version of isy showed 3.14). After high level check of consul (not sure if I checked programs tab or not) I went to purchase modules. I did purchase the Irrigation module via google checkout, noted that the option to apply a discount did not appear until after I logged into my existing google account. Discount did take and total of $4 was reflected on last step. After purchase I did go to manage modules on ISY consul and ISY asked to reboot. All rebooted fine yet after re launching the admin consul my programs tab was completely blank. Close and reopen of Admin consul showed same. Solved issue by closing all browser windows, going to java control panel, and clearing out the java cache. Subsequent relaunch of Admin consul shows all fine. Just a reminder to us that clearing that cache is an important step. Thanks for the discount on the Irrigation mod
  19. Thanks for the reply. Just checked today and indeed i see Mobilinc has pushed their 3.0 update that looks to be large ui update too. I was previously on v2.17, noted that app store pushed v3.0 yesterday 6/23. Appreciate the link on errors and I follow you completely on "server" error having a few causes, mainly noted it as an observation. thanks all
  20. Few times now (3x ?) since moving from 2.8.16 to 3.1.3 few weeks back I have run into a situation where MobiLinc gets stuck on the screen trying to clear communication errors. Immediately after starting MobiLinc popup is shown of 'cannot communicate with zyx..'. Clicking ok appears to clear 1st pop up window and present 2nd popup window. On clearing of this 2nd popup window Mobilinc usually hangs. The errors were expected communication issues from two modules being unplugged. Have tried power cycling ISY, power cycling iphone, with no impact. Both distinct times I have had this situation occur I have had at least 2 modules with communication errors. Solution both times has been to select "clear error log" from ISY admin module. Prior to upgrade I could clear multiple communication pop up windows without issue. Noted too as above my error log does contain a lot of similar messages. Thanks much for the note indicating these come from the ISY not being able to reach the Internet however that is perplexing since we have many other devices running very solid on same shared pro connection. thanks for any input J
  21. need a little help sorting out my error log post 3.1.3 update. I upgraded from 2.8.16 few days ago (around 6/7 9am), update itself went very smooth. Since then though I have noticed received pop up message about communication error with my EZRain zone 1 every day after program run although program runs and zone is watering fine. This failure seems to be more common since upgrading to 3.1.3 but I am not 100% sure. This prompted me to check error log (something I am not too familiar with yet) and found a ton of items in it. in my error log I found a flood of messages with -5011 flooding -140005 and a few others Full log here http://tinyurl.com/3dl7fs7
  22. Just checking in here to see if there might any new progress on hooking up isy to a RxCom for Oregon scientic data ? thanks J
  23. Hi All, Thank you much for adding these into 2.8.11 ! Just tonight I got to upgrading from 2.8.10 to 2.8.16 and was really excited to see the inclusion of weather info in the alerts. Thank you ! To answer your way overdue question on ideas for use: 1. send alerts to myself and other family members when the temp is lower than X (say 5 F) before they leave for school. "Hey kids wear a jacket its X". 2. similar but as alerts to myself for covering the garden or be alerted when the temp outside worth of closing up the windows 3. Hum and pressure changes (rate per hour) used to trigger alerts for my wife. She has been suffering from sinus headaches which we suspect are due to pressure and or humidity changes. This could help us prove theory and maybe even help take action prior to her being a wreck. Interesting point about #1 & #3 here is that now starts to bring the ISY into place where the rest of the family might feel value. Whereas today it is entirely out of their minds while doing all of its light and security management on their behalf. Did have three items to inquire about. small item: in programming interface: Condition: Module: Climate: spelling is "Hummidity Rate" (extra M) but on ISY Climate tab it reads correctly "Humidity Rate:" Noted though that condition does appear to work fine small question: in programming interface: Condition: Module: Climate: pressure options are listed mBar but on ISY Climate tab it reads pressure in inches. (I am using station RSMSP) The conversion is no big deal however was not sure if this was intentional, known, or would impact program condition itself. Having the programming in mBar does give a very nice breakdown in selection. larger question: When I created the program below for task #3 above I ran into it repeating every 60 seconds. What I am trying to accomplish is to have the ISY alert me once every hour if that the climate conditions are true. Instead it is repeating every 60 seconds. I suspect that since my ISY is set to "read weatherbug data every 60 seconds" this polling is causing ISY to re-evaluate status of my program conditions and restart the program. Is there an easy programming solution to this other than setting my polling to 3,600 sec ? Would like to avoid changing this by polling since we will want other programs to repeat at different intervals. noted that the actual rates in here are just to test with: ***************** If Module 'Climate' Hummidity Rate >= -5 % Or Module 'Climate' Hummidity Rate >= 5 % Or Module 'Climate' Pressure Rate >= -17 mbar Or Module 'Climate' Pressure Rate >= 17 mbar Then Repeat Every 1 hour Send Notification to 'J' content 'WeatherAlertShort' Send Notification to 'M' content 'WeatherAlertShort' Else - No Actions - (To add one, press 'Action') ***************** Thanks much for any help here and to ISY Team for including the Weather info in the custom alerts! J
  24. Is there a way to pass the any of the Climate info from weatherbug into a custom alert template ? Would be interested in passing current temp if possible into notification. thanks J
  25. Hi Michel, Not a problem on your reply timing... surely hope folks do not expect forums to be instant... thanks for the reply. I do have two follow up Qs: 1. pretty sure the answer is no here but figured I would check. Is it possible to individually control multiple locks from one MorningLinc module ? Currently we have 1 Morninglinc controlling 4 locks as a set but ideally we would like to control them individually. 2. Noted too that SH states MorningLinc can control up to 15 RF Locks however names no reference to individually. Seeing reference to a 15 lock limit seems silly (Locks or unlocks up to 15 Morning Industry RF deadbolts and door locks at the press of a button) but it brings forth my 2nd Q: Does anyone know if the MorningLinc RF comm to Lock is 2way ? Easy assumption would be "no; its 1 way" however reference to the 15 lock limit is interesting but maybe that is just poor documentation on SH's part since there is a "15 RF remote limit". However if MorngLinc RF comm to lock is 2way I would begin to wonder if there are any long term options of pulling confirmation messages etc. Thanks J

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.