All Activity

I had an ISY for many years and it worked flawlessly. I recently migrated to an EISY about a year ago. Occasionally, it would stop functioning correctly in that the UD Mobile app on my android phone would not be able to control the ISY, and I would receive the error below in the app (the black and white screen). When I tried to log in to the IoX Launcher, I was able to reach the admin console, but I could not control any functions and I would receive the other error below (the color screen). I would have to reset the EISY to get it to work properly again. This started occurring more often (on a monthly basis), so I set up a program to reset the EISY on a weekly basis. Now, this has been happening even more often, sometimes 2 or 3 times a week. It happened last night to where I had to reset the EISY, and then today, I ran the "Then" part of a program, but the "Else" part ran. I had to reset the EISY again to get it to work. This is becoming very frustrating. It seems that the ISY was very stable, and the EISY is not. I am running Firmware and UI Iox v.5.9.1 and have a Z-wave module installed although I only have a temperature sensor attached to the Z-wave and everything else is Insteon. Any help would greatly be appreciated. Thank you.

12

Thanks what slots number is the mqtt plugin?

Thanks @Javi, Here you go: <profiles> <profile family="10" id="1"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="2"> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="3"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="4"> <files dir="editor"> <file name="udmobile.xml"/> <file name="hometele.xml"/> <file name="custom.xml"/> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="hometele.xml"/> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="5"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedef.xml"/> </files> </profile> <profile family="10" id="6"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> <profile family="10" id="7"> <files dir="nodedef"> <file name="nodedef.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editor.xml"/> </files> </profile> <profile family="10" id="8"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="9"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> </profile> <profile family="10" id="10"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="editor"> <file name="editor.xml"/> </files> <files dir="nodedef"> <file name="nodedef.xml"/> </files> </profile> <profile family="10" id="11"> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> <file name="custom.xml"/> </files> <files dir="editor"> <file name="editors.xml"/> <file name="custom.xml"/> </files> </profile> <profile family="10" id="12"> <files dir="editor"> <file name="editors.xml"/> </files> <files dir="nls"> <file name="en_us.txt"/> </files> <files dir="nodedef"> <file name="nodedefs.xml"/> </files> </profile> </profiles>

I assume you could use "<name of location> fans <speed>" and create a routine that is not device specific. And the do "fans <speed>" that is device specific. Personally don't see myself controlling fans in a room I am not located in except for my shut down routine, and that is a single command that triggers an ISY program that then executes a shut down of all kinds of stuff.

Looks like the Node Server is missing a value. Please post the output of http://192.168.XX.XX:8080/rest/profiles/family/10/files. where 192.168.XX.XX is the local ip address

Hi @Javi, I can't create advance status configuration for the 4 tiles that have Nano in the description. No trouble with any other that I know of. Those tiles are associated with the MQTT plugin. Maybe that's the issue? Thanks, Tim

I keep contemplating that style but have avoided assigning rooms until now. How would you operate the fans in another room then? Say to operate the fans in the exercise room from the back patio? Can two different names be assigned? Absolute and relative?

Yup that's a classic. It looks like a field label, but it's actually a button to write the new value.

This discussion got me playing with Alexa a bit. I discovered that you can have each device respond uniquely to a command. So for example, the Alexa on my back patio would respond to "fans high" by turning on the patio fans, and that same command in the exercise rm would turn on the fans there. To the point here, by isolating commands to the relevantly located Alexa, Each Alexa will have fewer commands to understand and thus lower the chance of it confusing commands.

You press the button next to whatever feature your are tweaking after you change it. You should not need to write updates to devices, unless the little green 0101 icon is next to the device

I recently moved and am setting up a whole new system now that I have moved from the ISY994 to the EISY box. As personal preference, I like most of my lights to have a 2 second turn on and turn off rate. When a new device is added, it defaults to .5 seconds. When I use IoX and try to set the ramp rate, writing the change to the device doesn't work. I have tried using the "Write Changes" option at the bottom of the screen as well as the "Write Updates to the Device" when right clicking on the device in the device tree. However, it all works if I use the app on my phone. Any thoughts before I open a ticket? Thanks.

I guess this is just another quirk of Alexa but I’ve had the voice command “It’s movie time” in our house for a few years now. It correctly turns off all lights in and around the family room for watching TV. Maybe it’s because I don’t have any other commands beginning with “It’s” so there is no potential conflict.

I have several different lights in the livingroom. Grandfather Clock - An Insteon on/off module that turns on and off the light in the clock Floor Light1 - One floor "up light" Floor Light2 - Another floor "up light" Table Lamp - a Hue color bulb in a table lamp Fan Light - The lights in the ceiling fan All of these respond OK with Alexa. I will group the two floor lights so that they both do the same thing when commanded instead of having to command them separately. I am not sure why, but things are working better now after fiddling with things. I am not sure if Alexa has "learned" anything or that I am now doing things slightly differently. I have an IoX program called DoSunset. It affects most of the lights on my system, not just the livingroom. It automatically runs 30 minutes before sunset. If it is cloudy, sometimes I want it to run earlier and so I have it setup to run by Alexa when I ask. If found that if I set the spoken word in the portal to "It's Sunset" and also set the voice command in Alexa to "It's Sunset", it runs. I have a "TV Time" scene for when I want to watch television. It doesn't work if I have the Alexa voice command set to "It's TV Time" but it does work if the voice command is just "TV Time." I had the same problem in my last house when I had scenes for watching television in the family room and for the home theater. "It's TV Time" and "It's Movie Time" did not work but if they were just "TV Time" and "Movie Time", they worked. Just quirks of Alexa.

The way I outlined above, it always works no matter how you control it. There are ways you could mess it up and get multiple buttons lit at the same time or off at the same time, but you would have to go out of your way to do that and it would never happen excepting that you did it on purpose. Like adding the buttons to other scenes as responders. But why would you do that except to sabotage yourself?

If none of the above works for you, try this: Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns: ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state

If it doesn’t add the shortcut when you run the start.jnlp you need to clear the java cache again (selecting all 3 boxes). Then run start.jnlp again. More than likely java thinks thins are installed and it’s not actively adding the shortcut. That’s typical following a Java update as well.

Next step: Alexa, please remind me your device name for the living room lights? 🤨

This is how I do it. despite the warnings, I actually like the mutually exclusive option with keypad buttons. One has to recognize, however, the limitations. It only works if you manually press the affected buttons physically. The relationship is not enforced when you change the state of those buttons via the ISY.

Geddy -- thanks for the suggestion of using the right click. Yep, got me back in. Now, any idea on how to the UD shortcut icon back???? I have moved the start.jnlp download icon to the desktop and I can get in that way.. just would be nice to get the shortcut back. Again, thanks for your help

the hardest thing is remembering the exact words. Need to get a Grok assistant that can recognize what you want rather than requiring literal requests. And the real pisser is when you start to say what you want and halfway through realize you are saying the words in the wrong order and then Alexa gets all confused and you have to wait for it to clear out before you can go again.

@MTellevik To simplify things, why not have the away button on and lit when you're away, and when you're home the away button is off and unlit.

I don't recommend this for 5.x. Using scenes, like the fan example, is the recommended way.

@MTellevik from the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Linking_a_KeypadLinc There are other pages talking about this too, but I think this is the more current look of the window. Note the warning though about using scenes to handle it. I'm not 100% sure how this is handled in IoX 5.x these days.

I am not near my system, but recall the mutually exclusive feature to be found from the admin console, selecting the keypad and, along the bottom of the main window, you should find an “option” button (or similar) where ome can configure which butons are part of the mutual exclusive relationship.