LeeG

The Admin Console Event Viewer (Tools | Diagnostics | Event Viewer) with the Device communications events option selected provides the most detail available. With a 10 second interval between the Scene running and the device status of Off there may be another Program that is being triggered by the change in device(s) status. You can also right click on the Scene name and run a Diagnostics | Scene Test. This test is more extensive regarding Insteon commands issued. If another Program is causing the problem the other Programs can be disabled to see if the problem stops.

Sounds like a good idea. I agree that the difference between a 9 minute and 8 minute ramp up is not perceptible.

Avonlea22 Smarthome/Smartlabs are constantly adding/removing/tweaking function of the Insteon devices. The Smarthome user forum is a good place to frequent as rarely is any official statement made from Smarthome regarding changes. Lee

Tests of the low battery function on one of my motion sensors shows it tripping the low battery Group 3 On message in the low 4V range. I do not use it to send an alarm/alert but it could be used for that purpose. There is no counterpart Group 3 Off message when a new battery is installed. There are folks on the Smarthome forum who report using the battery eliminator successfully. Turning the LED Off for motion does not stop the LED from flashing when a responder ACK is not received.

I ran into this during my Search for similar symptoms. For a list of firewall remedies, please peruse this forum: http://forum.universal-devices.com/viewforum.php?f=3

After searching for similar situations there is a common theme that comes out. Firewall issues can cause a similar situation. Since it appears that the Device State is always blank it would seem more logical a configuration issue rather than the very intermittent Admin Console problem. Also I think the 32 bit Java is required even on 64 bit machine.

There is a thread (I think) that receives notifications from the ISY when status changes and commands execute. With no Device State information and no Event Viewer events I think they are related symptoms. Some issue with the Admin Console communicating with the ISY through Java. Are you Windows or Mac? Just curiosity? I have never seen the Admin Console not come up correctly after one or two tries. I have no suggestions on how to resolve it. Perhaps someone else or UDI can suggest a solution.

All blank Device State fields is not a device communication problem, particularly when Query does not resolve it. I see it at times when it is the first time starting the Admin Console in awhile. After that it generally comes up fine until it has not run for awhile. Like a timing problem when it has not run for awhile. Do you start the Admin Console with a URL or through the initial HTML screen? If with a URL it may not be that of the latest Admin Console.

Is the Current State field blank or it shows some On/Off state but is not being updated when the device state changes? Any chance the Java cache was not cleared after an update or the wrong URL is being used to start the Admin Console? That can result in the device status not being updated.

Try restarting the Admin Console. There is a glitch which I think UDI said is fixed in the next Beta drop where the Admin Console does not show any device state. I see it once in a while. When the Admin Console comes up without device states I just restart it until it does. Normally one restart resolves the problem.

Turning the relays On/Off through the Admin Console or Programs do not show the relay state with the Admin Console?

Sure, happy to. I suspect something happened during one of the earlier add attempts that damaged the Admin Console instance and aborted the add process. Since the Admin Console was affected I doubt it was device specific but that is not based on objective information. With no Controller nodes for the EZIO8SA and some of the Responder nodes not functional (relays) I hate to say this but there is no recovery from that besides Deleting the device and doing another add. Perhaps at some time after the water has been adequately returned to normal so that there are some hours to try again. If attempting again in the future have the Event Viewer running with Device communications events selected. The Event Log will be pretty large as 15 nodes with associated link records are created during the add process. Event Log will likely be too large to post. You can send the Event Log file to lwgwork@embarqmail.com if it fails again. Perhaps I can see something as it is happening. If it is Admin Console related it may not show in the Event Log.

Are the My Lighting devices showing On/Off status and reflect new changes when turned On/Off at the device? Whatever the issue it has nothing to do with the EZIO8SA at present, If no commands are logged the ISY make no attempt to talk to the device. Perhaps something happened or was wrong before when the invalid address format message was issued that has hung up the ISY. Try unplugging the PLM and ISY power supply if there is one.

DO NOT use start linking. Select Link Management | New INSTEON Device Enter Insteon Address, Name of your choice, from Device Type pulldown select [07.04] Compacta EZIO8SA: Insteon I/O Controller. Select Remove existing links Radio button Click Ok I suggest starting Tools | Diagnostics | Event Viewer with Device communications events selected before starting add process. That way if it is unsuccessful there will be documentation of the add process.

Use firmware 2.8.x and above. Use New INSTEON Device Enter Insteon Address, Name, and Device Type of EZIO8SA. It will take a few minutes. There will be 7 Controller nodes and 8 Responder nodes when the add is finished.

I would try it with the PLM you have. Simplehomenet markets an EZIComm which is a functional equivalent to the 2412S PLM including the 12V to power the EZIO8SA. They may also still have 2412S PLM in stock.

No resisters needed. Connect the EZIO8SA GND connection to AN1 and AN2 Inputs. I have no experience with a PLM at firmware 28. It must have had lots of dust. The newest PLM I have has firmware 92.

Use Wordpad to view the file. Copy portion of Event Log associated with Motion Sensor add to clip board. Paste clipboard into post.

Why do you think there should be an incorrect address format message? Is there some doubt about the Motion Sensor Insteon address? If all the information is entered into New INSTEON Device popup suggest moving the Motion Sensor closer to a Dual Band device. As a diagnostic run Tools | Diagnostics | Event Viewer with Device Communications Events selected. Then attempt add of the Motion Sensor. Post the Event Log after device add is unsuccessful.

According to the ISY User Guide a solid RX LED indicates a PLM communication problem. Suggestion is to unplug PLM for 10 seconds. Also check cable between ISY and PLM. Not sure if the TX LED also being on means something else.

Davonavo Use New INSTEON Device; specify Address, Name, and Device Type as Insteon Motion Sensor. Be sure the Motion Sensor is in linking mode by pressing Set button. Normally a popup is displayed as a reminder to put the Motion Sensor into linking mode. Lee

If the issue is with the EZIO8SA generating Insteon traffic unplug the EZIO8SA PLM. As a temp fix connect AN1 and AN2 Inputs to GND which will lock the Inputs ON and stop any cycling that may be happening on those Inputs. To use AN1 and AN2 in digital mode they need to be connected to +5V with 10K 1/4 watt pullup resisters. This turns each Input OFF. To turn each Input ON connect the Input to GND through a dry contact switch, leaving the pullup resisters connected. The challenge with the EZIO8SA is that it provides 12V DC, not 5V DC. A 5V DC power supply circuit is required which can be powered from the 12DC. There are fixed 5V regulators that can do that job. EDIT: Radio Shack carries a fixed 5V regulator Item # 276-1770, can ordered online.

Connect Inputs AN1 and AN2 (Inputs 5 & 6) to GND. These inputs do not have a pullup resister built in because they can be run in Analog mode. As such they are floating and may generate Insteon traffic that can interfere with adding the device to the ISY. The EZIO8SA Device Type must be selected when adding it to the ISY. Auto Discover cannot be used with SHN devices. ISY firmware 2.8.x or above must be used when adding an SHN device to the ISY.

Yea Michel, what are you referring to? I assume Michel did a free hand of what should have been a Set Scene to change the On Level and Ramp Rate in the Responders link record. The Insteon Direct On command cannot affect Ramp Rate.

Avonlea22 Insteon Direct device On command controls the Level (On Level) only. The Insteon Direct device On command has no place holder for Ramp Rate. Lee