matapan

How reliable is the scene test feature? I tested a scene twice and received back two completely different results. One where all devices in the scene failed, and one where all devices in the same scene succeeded. I did find that installing more Filterlincs for some other circuits helped rectify communication issues. How can one tell between a failing PLM with communication problems caused by a noisy line? Thanks!

Here are some screenshots of results:

Can anyone recommend the best way to troubleshoot link creation when one creates a scene? I have many scenes where there are multiple devices which act as as controllers for one device which acts as a responder. Once I have created the scene, I noticed that some of the controlling devices don't reflect the state of the scene. For example, if I have a Switchlinc dimmer which acts as a controller and responder in a scene, with a button on two Keypadlincs which act as controllers, I expect that when the Keypadlinc button is turned on, the button on the other Keypadlinc acting as a controller is also turned on, as well as the Switchlinc dimmer. With recently created scenes, I noticed that the state of the button or paddle which is not pressed is not updated with the current scene state. Older scenes I have created are correctly updated. Any thoughts on the best way to troubleshoot this? Thanks!

Thanks for your suggestions. I was not close to the PLM when I attempted to link the motion sensor. I tried linking the motion sensor using both methods, one described in the original post and one where I selected Start Linking and put the sensor into linking mode. The linking process in each case did not appear to initiate and the Admin Console went promptly back to a Ready state. I also tried factory resetting the motion sensor and tried to link the device. I looked at the communication events while attempting to link manually. It appears that the motion sensor was already added previously. Is this the expected behavior?

I tried adding an Insteon motion sensor model 2420 tonight and couldn't do it. From the Admin Console, I selected Link Management/Link a Sensor/Motion Sensor After accepting the next dialog with the instructions on putting the motion sensor in setup mode, I entered the device address, a device name, and the device type (2420M), then pressed OK. The console didn't do anything other than to return to a waiting state after this. No device created. Status of the controller is Ready. On a separate note, I have noticed that not all the links are created when creating scenes where I have 3 or more devices with a several controller and a responder. The observed behavior of this failure is when the device states are not synced amongst the controlling devices. I'm not sure how to troubleshoot this. Any ideas? Thanks.

Geddy: The information provided in the link was in context with the version of MacOS at the time. The Privacy and Security settings tab has been revamped in Mac OS Sequoia 15.3.2. There is a Developer Tools subtab which you can specify apps which can circumvent the security restrictions but the jnlp file cannot be selected to be added. The jnlp file is grayed out.

Under System Settings | General | Local Network, the IOX Launcher doesn't appear in the list, nor is there a visible way to add additional apps to the list. Not sure what the references to other posts are relevant - if I try launching start-8.jnlp, MacOS returns an error indicating that the app was not opened because Apple could not verify the file was free of malware.

Hi Geddy, I'm running macOS Sequoia 15.3.2. It's not clear how one adds apps to the local area network access list as no controls are visible.

Hi there, I have an ISY994i running the IoX Launcher on a Macbook. I tried launching the Launcher today and the Admin Console failed to start because of a certificate error. I don't understand the ins and outs of security certificates, self signed certificates. I tried reading the wiki pages about self signed certificates and it is above my pay grade. Does anyone know how to correct the issue easily to be able to launch the Admin Console? Thanks!

I want to write an automation script to notify me when my dryer load is completed. To do this, I think I'll need a plug for monitoring the load change on the dryer. Does anyone on this forum know a ZWave plug for this purpose that works with the ISY994? Or, if I'm barking up the wrong tree, is there a better way to accomplish this task?

I believe if you run the Airport Utility on your Macbook Pro, you can see your router and see all of its clients attached to it. You can look for the MAC address of your ISY to find its IP address and try manually adding it to the Launcher using the Add option.

Home Assistant seems to have a good model for this. If the update doesn't work, there appears to be a feature allowing rollbacks. I have no experience with that, as I have thankfully never had HA not comeback from an upgrade. But their model seems pretty sensible.

If you're concerned about the ramifications of using this node server, you can always use an IO Linc with your setup to generate the momentary contact necessary to open and close the gargage door, then use a door sensor to monitor if the garage door is open or not. I have a magnetic contact sensor mounted on the floor of my garage and the other component mounted to the door. Use a program to trigger the necessary contact to open and close the door and monitor the state of the sensor. This works pretty well.

Read your post and tried to think out of the box here. Any possibility of taking one of the modules and giving it to another user for adding it to their system? That might confirm if the device is bad or if you have comm errors.

Have you looked into a device called Broadlink? Apparently a lot of people use it for IR functions. It sort of operates like a Harmony Hub, but is purportedly easier to deploy. They're reasonably priced too, available on sites like Amazon. I personally have not tried the Broadlink device since I have amassed a collection of Harmony Hubs over the years. But it would be a device I'd consider. In addition to IR support, it also supports RF.

When using a UPS, is it a good idea to plug the UPS into a Filterlinc? This is presuming that the modem is not plugged into the UPS, but the eISY's power supply is.

I don't know what the cause might be, but I have a guess. A bad power supply for your ISY? Something I would try if I had a situation like this is to replace the power supply with a known good working one and see if that cures the reboot problem. I vaguely remember having some issue with my ISY a long time ago that was cured by replacing the power supply. I think most people at the time suggested the power supply or the memory card as being the culprits.

Here is the reference: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3 Under the heading "Instructions for using Multiple Echos Smart Home": To support multiple Echos with different Smart Home devices, you need multiple ISY Portal sub-accounts with each their own user profile. Have your Echos tied to different amazon accounts In ISY Portal, configure a sub-account and user profile per echo: <etc> <etc> <etc> Is this no longer relevant, as oberkc suggests?

Thanks to all who replied. There is a reference in the wiki page about the need to create separate accounts for each Echo device. Can anyone explain the rationale behind this?

I think there's supposed to be a way to say simple references to turn on lights in a room that has an Echo in it without using the long name and unique name we all give to different lights in the house. I did read the wiki article on Amazon Echo integration, which suggests setting up each Echo with different accounts to do this. Isn't there a less complicated way of doing this with groups? If what I'm asking isn't clear, let me provide an example: If there is an Insteon dimmer switch called "Master Bedroom Light", I'd like to be able to say: "Alexa, turn on the lights" in the Master Bedroom, but also be able to say the same thing when I'm in the garage to turn on the lights there, without having to say "Alexa, garage lights on" I have a Alexa group called "Master Bedroom" and another called "Garage", in which "Master Bedroom Light" is in the group "Master Bedroom" and "Garage Lights" is in the group "Garage". There is an Echo in each of these rooms.

If you have a multimeter, you can check the output of the power supply you have. I believe tip is positive and the ring is negative. I believe the power supply from UDI is 12 volts, 1 amp. If you find a similar power supply with a plug that has the correct polarity that fits in your controller's power plug it should work.

Instead of using a single motion sensor, you can use two for attempting to detect detection. The sequence of motion sensor triggers will provide the direction one is walking. I say "attempting" because in real life, people walk back and forth before the sensor times out for detecting the next event. You can set each motion sensor to have a short timeout cycle to address this.

I'm not in the same boat as you are. I am still using an ISY994i with a Z-Wave board. But I had a communication issue with one device and nearby devices would also not operate correctly when toggled off. The solution for me was to delete the device having communication errors and then add it back as a new device. This cleared the problems. The options to repair links or to update them were useless. It might be worth a try to delete one of the devices that you lose and add it back to see if it sticks around.

I was able to address the issue with odd behavior in the Admin UI with respect to the state reporting of Z-Wave devices recently added to my setup. The Admin UI was not correctly displaying the state information from one of two Aeotec Trisensors I added. One of the sensors would toggle on a motion sensing flag then toggle the flag off after the timeout period was reached with no additional motion sensed. The other sensor would toggle on like the first one on motion detection but would fail to toggle off on timeout. At the same time I was having this issue, one of my Z-Wave devices kept reporting communication errors. The option to repair links or update neighbors didn't do anything to resolve the communication errors. So I deleted and added the device back, then restored any links or references in programs that were broken when the device was deleted. This cured the communication error, and also corrected the state information reported in the Admin UI. For whatever reason, UDI Mobile was reporting the correct state information from both Trisensors. FWIW, this is what I found as a solution. If you have Z-Wave devices and get communication errors, don't ignore them - other devices in your Z-Wave network may be impacted if you leave the error(s) unresolved.

I have an ISY994i with version 5.3.4 firmware. I have the Z-Wave Plus board installed in the controller.