Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Brian H

Members
  • Joined

  • Last visited

Everything posted by Brian H

  1. This is part of the Smarthome Forum message. They thought a 302545 may just fit. "For what it is worth, the battery in the Mini Remote is accessible and looks like it can be replaced fairly easily. The LIPO (3.7v) battery has a capacity of 300mAh and measures 3mm tall, 25mm wide and 45mm long. For search and id purposes these dimensions are typically denoted as "302545" Clearances within the mini are fairly tight so I'm not sure how much variance from these measurements is tolerable."
  2. I will see it I can find the battery number. Used by a poster on the presently off line Smarthome Forums. The exact battery in the remote was not available so they found a close replacement. That seemed to work fine for them. I too have seen different posts on tabs glued or not. May have been a production change. The internal and external photos of the remote are in the FCC Database in the link in this thread.
  3. Glad it is now working for you. I suspect when you squeezed the casing you put some side pressure on the cables contacts and they made better connection now.
  4. It is a Micro-USB connector. Take a look inside the jack on the remote and you will see the contacts. The plug on the charging cord has the flexible contacts that connect to the contact points inside the jack. The soldered points could be flaky between the jacks contact strips and the solder pads on the board. Though I would suspect the contacts in the charging cord. The photos are in the FCC Database. Including the internal and external photos. SBP Grantee, 23422 product code, in the details tab. https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm
  5. There was a thread on the presently gone Smarthome Forums. From a user that changed the battery that would not hold a decent charge. They gently unsnapped the clips and opened it. I have seen reports that some had a small dab of glue on the snaps. The USB connector is a soldered on part and I don't know if you can squeeze the contacts. I have a jpg file of the inside of the remote and I can see if I can get it here.
  6. They didn't offer updates. Didn't want to release the firmware files and you would need a programmer or did not want the hassle of taking a module back to reprogram them. I believe the chips have a copy back fuse so an unauthorized person could not read back the file and use it for more chips. The unique six digit would be changed in each module. Except the special Developers Module. They all have the same six digit ID so their canned Docklight Scripting file worked for all the developers modules. I have a few of the version 1 access points. They took back our Signallinc RF units and it looked like they reprogrammed the processor and swapped out the RF board. For a fee that is.
  7. Unless Microchip is making the PIC Microchip preprogrammed for them. The chips are the standard ones off the shelf and programmed by Smartlabs manufacturer. Every module has a 5 pin programming connector so the IC can be programmed locally with the proprietary source file. The PLM has two as their is one for the main controller and one for handling the RF communications. Peel off the label on a chip and you would probably find its generic part number.
  8. Did you use the special boot link if the SD card was fresh and no firmware was on it yet? https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card
  9. Would be easier to purchase one from Smartenit. If you assemble it then you could probably easily reverse the RS232 #2 and #3 to look at the signals out of the EZIO8SA side of the equation. To just see if they are talking to each other. The LED on the side of the EZICOMM should flash a few times at power up as it reprograms it to ID as a EZIO8SA and not the native EZICOMM ID.
  10. If the LED pattern is not following the sequence in the wiki information but are constantly flashing. It could also be a power supply going bad. If they are always flashing. The power supply maybe going bad. I had a unit doing the same thing and a replacement supply fixed it. Supply may have enough power to keep it sort of running but the reboot kept the supply going on and off. There are also other posts here where the supply was the problem. If your supply has an LED on it. It maybe flashing if the supply is cycling on and off or it has too low an output. The blue power on LED is run directly from the ISY994i internal supply. It should be on all the time. If it is also flashing another reason the wall wart is probably gone. ISY994i has a input range of 5VDC to 30VDC. Center pin positive. Most here go for a 12VDC 1A or 2A. When I looked UDI has a 12VDC 2A replacement on their sales pages. Mine had a 5.5mm barrel with a 2.1mm pin.
  11. The photo you posted yesterday. Is the back of the EZICOMM used for the EZIO8SA correct? The FCC tested label on the back, the two prong AC Pins, factory reset beeps and address showing in your EZIO8SAAdd.txt match the photo's label. Would indicate you have one built on the 2413 base PLM assembly. So it is subject to the same power supply capacitors issues many of us have fought with for years. The cable in the box will allow you to test the EZICOMM with DockLight Scripting. The EZIO8SA would need the cable modified. Because the send and receive signals are reversed between the EZIO8SA and EZICOMM. Smartenit still has some of the cables on their sales site. https://smartenit.com/shop/plm-serial-cable/ I had a chance to look at the information the EZIO8SA sends to its PLM/EZICOMM. It sets the ID to 07 40, another command turns off the Set LED on the interface, then turns it back on and resets the configuration to disable the Set Button from doing local linking. So when you power it up part of the startup should flash the EZICOMM LED from on to off and back on.
  12. More information in this thread and the PLM.ptp program. https://forum.universal-devices.com/topic/37499-polisy-doesnt-boot-if-connected-to-powered-insteon-plm/#comment-344167 Docklight Scripting is on this web site. Evaluation copy is free to try. https://docklight.de/downloads/
  13. The "PLM.ptp" program for DockLight Scripting Evaluation program should have all the setting in it already. Except maybe the COM port if not 1. In that case you pick Tools, Project Settings and change the COM port number. It may ask to save changes but it will not as the evaluation version has a few features disabled like save and print.
  14. I would add one more item. The power supplies used by the ISY994i have some reports of them failing. I have had a few from the older ISY99i and ISY994i. The ISY994i has a large voltage range input. 5VDC to 30VDC. I have had original 5V DC 500mA to 5VDC 1 Amp units. UDI sells a replacement 12VDC 2 Amp on their sales site. 12VDC 1 Amp or 2 Amp should be a good way to go. Especially if you have a ZWave board installed.
  15. I did a test. With an early version EZIO8SA, powered by a 12V wall wart, 2413S V1.0 PLM. Network style cable between the 2413S and EZIO8SA. Powered the PLM connected to the EZIO8SA first. Then turned on the EZIO8SA. The EZIO8SA sent some data to the PLM and its set led flashed a few times. Added it to my ISY994i. Auto found it as a 07 04 EZIO8SA. To get how the outputs working. Their was an Options Screen. Change On Level On to 100% and Ramp Rate to 0.1 seconds Outputs changed on the screen as expected. I did not use a meter to check on the EZIO8SA. I am not too sure if I had to set the options but I believe I did. On the EZIO8SA I did have the AN1 and AN2 inputs grounded. Was recommended in their now gone Silmplehomenet forums. If you are not using them. They are high impedance and will pick up stray noise sometimes. With the AN1 and AN2 inputs randomly changing level.
  16. We may have confused you. Talking a PLM. There should be two. One for the ISY994i and the second one in your case a EZICOMM connecting to the EZIO8SA. There is no connection from the EZIO8SA and the ISY994i systems PLM. The EZICOMM is a Smarthome base PLM with the Simplehomenet/Smartenit custom RS232 serial board that can have RS485 on it also as an option.. The EZIO8SA should have a network type cable between its "PLM" jack and in your case the EZICOMM. The ISY994i has its own PLM to operate. The EZIO8SA should send a few software commands to its connected EZICOMM(PLM) to change its ID to 07 04 so your system finds it as a EZIO8SA and not a 03 2A PLM. I would factory reset the EZICOMM with the EZIO8SA not powered up. Then power up the EZICOMM and let it initialize. Then power up the EZIO8SA and it should as part of startup. Send a few software commands to the EZICOMM so it identifies as a EZIO8SA 07 04 and not the native 03 2A. If it still is found as a 03 2A we have to do more thinking.
  17. 07 04 is the EZIO8SA. I can't find 03 2A in the list from Smarthome in the Developers Group. 03 is the category for a PLM and I think subcategory 2A may have been one given to Smartenit (Simplehomenet) for their EZICOMM and not in my standard list or the list is too old. Thank you for providing the 03 2A ID you found in yours. When first booted up. The EZIO8SA should send and receive a few messages to the connected PLM or EZICOMM. To change its ID to 07 04 so the controller knows it is an EZIO8SA and not a PLM/EZICOMM. Since the user has said they have a wall wart power supply. I am not 100% sure if you factory reset the EZICOMM. If it resets the EZIO8SA if not powered down by unplugging the wall wart.
  18. One thing you may want to do. Order of the power up. Power up the PLM (EZICOMM) first. Then the wall wart supply on the EZIO8SA. When it first accesses the PLM the Set Led should flash a few times as it is reconfigured to ID as a EZIO8SA and not a PLM. Not an expert on the Insteon messages but in your EZIO8SAAdd.txt it looked like it said it was a different device and the links where added to the device if found. 02 50 1E 3F 33 03 2A 9B. 1E 3F 33 is the Insteon ID for the module connected to its PLM. 03 is the category for a PLM, 2A subcategory is not on my list but typical of a PLM and 9B is a firmware version.
  19. My probably first run EZIO8SA with a 2412S powering it and interfacing it. Did not work with the Auto Find. I had to pick from the drop down list. Mine used the original I1 peek and poke messaging. It may have been identified incorrectly. As I had options like ramp rate and on level options that I would think where a dimmer choices. 5.0.16C software Outputs did noot work until I set the Ramp Rate to 0.1 and the on to 100%. The EZIO8SAAdd.txt file in the thread show it used the later I2CS messaging and was successfully added though they reported a unsupported device? Docklight is still around and I posted a file here to do a few basic PLM tests. It was one of the version of the test files we got in the Developers Group. That I modified to do what I wanted as the originals where for the hardware kits you could buy. Like all the module in every kit had the same six digit ID. The Docklight you download is the evaluation type and making and writing files is locked out. Much studying and testing showed a plain text editor would modify and save my PLM.ptp file and Dockllght could use it. I did a few things like send an X10 On and Off to a test chime module, do a PLM ID, do a PLM get configuration, display the first link database entry, display next link database entry and the one you used with care send a software factory reset command to start fresh.
  20. The RJ45 jack on the PLM may look like network connector but it is a serial, TTL and power if a older 2412 PLM. The serial cable in the box. RJ45-1 to DB9S-2, RJ45-7 DB9S-5, RJ45-8 DB9S-3. Do not connect or short RJ45 3 and 6 they are the TTL level PLM signals and 2 on a 2412 12Volts unregulated. 19,200 baud,8 data bits,no parity,1 stop bit and no handshakes. The EZIO8Add.txt file you posted. Shows it was successfully added and it wrote the needed links into the EZIO8SA. I will study the file and try and tell what it ID as. After studying you earlier posts. I think you do have a 2413 based Dual Band PLM (EZICOMM) . The older 2412 didn't have the beeper you mentioned. Simplehomenet may have a 2413 based unit with the pass through AC outlet that a 2413S did not have. One of your logs also showed a firmware of 9B. That is one of the Dual Band PLM firmware versions. As for my mentioning the need to set options on my very early EZIO8SA. The options where more for a dimmer not a on off relay type module. As they don't use a ramp rate or on level. They are just on and off.
  21. The EZIO8SA is communicating with your ISY994I. The communications data your log shows that it has determined the module is using the latest I2CS protocol and it was used. The I2CS notes we got in the defunct Developers Group did not show anything changed in the PLM when I2CS was added. I believe the device communicating through the PLM had to understand I2CS if enabled. I maybe confused. Is the problem you now can't add it back into the system or it is in the system and not changing relay and reported state? I don't think the PLM is bad as it is communicating. If the EZIO8SA is telling it to send things correctly I don't know. If it never changed the relay or reported back could be the program itself or maybe an Options setting in the Administrative Console for the EZIO8SA in the module list. My probably first production run EZIO8SA needed some listed options to work and did not add with the Auto Detect method and needed the hand picked module in the drop down list. This was with a 2412S power line only PLM powering the EZIO8SA through the serial power cable. My add screen showed in mine the very slow original I1 was being used. Though I did not capture the communications.
  22. With your saved ISY Configuration that has the EZIO8SA in it. You should be able to click on the first entry of the EZIO8SA and pick restore the module from the list. If you are getting communications errors. You may have line noise or a PLM on the EZIO8SA going. Though the Hops Left of 3 would indicate it did reply back with a incorrect status. One thing I did notice in my 5.0.16C version. It had a screen to set the Options settings. On Off level and speed. I had to change it before my unit would go on and off. Mine was On 0% and 9 minute ramp time. Not sure about the ZWave. It may need a 700 series card and a firmware revision high enough to support its security protocol. In the UDI sales pages I believe the board is presently out of stock.
  23. Especially if you have RF devices that have to be done one at a time. Hopefully a PRO version allows you do disable automatic writes and do each one individually after waking it up.
  24. The photo of the (saved) ISY Configuration shows it was found and installed when run. It also shows the unit is replying back to the command. Did you try and restore the EZIO8SA after the reset. To put the known links back? Not sure about the On Off not working properly. I know some had issues with the module and other models from that company. If it never updated or turned On and Off. It maybe the version of firmware in the EZIO8SA itself. The ISY does not display the EZIO8SA firmware version or test the module. Their own SHN Utility can test the EZIO8SA and cycle it inputs and outputs and firmware version. Unfortunately it needs its own PLM to be used. Does the EZICOMM PLM based power the EZIO8SA through the serial cable? The power line only ones could supply power out the serial cable. The Dual Band one do not and an external wall wart has to be used. The pass through outlet on the front is typical of the power line only 2412 main board PLM with their custom serial board. If the original EZICOMM is sending and receiving Insteon messages. A Dual Band may not help. Early EZIO8SA modules had a factory update. I think it was when the EZICOMM was a Dual Band for awhile before they also had power supply issues and went back to 2412 Based power line only PLM.
  25. When you factory reset the EZIO8SA you cleared out all the links in it and that maybe why it doesn't respond to the older firmware backup. As it was in the backup file already but not having any links in it. With the newer firmware and the no response. You may want to try it with the Event Viewer in Level3 and capture the EZIO8SA message back if any. It is very possible the messages are not being sent back especially if it is the older power line only version of the PLM or the PLM is failed, if it was one of the Dual Band PLM used by Smartenit (Simplehomenet or Compacta) for a time before going back to a power line only one made special for them by Smarthome.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.