kzboray

Hum. I have multiple ISY's defined. I didn't realize that any one of them could cause this issue. let me disconnect all but the local one and see what happens.

Damm it just disconnected. took about 5 minutes this time. Sorry to raise false hope. Any other ideas before I start from scratch?

That seems to have resolved the problem. I guess @bmercier should be updated. Should I tag him, or do you want to do that?

I tried to " System > Your System> Local connection settings. Enter your local credentials and set Only Use local connection to true" but it gives me an error upon trying to do the sync afterwards.

I'm going to start from scratch @Javi It's got to be something I did since no one else is reporting this issue. I'll delete the app, and re-configure everything from scratch and see if that fixes it. If not. I'll let you know and we can trouble shoot further.

I also tried adding a local network under Settings, but this had no effect.

OK just disabled wi-fi on my phone and the problem persists. doing nothing simply opening the Favorites screen results in a disconnect after 30-60 seconds.

v0.175

I normally muddle through this stuff, but this is giving me trouble. I appreciate your help. Unfortunately the app just disconnected without me doing anything. I was just looking at the favorites page and it disconnected all ISY's. Showing disconnected on the UD page, and not re-connecting automatically. I'm at a loss as to what to do next. I can try a complete re-set. uninstall UD Mobile and then re-configure everything from scratch if you think that might help? I'm 10 ft form the router and have a solid wi-fi connection. So I don't believe it's that. Just re-started the App and after about 30seconds on the favorites screen it disconnects. I have to exit and re-start the app to get it going again.

@Javi I just deleted and re-installed UD Mobile on my phone. I used a backup to restore my customizations and it seems to have fixed this problem. Don't spend anymore time on it.

I just changed the <Custom Name> & <Type> from Switch Widget to Default and this this happened. The Icon color should be green as the device is ON and I have set the custom color parameter. Here is the Favorites Screen again showing the device Icon as Blue; Should be Green. And finally, the Sign in Page showing this time an Error. Closing UD Mobile and re-starting it then waiting for it to sync fixed the error. Previously this has also shown Disconnected.

I took the screen shots after re-connecting. I'll see if I can re-produce the error and screen shot the disconnected screen

Android 10 UD Mobile .175 Setting Global User Preferences / Span to 1 results in favorites being displayed as span value of 3 or greater. I can't tell what the value actually is since it expands across the screen on my phone. Setting the span value back to default allows the span values as set for each device to work again. As you can see below the span value is 1, but since I have set the Global value to 1 the favorites appear spanned across the screen.

I am new to UD mobile and just playing with two insteon devices to learn the ins and outs of UD Mobile. When I setup the mapped values as soon as I finished editing the values it disconnected. the same for editing the devices colors and icons in "family room"

@Javi I'm sure I've mis-configured something, but anytime I edit devices in UD Mobile it disconnects. I have three ISY's / Polisy's added and when this happens they all show disconnected. If I re-start the app and wait a few seconds they all come back as connected, but doing any edit in the app causes all attached devices disconnect. What information can I supply to help isolate this issue? Samsung S9+ UD Mobile .175 Android 10

I agree with @asbril I depend on the portal for myself and also clients. It is rare that there is a non-planned outage and planned outages are announced well in advance. I would be curious to see the uptime metrics on the portal, both planned and non-planned. I suspect the non-planned downtime is in the four nines area per year; less than an hour, which is outstanding.

@CandC Z-wave and Insteon are very different technologies. One of the main advantages of Insteon over z-wave is the way that Insteon supports scenes (groups of devices). z-wave doesn't do this very well. Every z-wave manufacturer has their own way of implementing scenes if they support it at all. And to make things even more confusing in z-wave, product to product from the same manufacturer can implement scenes in different ways. Insteon makes scenes easy in comparison. As @asbril said, most of the time with z-wave devices you end up having to write programs to simulate an Insteon scene, but it is usually possible.

@bgrubb1 I've never heard of nor experienced support taking more than 24 hours to respond to a ticket. I once put in a ticket on a Sunday evening, Michel personally responded within minutes. I would suggest you open a new ticket and reference the old one. Something unusual happened and I'm sure Michel would like to know about both your issue as well as the support snafu. Here's the link to enter a support ticket. https://www.universal-devices.com/my-tickets/

@Dan Torbeck Factory Reset There are only a very few reasons for performing a Factory Reset: Corrupted File system (blinking ERR light) Also instead of a factory reset another option for corrupt file systems issues is Replacing/Formatting an SD Card To start fresh ... i.e. if you are going to restore your old backup on the same ISY, then in all likelihood factory reset is NOT going to fix anything Reuse one ISY for more than one location You have configured your ISY with a static IP address, changed router/network, and can no longer access ISY IMPORTANT: You must reconfigure ISY again or restore your backup after the factory reset. Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second) Hold for at least 30 seconds until all of the the RX, TX, Mem, Error lights turn off and Mem light starts flashing quickly Release and wait for system reboot (reboot is complete when Mem light stops flashing) You may wish to also reset the PLM at this time. 2412S Quick Start Guide

I don't have access to a mini-remote atm, but if you manually link it to a device that has been added to AC, you should then be able to see the min-remote address in AC. After linking them manually, I would recommend you factory reset both devices and instead re- link them in AC. Manual Linking: 1) Tap Mini Remote scene button of choice 2) Press and hold Mini Remote set button until it beeps Mini Remote LED will start blinking green 3) Turn responder on (or any other state such as on 50% or even off) 4) Press and hold responder set button until it double-beeps Mini Remote will double-beep and its LED will stop blinking 5) Test by tapping Mini Remote scene button just programmed Responder load will respond appropriately

I'm not sure about support via a NS, but @io_guy offers a Polyglot alternative called Nodelink which does have DSC support. You will need to dedicate a device to running Nodelink 24/7. Here is the forum link. https://forum.universal-devices.com/forum/113-nodelink/

@Blackbird Here is an example of an ELK controlling an Insteon scene. In this scene when the front door opens, this event is passed to the ISY994i which then activates the Insteon scene if it is dark inside the home and the alarm is set to away (meaning no one is home). It uses one state variable for the alarm, which is explained.

@photogeek54 The Elk M1 is supported by the Node server (NS) developed by @Jimbo.Automates. The NS runs on a PolyGlot server, current models supported are the PoliSy and soon to be released Eisy. This NS offers a lot of functionality not supported by the original ELK module designed to run on the ISY994i. I would not recommend buying the ELK module and would instead spend your money on a PoliSy or Esiy when they become available hopefully later this month. Not only will you benefit from a much more robust appliance, but it also allows you to add on multiple technologies at minimal cost to you. @Jimbo.Automates has done a terrific job with the current ELK M1 NS in terms of features supported. If an API is released by ELK for the newer version 27, I imagine @Jimbo.Automates will do his best to offer a NS to support that as well. Keep in mind ELK may choose to keep the API private for the version 27 equipment and that would mean it would be impossible to offer support via a NS. It's not something that exists so it's not a good idea to make future plans on something that might be. I have personally installed many ELK M1s in combination with ISY994i's and PoliSy's. Its a very robust system combination.

I'd also try a reboot of the PoliSy and see if that clears things up.

WoL is pretty simple to understand. at it's most fundamental It's either a unicast or broadcast packet. More often than not it's going to be a broadcast on a single sub net going out to all devices whether there is a switch or not. switches simply re-transmit all broadcast traffic on a single sub net to all active ports. Your issues seems to revolve around changing the location of the IoP. Changing it's location physically wouldn't change WoL at all. Something else changed. One possibility is that when you changed the location an IP addr changed. If you are using DHCP this is something to check on both ends of the connection. IoP and the TV. Switches often keep IP addr to port mappings in memory so that a broadcast packet only has to be forwarded via unicast to a specified port instead of blasting the entire sub net with unnecessary traffic. If the switch is still sending to an old IP for your WoL traffic it might not be getting to it's destination. Now this will only last as long as the switch keeps this info alive in memory. All of this is to say, I don't think it's the IoP that's the problem.