jtara92101 Posted November 2, 2010 Share Posted November 2, 2010 -11022 Couldn't open file /conf/fyp.cfg -11022 Couldn't open file /conf/adr.cfg Flash corruption? Restore ISY? I got this when trying to set-up a new scene. I got down to a particular control, and got this when trying to adjust the brightness and ramp rate. I can change other stuff. Also got "cannot communicate with device" but was able to restore the device without error! Just happens when trying to adjust anything in the new scene past what I'd already set-up. Maybe just delete the scene and start over with it? Link to comment
Michel Kohanim Posted November 3, 2010 Share Posted November 3, 2010 Hello jtara92101, Completely benign; these are configuration files for the following services (Configuration | Electricity tab) which you have not enabled: fyp = Flex Your Power adr = Open Auto DR These warnings are supressed in 2.8.0+. With kind regards, Michel Link to comment
jtara92101 Posted November 3, 2010 Author Share Posted November 3, 2010 In this case, not benign, though. I was getting this message when trying to change either the ramp rate or on level of a couple of dimmers in a scene. Now, I just get the message "request failed". Checking the log, there is no traffic generated. Now I'm getting "cannot communicate with MB Shower". Various messages at different times seemingly related to the same thing - I try to change the on-level or ramp rate of the MB shower in a scene, and it doesn't work, with these various error messages, some of which don't make sense in this context. The slider stays where I put it, but if I move to another node and then back again, I can see that the change was not made. Now despite the fact that the ISY claims it "cannot communicate" with the MB Shower dimmer, it IS able to successfully restore the device. I just queried MB Shower, and then tried again to change the on level. Here's what I got in the log. Anything unusual or incorrect here? This time I got -200000 failed to write device link, 2 times. It's a different error message practically every time! The 7 INST-ACKs below are from the Query I did. The rest of it is from my attempt to change the on level. Tue 11/02/2010 09:52:19 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:52:33 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:52:37 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:52:46 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:52:55 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:53:09 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:53:23 PM : [iNST-ACK ] 02 62 0D.75.42 0F 19 00 06 LTSREQ (LIGHT) Tue 11/02/2010 09:53:42 PM : [ D 75 42 1] RR 26 Tue 11/02/2010 09:53:42 PM : [D 75 42 1 ] Using engine version i1 for 'MB Shower' Tue 11/02/2010 09:53:42 PM : [D 75 42 1 ] Link 0 : 0FF8 [A2000F9F52FF1F00] Writing [A2000F9F52FF1F00] Tue 11/02/2010 09:53:42 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:53:51 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:00 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:14 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:28 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:32 PM : [D 75 42 1 ] Link 0 : 0FF8 [A2000F9F52FF1F00] *Failed Writing [A2000F9F52FF1F00] Tue 11/02/2010 09:54:32 PM : [D 75 42 1 ] Using engine version i1 for 'MB Shower' Tue 11/02/2010 09:54:32 PM : [D 75 42 1 ] Link 0 : 0FF8 [A2000F9F52FF1F00] Writing [A2000F9F52FF1F00] Tue 11/02/2010 09:54:32 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:41 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:54:50 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:55:04 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:55:18 PM : [iNST-ACK ] 02 62 0D.75.42 0F 28 0F 06 SET-MSB(0F) Tue 11/02/2010 09:55:22 PM : [D 75 42 1 ] Link 0 : 0FF8 [A2000F9F52FF1F00] *Failed Writing [A2000F9F52FF1F00] Link to comment
jtara92101 Posted November 3, 2010 Author Share Posted November 3, 2010 Seem to have fixed it - deleted scene and re-created it. Link to comment
Michel Kohanim Posted November 3, 2010 Share Posted November 3, 2010 Hi jtara92101, They are 1000000% benign and have nothing to do with the other symptoms. The reason you get those on the Admin Console is because they are the "last two errors". It seems to me that you have communications errors with your devices. Is it isolated to a few devices or to all of them? Does it happen all the time or only at certain times? Do you get any green 0101 icons? -20000 (cannot write high water mark) in combination with successing INST-ACK (PLM' ACK to our command) without an INST-SRX (response from the device) means that the PLM can NOT communicate with that device. With kind regards, Michel Link to comment
jtara92101 Posted November 3, 2010 Author Share Posted November 3, 2010 V35. Need I say more? Got 4 of the buggers. Oh, and one unused one in a box. Including the one I've been having the trouble with. I'll call SmartHome in the morning... (Wandered into the "communication issues" area, and recognized symptoms...) Link to comment
Michel Kohanim Posted November 3, 2010 Share Posted November 3, 2010 Hello jtara92101, Whooah ... I am so very sorry to hear. Yes, indeed quite symptomatic of V35 SWLs. On the bright side of the coin, you should feel lucky that they are impacting communications with other devices. In most cases, those SWLs actually cause communications errors on unrelated and perfectly functional devices. Good luck! With kind regards, Michel Link to comment
jtara92101 Posted November 3, 2010 Author Share Posted November 3, 2010 Actually.... I was wrong. I got confused - they are in the other bathroom. The switch I am having trouble with is V27. But I do have 4 V35 SWLs in the system. Among the oddities is a new dual-band lamplinc that doesn't seem to bridge phases most of the time. It's sensitive to where I plug it in. In certain locations an old access point works just fine. Replace it with the lamplinc and no bridging. But seems to work in other locations. I OFTEN get "flashing" of the LED when I press a button that is linked to something. Should the V35s be RMAd? I actually have enough V36s to replace them all, because I just recently got 4 more SWLs, and hadn't installed them yet. I can hold-off installing the new locations until I get replacements. Link to comment
Michel Kohanim Posted November 3, 2010 Share Posted November 3, 2010 Hello again jtara92101, I strongly recommend getting your V35s replaced. From past experience I can tell you that most, if not all of the communications issues will disappear when these units are no longer in the network. To test my hypothesis, simply pull the set button out on these 4 switches (so that they are offline) and retry your tests. With kind regards, Michel Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.