matapan

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.

Thank you for this reference!

I recently added several more Z-Wave devices to my setup and ran across some interesting behaviors. The two Aeotec Trisensors I added behaved differently from each other if the Admin UI is assumed to be accurate with respect to device state. On motion detection, each sensor changes its motion state from off to on. Upon reaching the timeout period, only one sensor reverts back to an off state for its motion state. The other sensor remains in an On state with respect to motion detection. All of this was reported in the Admin UI. I tried modifying the parameter of the motion sensor, but upon choosing (Write Changes), the Admin UI returned a communication error for the sensor. I assumed this was due to the proximity of the sensor from nearby Z-Wave devices. For a completely different reason, I installed UD Mobile on my phone. I looked at the device state for the motion sensors and noticed that both motion sensing states were now off. I triggered each of the sensors and waited for the timeout period to be reached. In the mobile app, both sensors reverted back to an off state after the timeout period was reached. There were no communication errors. What can account for the difference in reporting from the Admin UI and UD Mobile? Why am I getting communication errors in the Admin UI with these devices but not in the mobile app?

thanks, but I still get a 404 error after modifying the url

http://10.0.xx.xx/rest/zwave/node/ZW023_1/query/

Second method is over my head.