Brian H

Glad you got it working again. Your reported finding may assist someone else with the same issue.

The closest Insteon modules. Would be the alert module and siren module. The siren module has a chime function also. Of course both are no longer in production and the alert was a real short time production device. You can still get the X10 chime module if you don't find something else.

Good idea. Though in my case it probably would not show much. I came from X10 use and have a JV Digital XTB-IIR. Coupler Repeater in use. It blasts over a 20 volt signal back on both phases of the house power. My lowest X10 signal is about 1.2V on an XTBM meter. It also knows enough to NOT see the end of an Insteon command and try and duplicate it as an false X10 command. I still have an X10 Palm Pad in use the control some of my Insteon modules that can have an X10 address added to them.

Your second question. The 2868-222 Siren Module It is a very Loud Insteon triggered siren. I have one in use. I left the sound reducing plastic film over the siren output port. As that is loud enough for me. It also has a chime function but I have no experience with the chime function. It may have been one of the early removed modules. There was a 2867-222 alert module also. It was an very short production run before the later siren module was released. It had a chime like output sound. Broyd made a very important point. The X10 chime module has a power line derived power supply. Either the + or - side of the power supply is directly connected to the HOT line input and logic supply.

Trying it in the same outlet as the PLM. Is a good idea. It would show if you have a power line signal to the Chime Module problem. If it chimes at the PLM location. You may have a new signal sucker or power line issue. One easy thing to do. Rotate both the House and Unit Code wheels around a few times. They sometimes get dirty and make a bad connection. So the address set on the wheels. Is not the addresses the module is actually using. Rotating may clean up a poor connection. The chiming at power up is normal but does not see if it actually will respond to an X10 On command.

The failing power supply. May have caused the controller to write garbage to the SD card. Power supply issues are a failure we see here. I had a few over the years myself. Glad you are back in business.

LED flashing in the bar graph display. Sounds like the power supply is full of ripple. I too would suspect the filter capacitors. Especially in the older model power line only models.

Glad you found the issue and are now working.

You need a 2413S serial port PLM. For use with an ISY994i. Connected to the serial connector on the PLM. It looks like a Network RJ45 cable but it is serial signals. Uses a network style cables between the PLM and the ISY994i serial connector Port A connector.

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.