heyfrank Posted February 23, 2012 Share Posted February 23, 2012 Anyone having any issues with their Dualband Dimmer switches reporting the correct on/off status? I just started to notice the issue when I have taught my ISY to send a text message when the status is turned to "on"... Link to comment Share on other sites More sharing options...
Michel Kohanim Posted February 24, 2012 Share Posted February 24, 2012 heyfrank, In ISY programming vernacular On = 100%. If you want to be notified of any level, the please use Not Off in the condition. With kind regards, Michel Link to comment Share on other sites More sharing options...
heyfrank Posted February 25, 2012 Author Share Posted February 25, 2012 Michel, Thank you for the reply and kind words. Although, it still does not function the way I expected, and I still do not get a text when the kitchen light is turned on. Here is the program I've written, can you please glance over it and tell me if you notice anything out of the ordinary? Thank you Frank Link to comment Share on other sites More sharing options...
Michel Kohanim Posted February 26, 2012 Share Posted February 26, 2012 Hi Frank, Thank you. Just a quick question: do you know that Wait can be interrupted? This means that while you are waiting, if the condition turns to false, the program stops and does not execute the next statement. Do you have problem with other notifications (if any)? With kind regards, Michel Link to comment Share on other sites More sharing options...
heyfrank Posted February 26, 2012 Author Share Posted February 26, 2012 I did not know this, I will try it without the wait command and get back to you. Did everything else look fine? Link to comment Share on other sites More sharing options...
heyfrank Posted February 26, 2012 Author Share Posted February 26, 2012 Reporting back... still not as accurate as I'd like it to be, whenever it's physically turned on (the switch is connected to a chandelier) it still does not report the correct status in the isy web interface some of the time, and i still only get the text 50% of the time, and usually only when I control it through the web interface or isy interface admin. any ideas why? Link to comment Share on other sites More sharing options...
LeeG Posted February 26, 2012 Share Posted February 26, 2012 Watch the device status under the Admin Console as the switch is turned On and Off at the switch. If the Admin Console status does not track exactly that could explain the lack of email as the ISY is not aware of all the switch operations. The actual command flow from the device can be viewed using Tools | Diagnostics | Event Viewer with Level set to 3-Device communications events. Likely the event viewer will not show device traffic when the Admin Console does not show a device state change. Assuming this is not solid, that is, the event viewer never shows traffic from the device, there is likely a comm problem between the device location and the ISY PLM making communication unreliable from that location. Link to comment Share on other sites More sharing options...
heyfrank Posted February 26, 2012 Author Share Posted February 26, 2012 I will check it out. I can control the device on/off and even dim from the admin console and all that, just not get proper status from it. the PLM is only about a total of maybe 20 feet from the PLM and ISY. Also, yes the device status isn't always correct in the admin console. I will check into the event viewer once I have a few free minutes. Keep in mind also that when I did have my SmartLinc before my ISY, the status worked perfectly fine. Link to comment Share on other sites More sharing options...
LeeG Posted February 26, 2012 Share Posted February 26, 2012 If device status changes are never reported then the link records in the device and/or PLM are suspect. If device status changes show some of the time and not others then communication from the device to the PLM is suspect. EDIT: I was not aware the SmartLinc kept track of device initiated state changes. The SmartLinc would have to be a Responder to each device which is not established by Set button linking the devices as Responders to the SmartLinc. Link to comment Share on other sites More sharing options...
heyfrank Posted February 27, 2012 Author Share Posted February 27, 2012 It looks as though in the event viewer the communication seems to be fine. I've attached two screenshots if they help any... Link to comment Share on other sites More sharing options...
LeeG Posted February 27, 2012 Share Posted February 27, 2012 The link record in the PLM is missing or corrupted. There should be more messages for each button press if the links were correct. The above was when I thought the test was the requested in-bound test. There is information on link records until the inbound test is run. Those are outbound messages initiated by the ISY. Press the button/paddle on the device itself. Link to comment Share on other sites More sharing options...
ScottAvery Posted March 2, 2012 Share Posted March 2, 2012 Side note: Not sure if it is acceptable to state it here, but Amazon has the dual band dimmers on sale 15% off today. Only a couple dollars more than an access point. Link to comment Share on other sites More sharing options...
dgruehn Posted March 28, 2012 Share Posted March 28, 2012 Any resolution to this thread issue? I am having the same issue - devices not showing correct status in Admin console. Firmware: v3.2.1 UI: v3.1.17 Link to comment Share on other sites More sharing options...
LeeG Posted March 28, 2012 Share Posted March 28, 2012 dgruehn The UI and Firmware lines must show the same values. It indicates the Admin Console is from 3.1.17 and the ISY is running 3.2.1. Either the Java cache was not cleared or the URL to access the 3.2.1 Admin Console is not being used. Don't know if that mismatch would cause the results you are seeing but this should be resolved immediately before doing anything else. Then see what the results are. There are many causes for not seeing device status updates. Link record problems in the PLM and/or devices, powerline interference, powerline coupling issues, are some. Link to comment Share on other sites More sharing options...
dgruehn Posted March 28, 2012 Share Posted March 28, 2012 dgruehn The UI and Firmware lines must show the same values. It indicates the Admin Console is from 3.1.17 and the ISY is running 3.2.1. Either the Java cache was not cleared or the URL to access the 3.2.1 Admin Console is not being used. Don't know if that mismatch would cause the results you are seeing but this should be resolved immediately before doing anything else. Then see what the results are. There are many causes for not seeing device status updates. Link record problems in the PLM and/or devices, powerline interference, powerline coupling issues, are some. Thanks for the quick response. My bad.. I was using the wrong URL... called the ISY by the IP address, got the right admin console, but still encountering the issue: - I moved my PLM into the garage right next to the switch box - The devices are all Insteon dual band and were working fine with v3.1.13 - I have a SignaLinc plug-in phase coupler and am using 4 Insteon repeaters (4000 sq ft home) - I have 160 Insteon devices. All were working well in dual band with v3.1.13 - If I query the device in the Admin console the correct status is displayed - Device control is working fine in the admin console I should probably know this put is there an easy way to "fix" or rebuild the Link records/table? Link to comment Share on other sites More sharing options...
LeeG Posted March 28, 2012 Share Posted March 28, 2012 dgruehn To restore the entire PLM link database do a File | Restore Modem (PLM) function. If you have RF only devices do not put them into linking mode. They may produce failures during the Restore process but that is okay. When the Restore Modem (PLM) is fully complete look at the RF device nodes in the My Lighting tree to see if any are marked with a Red ! or Green Icon to the left of the node name. If so put only one of the RF device into linking mode, right click on node name and select Write Updates to Device. The RF devices have to be done one at a time to avoid one device cancelling the other out when put into linking mode. There are a couple of items that stand out in your last post. You mention SignaLinc plug in couplers. Are these actually SignaLincs with the black external antenna? If so they do not couple extended commands and they operate on a different RF frequency than all the other Insteon RF devices. A device Query and device control through the Admin Console use Insteon Direct commands which do not use link records. There can be issues with the link records in the PLM and/or devices and still have Query and device control work. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.