stillwater

Is your Query ALL (typically 3am) program enabled? (This used to be pre-installed on the ISY). This is designed to set all the insteon devices to conform to what is in the ISY, but I've seen cases where all the insteon traffic associated with this Query can cause devices to change states to those not intended -- especially if the PLM is marginal. You may be able to see in the event log what time the switch happened and see if that corresponds to when the Query All program ran (if it's enabled).

If I understand your question, the ISY REST interface is the answer. https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface It's worked well for me. I am a little rusty but I think you can turn scenes and devices on and off directly. You can also set integer and state variables. Changing a state variable can trigger programs. So you can do pretty much anything with it. Others may also be able to point you to better documentation or best practices.

@MJsan Unless I'm missing something, you couldn't operate the "new" (Polisy/PLM) and "old" (ISY994i/PLM) systems in tandem -- if by in tandem you mean having them operating at the same time with the same devices. All the insteon devices need to have a single PLM Insteon address in their memory to operate. ISY/ioP (ISY on Polisy) have the very convenient option for migrating from one PLM to another, but it involves rewriting the PLM memory and rewriting the PLM address in all of the insteon devices, and so takes some time in anything but the smallest system. I haven't tried it but it seems plausible to me that one could conveniently switch back and forth between ISY and IoP with a single PLM. Or one could have parallel ISY/PLM and IoP/PLM combinations with each one controlling a subset of the insteon loads, (not splitting groups/scenes), but most likely in practice this would amount to having a small experimental new system alongside the "production" old system, and I'm not sure what would be gained. I suppose you could keep backups to restore the whole topography after the split. I have a polisy and my strategy is just to wait until the bug reports with new versions settle down to the same level as the ISY-994i, and then I'll switch over all at once. If access to PG3 is driving you to use Polisy soon, but you are reluctant to rely on IoP until further tested, you can always run PG3 (and PG2) on Polisy and have it talk to your existing ISY-994i which will continue to control the Insteon devices through the PLM until you decided to switch over to IoP. Again I may well be missing something -- others with more experience may have more informed views.

can confirm it is now working for me.

Yes @InsteonNut per @Geddywe are posting here to try to get your attention after emails to mobilinc support have gotten no response. Please see this thread https://forum.universal-devices.com/topic/36731-unable-to-access-994i/#comment-340580

My Mobilinc HD has worked for something like 6 years. Haven't changed any configuration this weekend. I don't know why but with Mobilinc (unlike UDI products) everyone always tries to blame the user. Only problem was when something convinced me to try Mobilinc X when it was new. It had fewer features than Mobilinc HD and it completely clobbered my ISY -- had to start fresh with a new SD card, as I remember. Wes thought it was all a big coincidence.

It seems very likely that Mobilinc Connect is down. Only other possibility I have thought of for my system is if Ubiquity pushed something to my Edgerouter X that is blocking mobilinc connect traffic. Since nothing in the 994i has changed it seems unlikely this is a UDI problem -- unless conceivably something changed in UD Mobile that is interfering with Mobilinc Connect -- but I'd expect to see something in the error log.

Mobilinc Connect (for ios Mobilinc HD app ) is still out of commission for me. No reply from mobilinc support. @InsteonNut what say you? Fortunately we have the option of migrating to UD Mobile, though it would be nice to have the familiar look and feel of mobilinc and not have to drop everything to configure UD mobile to make it easy to use.

While I appreciate Mr. Bill's attempt to help, obviously this thread should not have been marked "solved" as only 1/5 people have reported that rebooting did anything to solve their problem. Perhaps not surprisingly, Mobilinc support has not responded to an email to them on the subject. I copied Michel for his situational awareness and he responded instantly asking for my UUID. I looked in the mobilinc section of the UDI forum under third parties and saw the reference to a firewall entry for traffic from specific URLs. I looked at my Edgerouter X settings and haven't found a way to add URLs rather than IP addresses. But since nothing has changed in my configuration it seems unlikely to be a firewall issue... Probably the most sensible response to this and other Mobilinc issues is to make the switch to UD Mobile.

Also the "Send email" email support button on the Mobilinc HD app does not work on my iPhone.

Just checked after seeing this. My lifetime Mobilinc HD which connects to ISY via Mobilinc Connect is not connecting. (Status: "Checking"). I have ISY994i at 5.3.4. No significant recent changes to configuration. It worked fine in the last few days. iphone is on same LAN (via wifi) as ISY (ip address assigned in router). Rebooting ISY and iPhone did not help. I did install UDI's app UD Mobile on the iPhone sometime (2 months?) back but have not been actively using it. I was surprised it seemed to coexist fine with Mobilinc HD (Some years back the ISY portal and Mobilinc Connect conflicted, or so I thought). UD Mobile still connects fine. ISY error log shows nothing except for some queue full message ignored errors on startup that go away after awhile. No indication Mobilinc Connect is trying to connect.

Looking at the picture of the relay, it's a little hard to read but I think it says the contacts are rated 16A at up to 30vdc or 250 vac but the coil voltage appears to be 115vac as indicated by the coil: 115vac marking. 30 vdc is a common contact rating voltage threshold for relays but would be a quite unusual coil voltage.

My sense is that the relay clicking means the coil is activating and the armature is pulling in (and releasing to some extent when it turns off if it clicks then also) but does not necessarily indicate that the actual contacts are separating as they are generally mounted on metal leafs with some compliance.

I don't have direct experience with this but it sounds like the actual relay contacts have fused together, or possibly the return spring has broken or become detached. The contacts shouldn't have fused with only 130 watt load but inrush current could be higher. If so, two possible approaches to fixing: 1) Open it up and replace the relay with a new one with same coil voltage. Would require soldering. 2) Open it up and break into relay case and unstick contacts, use emery cloth to sand contacts, see if it works for another few years... then see (1) [Sometimes just banging on the relay will unstick the contacts] Once the case is open you could confirm the diagnosis by measuring resistance across the relay contacts with an ohm meter (with unit unpowered).

I know this isn't very helpful but some years back I had to resort to Telnet to deal with a corrupted SD card and it worked fine for me. You do need to know the local ip address of the ISY and be on the same network.

I am sure this won't be helpful to current participants in this thread but it might be to any onlookers... Maybe a month ago I set up a new Polisy using the wiki as a guide and there was zero ambiguity about which RJ-45 port to use for ethernet.

I am confused. The original program that wasn't working was looking for DOF command and now you are focused on DON not translating into proper state in IoP? Are you thinking these are the same problem (i.e. in the program the IoP thought the load was ON when it was OFF?)

Thanks. This is the North American product index page -- listing of all certified Zwave products with North American frequency. https://products.z-wavealliance.org/regions/2/categories Lots of products.. Some of which are available!

Thanks! The Zen51 and Zen52 appear to be 1.5 x 1.4" and I don't know how thick so they look micro size. They are 700 /S2 series. Thanks for the direction to Fibaro and Aeotec. The Fibaro Dimmer 2 is slightly larger and is 500 series. Aeotec Nano Dimmer is 2.9" x 2.9" x 1.1" and also 500 series. I see on the site linked by Techman that Silicon Labs is already out with 800 series modules that are available to be incorporated into products. ... haven't looked at whether that means 700 series stuff will become somewhat obsolete or whether 800 series just allows longer battery life or something.

Thanks for this @lilyoyo1 With all the interest right now in moving from Insteon to Zwave (or adding Zwave devices to an Insteon system), It would be great to have a table that shows closest equivalents to the various Insteon devices -- I had the impression that Z-wave was mostly switches and outlets.. It looks there is more than I had assumed (for example. sensors). I have seen the Zen17 recommended as a replacement for the Insteon IO module. I was wondering are there Z-wave plus or (better) 700 series equivalents to the Insteon Micro On/Off, Micro Dimmer, and Micro Open/Close modules? Though they are not exact replacements I see the Zooz Z51 could work instead of the Micro On/Off and the Z52 instead of the Micro Open/Close. I looked at a few other brands but haven't yet found a Zwave 700 equivalent to the Insteon micro dim.

@Michel Kohanim Apparently yes a KPL button. First sentence of first post from @arshishk was "I have the following program that checks the status of a keypadlinc button, and if the status is On, waits 1.5 hours and then sets the switch to Off."

By default a Mac will often unzip the firmware file you downloaded. You want to upload the stil-zipped file to the ISY994. Can't guarantee that this is your situation but that's often the problem.

3-4 Insteon devices failing each year out of 53 seems high, unless perhaps they are very old. Do you have a whole-house surge suppressor at the electric service entrance or main panel? If not this is a crucial investment to prolong the life of insteon and other electronic devices. It's been a long time since I made the jump to 5.x but my memory is that it isn't very difficulprocess if you only have insteon. You will need to check your scenes and the controller scene menus after the upgrade. A few programs may indeed need to be re-saved and possibly edited. The good news is there is no hurry to do the upgrade if everything is working for you now. You will definitely need to upgrade firmware and Z-wave interface before making use of Zwave --especially the new and better Zwave products (series 700) which you will want to use exclusively if you move to Zwave.. [I am not a Zwave user and others will have more info on that. I believe that there is an intro to Zwave somewhere either in this forum or in the UDI wiki that would be helpful to you --- maybe search for that.]

I don't use UD Mobile but if it's on an iPhone try disabling notifications for the UD Mobile App in Settings?

"ISY Serial Controller" I assumed @Michael805 meant a 2413s, or maybe a 2413s+ISY994i, not an ISY 994i