Xathros

If Alexa is recognizing your commands accurately then the vocabulary is the problem as Jon alluded to above. I suspect that once the Connected Home portion of the ISY goes live, these problems will disappear. -Xathros

Not sure how this differs from Ubi other than being funded on Indie go go instead of Kickstarter. Looks to be based on Google's voice processing just like the Ubi. -Xathros

What names are not working for you? Izzy CAN address scenes. Just set the spoken name for the scene in the same way you do for a device. Make sure there are no duplicate names (Don't use same spoken name for a scene and a device). Check the Alexa app to see if Alexa is understanding your requests. In my testing I have found that Alexa can misunderstand "...tell Izzy to...' as "...tell it to...". When that happens, the commands fail as they don't get passed to the Izzy skill. Hope this helps. -Xathros

And refrain from calling devices Lights or Lamps. Alexa is having a problem with things named lights & lamps at the moment. So, for example, instead of "Kitchen Lights" in the spoken field, use just "Kitchen". -Xathros

Your UI is out of date. UI should match the firmware version. Clear your java cache and then download the JNLP for the console from the 4.3.26 release post. -Xathros

Have you logged into the portal and connected it to your Amazon account? -Xathros

Hello and welcome to the forums. How are you accessing the console? Via web browser or have you downloaded the JNLP application and have an icon on the desktop? Do you know what firmware version you have on the 994 and do you know if the admin console is the same version? -Xathros

Not exactly but you can just create another scene with all of the above as responders. -Xathros

man cave

You can right click your programs and use the find replace to search for the name of your stat. Also, sort the program summary by last run time and look at the most recently run program(s) -Xathros

I can't tell from your screenshot if that is an Integer or State variable. -Xathros Sent from my iPhone using Tapatalk

I'm guessing that you have no Integer vars defined thus, no file to be opened, thus the file open failed message. After a quick review, I see nothing but perfect comms. Did any of the operations your tried fail during these tests? -Xathros

Not all dualband devices perform the same in terms of range. Those installed in walls and especially those installed in metal jboxes tend to have poor range. Plug-in modules like the range extenders and LampLinc modules tend to offer better range since they are less obstructed. Perform the beacon test from your existing dual band devices and if you get consistent results indicating a successful bridge, then move on to isolating problem devices. Identify a consistently problematic device and run multiple scene tests against it. Then after filtering suspect devices, repeat the scene tests and evaluate the results. If no or insignificant improvement, then move the filters to other suspect devices until you see marked improvement in the test results. You can isolate entire circuits at a time by turning off their breakers and testing with them off. Keep in mind, this might effect your bridging if any of your bridge devices are on the circuit you turn off. -Xathros

This sounds like simply poor communications on the Insteon network and is not that uncommon. This can happen if you have noisy power supplies/electronics on the line or devices with noise filters built in that actually absorb the Insteon signals as though they were noise. It can also be signal propagation problems across the legs of your electrical feed. Best practices state that you should isolate noisy items or signal absorbing items with FilterLincs. Things like computers, UPS boxes, Noise filtering power strips, many wallwart style power supplies (cell chargers etc) have been shown to interfere with Insteon signaling. You should also ensure that you have reliably bridged the legs (phases) of your electrical feed with Range extenders or other dual band devices. Perform the 4 Tap beacon test from several different dual band devices to ensure proper bridging. Locate the ISY's PLM as close to the service entrance/main panel as possible and preferably on a dedicated circuit not shared with other non-isolated electronics. The set phase bridging devices would also be best close to the main panel with additional dualband devices distributed around the premises as needed for good RF coverage. There are MANY threads on this forum discussing comms diagnostics and procedures. Hope this helps. -Xathros

Awesome! Glad I could help. Now, based on the the above, I am assuming that you are launching the admin console from the ISY Web interface each time. May I suggest that you instead, install the Admin console as an Icon on your desktop and launch it from there. Download and run this file: http://isy.universal-devices.com/994i/4.3.26/admin.jnlp This will create an icon on your desktop for the admin console. Try again to delete the scene using this console and report back. If you cannot delete, try clicking each device within the scene one at a time and look at the displayed info for each device. Do any look strange/wrong/bad ? If so, try removing the bad device from the ISY tree and see if that helps out the state of this scene. I wonder if a /rest/nodes dump from a firefox session would shown anything useful related to this scene... Hope this helps. -Xathros

When prompted to save the backup on your Mac, where are you pointing it? If not a location within your User folder, this may simply be a permissions issue. Try saving to the Desktop, Documents or anywhere else within your home folder. The ISY File chooser often defaults to locations outside of the home folder and many times those locations are not writable. Hope this helps. -Xathros

Hi Barry, If you have reverted to using port forwarding on your router rather than using MLConnect, and in your Mobilinc settings, Host Type is set to ISY rather than MobiLinc Connect, then you will do no harm by buying into the UDI Portal. In fact, based on recent feedback, you will be able to turn off your port forwarding and use the UDI SY Portal address and credentials in Mobilinc to get you connected. Hope this helps. -Xathros

Glad I could help. -Xathros

Just to clarify and put it all in one place... The 4 Tap beacon test is not linking the range extenders. It's simply running a test to help you determine if their placement and circuit choices are correct to allow them to bridge the legs of your electrical feed. These are simply dual band devices with no load control or sensors built in. Since they have no controller or responder functionality, they have no need to be added to the ISY or linked to themselves or anything else. Basically just plug and play as long as they are within range of each other (or another dual band device) and on opposite legs of the electrical feed. Some folks (Teken) recommend DualBand LampLinc modules instead of range extenders as they perform double duty (same bridging function as range extender plus can control loads). -Xathros

Should be able to call a script to get the status from the python module, evaluate the response and set an ISY var with a /rest call based on the response. No? -Xathros

Does DSCLink have io_guy's Relay server built in? If so, then you have everything you need to make this work with the ISY already. A few simple bash scripts is all it would take to complete the interface between this python module and the ISY. Use the Relay server to run the scripts via the ISY's network module. If not, then look at ISYLink or NodeLink both of which offer the Relay server. -Xathros

Just curious, what was the resolution? -Xathros

Excellent. Factory reset of all new or devices being repurposed is the best route for sure. -Xathros

Stu- Understood and I have many such offsets in my programs. Just didn't expect that in this case and since the times here are less trigger and more of a limit of operations, +/- minutes makes more sense to me. Thats why I called it out. Just trying to read between the LoC. -Xath

Howdy smokegrub, Your sensor is likely configured to send On commands only. This is why you never see the status in the console change to Off. You can change that by changing the "On Commands Only" option in the sensor. You don't NEED to however. The simeplest and, in my opinion, best solution here would be to change your program to use Control rather than status: If From Sunset - 30 seconds To Sunrise - 30 seconds (next day) And Control 'Motion Sensors / Deck Motion Sensor / Deck Motion Detector-Sensor' is Switched On Then Set 'Deck Light (TL)' On Wait 10 minutes Set 'Deck Light (TL)' Off Else Set 'Deck Light (TL)' Off This solution has the added benefit of restarting the 10 minute wait with each additional motion detected and will only turn the light off after 10 minutes of no motion detected and/or at 30 seconds before sunrise. Also, did you really mean 30 seconds before sunset/sunrise or was that supposed to be minutes? Not that there is anything wrong with this, just seemed odd to me. -Xathros