Brian H

From the UDI wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights

Smarthome was very consistent with using the same cable. They where also used in the serial port connections on their X10 modules. Though some of the other pins in the RJ45 style connector where varied signals.

Yes it did have the RJ45 to DB9 serial cable in the box. Only three wires used. Hidden in the shipping cradle and not well pointed out.

Good information. The wide input range may definitely show less flicker.

Electrical feed to the home probably has issues. Electrician or power company checking maybe needed. If you don't have a meter or experience in properly and safely checking the readings yourself. If you have any plug in lights. Do they also flicker when directly connected to the outlet and not through the module? Are any dim and others extra bright? Appliances not on Insteon acting strange?

An FCC Type Acceptance number on the module. Would also indicate it was Dual Band with an Insteon RF Transmitter circuit in it.

The V2.3 was the first revision I have see with C7 and C13 changed to a capacitor made for a switching supply. I would still think of the PLM as a possible problem. Especially if a power off and cool down would make it work again. Empty or almost empty Link Database would be another clue. Having to Query the modules to show their present state maybe normal. If the ISY controller does not know the modules present state at power up.

You could also do a Query from the Administrative Console and see if the tripping also happens then.

I too have seen the same model LED bulbs act differently as the main model number was the same but the manufacturer changed the design in later produced units.

If you have a ZWave board. Pay close attention to where the older board support was ended. Later version if you have a ZWave board only work with the new board. So you would need which board you have before picking a firmware version.

The power LED is connected directly to the ISY994i's power supply so nothing controls it On or Off. Either the LED itself has failed or the current limiting resistor is opened. I looked at the photo in the how to add a ZWave module to an ISY994i. The LED is a separate LED assembly on a 90 degree frame. Looks like an LED assembly as I have them in other devices. I opened up my spare ISY994i and did not see a screened part number on it. It is a through hole mounted LED. Soldered on the bottom of the board. The others are also individual assemblies that I originally thought where one long assembly. I would suspect the LED itself first as it seems to be very bright on mine.

Good to see you found the problem. I have seen some posts where a 4.xxx to 5.xxx sometimes needed manual intervention.

Either the EZIO8SA programmed the EZICOMM wrong, the EZICOMM has issues, you accidentally got the reply read incorrectly. The reply after the reset looks correct. Wait for your package and see if their is any differences. Factory Reset is different and explained in the Quick Guide in the box.

I would second the power supply check. They can cause all kinds of strange things when they start to get flaky.

I am not too sure on the Factory Reset as my old EZIO8SA factory reset was for a 2412S and the one I found on the Smartenit site also looks like for a 2412S base. I know they went back to a 2412 base from a 2413 base. When they had power supply issues like we did on our 2413S PLM. It didn't get programmed correctly or not at all. You may want to try a factory reset on the EZICOMM and then read it again. Hopefully the 02 73 will then return the 02 73 00 00 00 06 Your 02 73 is completely wrong. The last two bytes before the 06. Should never be anything but 00 00. Unless Smartenit has done something not allowed by the Developers Guides information. If you have not tried a different cable between the EZIO8SA and the EZICOMM. You may try that

This is from the guide on their site and sounds like the older 2412S. As it didn't have a beeper or two color Set LED 1) Unplug PLM for at least 10 seconds. 2) Press the SET button while plugging the PLM back in and continue holding SET button for 3~5 seconds. 3) Release Set button when buzzer stops. 4) LED will go out for one second and come back on when reset is complete Your method sounds like the proper newer ones with a 2413S based EZICOMM. That sounds correct about the sequence. After the reset the EZIO8SA should program the EZICOMM. From what I have read. Resetting the PLM when the EZIO8SA is connected also resets it. Though just the EZICOMM maybe all that is needed. After it programs the EZICOMM remove it from the EZIO8SA and see what the PC programs shows for the Get Configuration 02 73 shows. It should be 02 73 80 00 00 06 if it got programmed.

After you are able to see if the EZIO8SA has programmed the EZICOMM. We may have a better handle on what the problem is. I looked at one of your previous posts. The back photo shows the EZICOMM is a base 2413 Dual Band Module. So one more thing to consider is it has power supply capacitors just like we see in our 2413S PLM.

OK lets try this. Factory reset the EZICOMM and EZIO8SA. Power them back up and let the EZIO8SA reprogram the EZICOMM to look like a EZIO8SA. The LED on the EZICOMM should also pulse during the reprogramming. Take the EZICOMM and connect it to the PC with out resetting it. In the DockLight program PLM.ptp The Get IM Configuration 02 73. Should get a reply back of 02 73 80 00 00 06. If it was reprogrammed by an EZIO8SA or a 02 73 00 00 00 06 if it was not reprogrammed. I found the Get Version 02 60 always reports it is a PLM even if reprogrammed but the Get Configuration 02 73. Would be 02 73 80 00 00 06 if it was programmed and not the default 02 73 00 00 00 06.

Sounds like a good choice. If the adapters can be set to what polarity is on the Tip. It is + positive voltage on the Tip and negative on the outer barrel.

Maybe a recap would help. In your log file posted in the early messages. It showed the EZIO8SA with EZICOMM. Reporting it was a category 03 subcategory 2A. That is a PLM from Smartenit as the 2A is not one used by Smarthome and probably given to Smartenit as a third party device. I would have expected the 03 2A would have been caught earlier before the Administrative Console tried to add it and not program all the relay and input links in the module before giving the unsupported device message. It should have been 07 04 if reprogrammed. The flashing of the EZICOMM Set LED may give a clue to the programming data being sent and properly received by the EZICOMM from the EZIO8SA. Our tests where trying to see if the EZICOMM was being set to 07 04 and not the default 03 2A. Though not 100% conclusive. As you have found out.

When you had the older 2412S connected to it. The power was sent through the serial cable and was closer to 20VDC. No wall wart needed. I believe it has a switching supply with a wide range for the DC input.

I agree. A dimmer controlling an outlet is a bad idea and against the electrical code. One wrong load connected and you may have sparks or failure of the device or connected device.

Step 4. The LED on the side of the EZICOMM should flash a few times if it is communicating with the EZIO8SA and setting the EZICOMM. The network style connector on the ISY994i,EZICOMM and EZIO8SA all are serial signals not the normally used network signals. You normally find on a RJ45 jack. When you have the EZICOMM connected to the PC with DockLight. You can use the PLM.ptp file to see if the EZICOMM will respond properly. The EZIO8SA uses a PLM or EZICOMM. To be used in the system. The Smartenit program needs it own interface to run. So you need a PLM or EZICOMM on the EZIO8SA and another one on the PC. So you need two PLM units. One for the PC and another for the EZIO8SA. With no PLM on the EZIO8SA but on the PC so the utility runs. It can open the program but will not connect with an EZIO8SA with no attached PLM or EZICOMM. Does the LED on the EZICOMM flash when you start up the connected EZIO8SA flash a few times? That should show if the two units are communicating and should be setting the EZICOMM to report it is a 07 04 module and not the default 03 2A. Are you still getting the messages you posted in a previous log file. Where it tried to add the module and got many communications listed. Normally I would expect the unsupported device would show up quickly if the device was not in the ISY list of known devices. Not the whole sequence of commands before calling the unsupported device. Have you tried connecting the EZIO8SA to the EZICOMM and letting it initialize? Then connecting the EZICOMM to the PC and seeing what the 02 73 command reports? With out resetting it first.

I checked my notes and Developers Guide. I have a correction. With the EZCOMM programed by the EZIO8SA. The 02 60 command will still return the 03 2A with the 02 60 command but to the outside world. Like the ISY994i it should report it is a 07 04. If programmed by the EZIO8SA the command 02 73 should report a 80 if it was programmed by the EZIO8SA. On mine at power up of the EZIO8SA. It sets the Host Category to 07 04. Turns off the Automatic LED control and Local Set button linking, turns the Set LED off, turns the Set LED on, turns back on the Automatic LED control and leaves the Local set button linking off. When turned on. The LED on the side of the EZCOMM should flash off and back on if the EZIO8SA is programming it. Another clue would be a programmed EZCOMM reporting a 80 with the 02 73 command if it was programmed or a 00 if not. In your Hyperterminal showing @@@@@. The PLM uses HEX for messaging. If you are sending ASCII that maybe the reason. The preset DockLight ptp file is set to send HEX.

The Smartenit program uses its own connected interface. PLM both 2412S and 2413S. May also use a 2412U or 2413U that I never tried. The older 2414S PLC or maybe the 2414U USB PLC. The PLC also needs the SDM3-308 Smarthome Device Manager. SDM3-308 was in the utilities download package. Maybe too old for Windows 10. Their EZServe or EZICOMM. With the EZIO8SA it still needs its own PLM or EZICOMM and the program needs it own interface. So you need a interface separately for the program to access the EZIO8SA. Your utility display shows not connected so you can't do anything with the EZIO8SA. I believe since it has no interface connected to the EZIO8SA and the interface is being used by the Utility. Your PLM.ptp display. 02 60 Get IM Info. 1E 7F 33 6 digit Insteon ID. Category 03 PLM. Subcategory 2A (I think id is a Smartenit id). 9B firmware version. 06 ACK command processed correctly. You may want to run the PLM.ptp on the EZCOMM after you have it initialized by the EZIO8SA and not reset. The 02 60 Get IM Info results should now show the category and subcategory for the EZIO8SA and not the PLM data.