Illusion Posted June 6, 2011 Posted June 6, 2011 Yes, the nodes for the IR TX are there in the list for me as well. Quote
andyf0 Posted June 6, 2011 Posted June 6, 2011 Waahhh! Michel, do you think you can fix this for the IRLinc RX in the next update? Quote
Brian H Posted June 6, 2011 Posted June 6, 2011 I don't believe I downloaded the incorrect update as the file size matches the one in the ISY99i link. Is it normal to now have three Zigbee choices in the Link Management Tab? Quote
Michel Kohanim Posted June 6, 2011 Author Posted June 6, 2011 Hello andyf0, yes, consider it done. Brian, if and only if you have 994 with Zigbee enabled. So, this is a bug. Thanks for reporting. With kind regards, Michel Quote
Illusion Posted June 8, 2011 Posted June 8, 2011 When I select a device from the new web interface I do not see a title for which device I am looking at... Quote
Brian H Posted June 8, 2011 Posted June 8, 2011 I see the same thing when I select a device. I am using Windows XP SP3. Quote
Michel Kohanim Posted June 9, 2011 Author Posted June 9, 2011 Hi Brian, Known issue which should be fixed in the next release. Thanks and with kind regards, Michel Quote
nstein Posted June 9, 2011 Posted June 9, 2011 In the mean time you should be able to see the name of the device or folder by looking at the title bar of most web browsers. -Nick Quote
junkycosmos Posted June 9, 2011 Posted June 9, 2011 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 Quote
Illusion Posted June 13, 2011 Posted June 13, 2011 Since upgrading to 3.1.3 I have had a problem changing the back-lights in two of my KPLs. I have this done programmaticly. I am trying to determine if I have a new comm issue or if it could have something to do with the beta. I never had an issue with this before, but I did add 5 additional devices after upgrading to 3.1.3 Here is a log of the level three event viewer.: Mon 06/13/2011 04:42:44 PM : [All ] Writing 2 bytes to devices Mon 06/13/2011 04:42:44 PM : [12 3A 85 1 ] Memory : Write dbAddr=0x0264 [00] Mon 06/13/2011 04:42:44 PM : [12 3A 85 1 ] Using engine version i1 for 'Wake 3AM' Mon 06/13/2011 04:42:44 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:42:53 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:02 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [iNST-SRX ] 02 50 12.3A.85 13.24.AA 23 28 02 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [standard-Direct Ack][12.3A.85-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Mon 06/13/2011 04:43:03 PM : [iNST-ACK ] 02 62 12.3A.85 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:07 PM : [12 3A 85 1 ] Memory : Write dbAddr=0x0264 [00] - Failed Mon 06/13/2011 04:43:07 PM : [All ] Writing 2 bytes to devices Mon 06/13/2011 04:43:07 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] Mon 06/13/2011 04:43:07 PM : [F C1 DE 1 ] Using engine version i1 for 'Front Porch KPL' Mon 06/13/2011 04:43:07 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:09 PM : [iNST-SRX ] 02 50 0F.C1.DE 13.24.AA 26 28 02 SET-MSB(02) Mon 06/13/2011 04:43:09 PM : [standard-Direct Ack][0F.C1.DE-->ISY/PLM Group=0] Max Hops=2, Hops Left=1 Mon 06/13/2011 04:43:09 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:18 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:27 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:31 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] - Failed Both devices are v.2d I made a test program that just tries to change the back-lights in these two problem devices for testing purposes. Each device is on a different circuit. I do not appear to be having any other comm issues, even with other devices on those same circuits. These are the only two I am having trouble with. The regular program changes lots of switch's back-lights, but it appears to only use i2 on these two, the two I am having trouble with. Thoughts? An issue with the beta or because I changed something else in the system? Quote
LeeG Posted June 13, 2011 Posted June 13, 2011 The trace looks like a comm problem. Note the 9 second elapsed time between the commands being issued which did not receive a response from the device for the first two attempts. Mon 06/13/2011 04:42:44 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:42:53 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:02 PM : [iNST-ACK ] 02 62 12.3A.85 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:03 PM : [iNST-SRX ] 02 50 12.3A.85 13.24.AA 23 28 02 SET-MSB(02) Same thing with the other device. No response to these three commands. Mon 06/13/2011 04:43:09 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 2B 64 06 PEEK (64) Mon 06/13/2011 04:43:18 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:27 PM : [iNST-ACK ] 02 62 0F.C1.DE 0F 28 02 06 SET-MSB(02) Mon 06/13/2011 04:43:31 PM : [F C1 DE 1 ] Memory : Write dbAddr=0x0264 [00] - Failed Quote
Illusion Posted June 13, 2011 Posted June 13, 2011 Thanks Lee. I will see what I can do. Querys on the devices only are loosing 1 hop most times. Having trouble getting consistent results though. Quote
LeeG Posted June 13, 2011 Posted June 13, 2011 A technique that has been useful is to connect a wired device to an Appliance cord that has a plug on one end and bare wires on the other. Plug the Appliance cord near the PLM and see if things improve. I would expect good communication when receiving power near the PLM. I have not seen a device that would not at least ACK the basic Set MSB, Peek commands (except for motion sensors and triggerlincs which are exceptions to keep memory size small). The Set MSB and Peek commands have been Depreciated for years but there is so much software in existence today that uses these commands I really don’t think Smartlabs did away with them for KPLs. Also a few of the commands were ACKed even though the majority failed to get any response. Quote
Illusion Posted June 13, 2011 Posted June 13, 2011 Something else is going on here. I am not sure what. I pressed the buttons on the 3AM KPl approx 50 times. All showed up in the event viewer with 2 hops left, no button presses missed. Quote
Michel Kohanim Posted June 14, 2011 Author Posted June 14, 2011 Thanks LeeG for helping Illusion! junkycosmos, most of those errors are mostly network related. It seems ISY has a hard time getting out to the Internet. With kind regards, Michel Quote
evilpete Posted June 14, 2011 Posted June 14, 2011 junkycosmos, most of those errors are mostly network related. It seems ISY has a hard time getting out to the Internet. l I am getting the same error a lot also ( if 12->25 times a day is a a lot ). I dont think it's a problem but thought I would mention it just in case. Quote
junkycosmos Posted June 23, 2011 Posted June 23, 2011 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 Quote
Michel Kohanim Posted June 24, 2011 Author Posted June 24, 2011 Hello junkycosmos, I think the problem with MobiLinc has already been addressed by a new version of MobiLinc. As far as the error log entries, those errors do NOT necessarily mean lack of Internet connection. They mean different things based on the error codes such as: - The server did not respond - The server responded with bad status - Can't resolve server name etc. For a list of errors and what they mean please consult: http://www.universal-devices.com/mwiki/ ... r_Messages With kind regards, Michel Quote
junkycosmos Posted June 24, 2011 Posted June 24, 2011 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 Quote
Michel Kohanim Posted June 26, 2011 Author Posted June 26, 2011 Hello all, Release 3.1.4 (Beta) is now available: viewtopic.php?f=25&t=6547 With kind regards, Michel Quote
Illusion Posted June 26, 2011 Posted June 26, 2011 Sorry this may be a bit late, but I am having difficulty with the event viewer. It will be sometime before I can download and test on the latest firmware so I will report here. If I select level 3 (whatever that is called now) and then try to drop back to level 1 it still shows level 3 info. If I select none, then select level 1 or 3 the event viewer will still not propagate information. I have to reopen the event viewer from the tools menu to get it to work. I have also found I have to select my desired info level before opening the new window because it will open to the last selection and then I cannot change it, except to level 0 (none) successfully. Quote
Michel Kohanim Posted June 26, 2011 Author Posted June 26, 2011 Hi Illusion, Thanks so very much. Verified as bug and unfortunately it has to wait till 3.1.5. With kind regards, Michel Quote
Illusion Posted July 6, 2011 Posted July 6, 2011 I had a switchlincrelay (SWR) go wonky on me. I did a factory reset and restore from the ISY. The switch seemed bad. It would not respond to any of the scenes it was a member of. I did a link table comparison and the ISY showed it should have a single link, to the PLM. But the ISY knows that this device is a member of a whole bunch of scenes. I had to remove/re add the device and re-assign it to its scenes. Why would the ISY not know about needed links for scenes the ISY knows the switch is part of? I restored a KPL recently and sure enough it does not appear to have all its scene info either. Link table comparison shows correct, but that does not mean anything if the ISY link table is incorrect. Thoughts? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.