MrBill

You can swap back and forth yes, but I don't know how successful you'll be doing it remotely as the portal connection does need approval via the admin console. the directions are here: https://wiki.universal-devices.com/index.php?title=Main_Page#Instructions_for_Purchase.2FActivation.2FDeactivation

Is this an ISY994, or ISY on Polisy.... I suspect you mean ISY994 by the version numbers... but you posted in ISY on Polisy...

are you using https://<the.ip.of.polisy> you must use https not http

that's the cloud version of polyglot... you need to review the instructions for logging into your Polisy.

From the ISY's perspective, there's only two places From can come from: The smtp client defaults as shown above, and that can be override in an individual message. In the case shown above the From is blank, meaning use default. Note that when this field is used it's the same format as the default with Name and email address separated by a colon. Now once it leaves the ISY and is accepted by the smtp server the smtp server could also be replacing a blank or corrupt FROM line. and likewise the email client thats receiving the email message could also be replacing a blank or corrupt FROM line, and likewise most mail clients allow filters to change the FROM line. If I was betting tho, it's more than likely the email server providing a default FROM.

Did you restart the admin console AFTER the nodeserver was installed? this and this make me think that the admin console was not restarted after the nodeserver was installed.

you have the From Field set correctly... many people miss that colon in the example. this doesn't look correct... but if you're receiving emails apparently it is correct... the field should just have smtp.server.com --- My understanding of your issue after reading the post multiple times is that you are having issues with the FROM address? Perhaps you could restate exactly what the issue is, because it's very hard to follow from your initial post.

in the meantime if you have pro turn off those two green buttons on the right end of the admin console ribbon. That green 1011 icon will try to write often, turning off those two buttons will hold those.

Feit bulbs have gotten better in recent years... but at one point some caused electrical noise that blocked Insteon.

yep... they change color (warmer) as the dim. they resemble a dimming incandescent bulb color wise. they generally are available in all shapes and sizes.

@tomas21 Specifically cheap off brand LED bulbs often have cheap power supplies. After learning the lesson, I pretty much try to stick with Philips Warm Glow bulbs (or Phillips Hue in a few cases) for anything and everything. If Phillips isn't avaialble in that size style.. i stay away from off branded bulbs, including Feit from Costco.

I'd try a different bulb. What's different about the lights between where it happens and where it doesn't. When I mention different bulb I mean different brand or style, not a second bulb exactly like the first bulb or bulbs.

that green icon is 1011 which just means the ISY has instructions it hasn't been able to write to the switch. It will try to write those instructions often... like eveytime the ISY wakes up to write other things to other switches... If you have the pro version of ISY, turn off these two buttons on the admin console tool bar: The left one is for wired devices the right is for wireless devices. this will turn the green icons to grey (deselected) and prevent the ISY from constantly trying to update the device while we try to solve the problem. My method for finding a noise making device is a little bit intrusive... but I go to the breaker box and leave 3 circuits turned on... the circuit with the ISY, a circuit on the opposite phase that has a dual band device near the PLM, and the circuit with the switch that's not working... in this case Boy's bedroom recessed. All other circuits get turned off. Next go to the ISY and right click the device and restore it? did the ICON go away? can we now turn it on/off from the ISY? this is good. so then i go back to the breaker box and turn on about 1/4 of the circuits and back to the ISY to retest... rinse and repeat until the device doesn't work again... when it stops working then we turn some of those breakers back off and keep playing this game until we find the exact breaker that makes the switch no longer work... Once we have it down to a single circuit... and two paragraps up the bad circuit might just be the one with boy's bedroom recessed. if it didn't work with all the other circuits off except those three the noise maker is on one of those 3 circuits... To hunt on a single circuit first go unplug anything thats plugged in on that circuit. retest... then try turning off all dumb switches (if any) and pulling the airlock tab out on all other insteon switches on that circuit. eventually you'll likely get it down to one device that's generating noise. Either put a noise filter on that or eliminate it. --- another method unwire the switch and wire it to a test cord so that you can plug in... .Plug it into the same circuit as the PLM and "restore device" further test the switch to prove to yourself it's working... then re-install it and if it's still doesn't communicate start the hunt for a noise make or signal sucker (see the Wiki articles that I previously linked) I'm not sure what No change for the foyer means. a note about the buttons : When these are deslected you can still force the instructions to be written to that device only by right clicking the device and selecting "restore device".

it more than likely means you have electrical noise on the power line, perhaps only on that circuit if this is limited to 2 switches. First question to ask is did you plug in anything new on that circuit or change any LED bulbs? What happened when you restored device? There's several wiki articles on the topic

Dual band devices generally handle phase coupling. When searching for the noise or signal sucker on a location that used to work and just started having issues, the first question to answer is what's different or new since this location last worked. Almost anything new that plugs in, I immediately test to see if it causes Insteon interference-- a new device or bulb is suspect until proven innocent. The technique then becomes more invasive, turning off breakers and/or unplugging/unscrewing things until the culprit is located.

I just read from the top down... this sounds like nothing more than a noise/signal sucker issue to me. All my wired devices are dual band... doesn't matter i can have conditions that prevent signals from getting through. thankfully it doesn't happan often anymore. We used to have a counter top deep fryer that just being plugged in would bring Insteon in half the house to it's knees. Bought some LED bulbs once the reaked havoc on all nearby items... didn't take me long to figure it out because it was the only thing "new" at that time. Also remember a semi recent case of someone elses where it was a drill or tool charger in the garage.

eventually yes. With your experience level I would recommend you wait a few months at this point. They're still chasing a few bugs out of the system, but yes ultimately you will want to transfer to ISY running on Polisy. As I mentioned it just became possible to migrate a few days ago.

For the time being that might be true. But when you decide to migrate to "ISY on Polisy" you will plug the 2413s into that port on Polisy. Why would you migtate... it's the direction ISY is taking... someday the 994 will be obsolete and no longer receive updates... new features will likely only be introduced to ISY on Polisy. ISY on Polisy is new, it's been in testing for 6-8 months and has only just in the last few days reached the point that its easy to migrate an existing installation.

You'll need that port for your 2413s when you move to "ISY on Polisy".

The rs-232 port on the back by default works with the Insteon serial PLM. Are you planing to use 2413s with your Polisy?

with directIP you can use the ISY portal and its Echo integration. I can understand that. but if it is a result of an ISY firmware change only Wes will be able to identify the problem. Then he will either need to either fix mobilinc or work with UDI to change the firmware. Also 5.3.4 has been around since July 30th and this problem has not seemed to bother anyone else... although I don't know how many people use Mobilinc X and Mobilinc connect these days... there have been several complaints that Mobilinc X is now well over a year with no updates or development. On that note, Wes hasn't logged into the forum since 12/22. you might want to open a ticket at mobilinc.

Actually you can now... (source) (Bold and Red Font edit by me)

Since this is a mobilinc and mbilinc connect problem we should ping @InsteonNut. This thread probably really belong in the mobilinc section of the forum as one way or another Wes will need to provide the support. FWIW, it no longer requires backend changes to migrate back and forth between Connect and the ISY portal, but it's not a fast single click process either. the instructions are here.

So just to be clear, are you using Mobilinc Connect or the ISY portal? You mentioned the portal integration which normally refers to UDI's ISY portal, but later you mention that it's Mobilinc Connect.

Can the ISY control the device? Have you gotten it added? Z-wave needs a mesh of devices.. and the ISY's transmitter doesn't reach far, the nearest device will repeat and will reach further. You may also discover that the ISY standing on it side edge may have better reach. see this post: