matapan

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?

But a poor quality product virtually guarantees a loser, unless you can overlook the negative quality and tolerate it.

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.

Out of curiosity, I checked out the eBay listing for the refurbishing service. The seller has different grades of service offered, from the basic electrolytic capacitor replacement to "the works", where additional components are replaced, working or not. The listing begs the question: Does a component upgrade make the PLM a reliable unit for say, 10 years? 25 years? Or does the design need to be revamped to ensure long module life? I figured from reading past comments about the capacitor replacement that this is a maintenance thing; you replace the caps every 3-5 years to keep it going. Is this the case? Electronic design and repair is above my pay grade apart from the manual labor involved.

FWIW, I sent a comment to the new Insteon company about product quality and the longevity of the PLM in particular. Steve Lee responded back, who mentioned that the PLM quality has improved significantly over past several years, to the point where the Insteon company has a negligable return rate on the devices. I did stress the importance of product reliability and stability in terms of a product line's reputation in the email thread.

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.

I get a 404 error when using the first method.

I had the occasion to turn some circuit breakers on and off several times while working on installing some new outlets in my house. The circuits power cycled have some Z-Wave devices on it. Apparently, power cycling these Z-Wave devices didn't do them any good, as I am getting strange communication errors now for these devices. According to the wiki page article on communication errors, there should be an option in the Z-Wave menu in the Admin UI for healing the Z-Wave network. I cannot find this menu pick or its parent called Tools. Is the Wiki page outdated? I am on firmware version 5.3.4 on an ISY994i with the Z-Wave plus board.

I have the occasion to update device properties on two Aeotec Trisensors I acquired recently. There appears to be a means to set a device's properties by specifying a parameter to be updated along with its value in the Admin UI. There doesn't appear to be a means to view the device property values directly. I think I found another post in this forum which describes in general detail how to pull the parameter values in a script and assign it to a variable to email or text it out. Seems like a kludge if all you want to do is to see the current device property value is set to. Is there an easy way to see the parameter values set for a device? If the script route is prescribed, can someone describe in detailed terms how this is done? Thanks.

I have a six button Keypadlinc I added to my ISY setup a while ago. Recently, I wanted to assign one of the buttons as a controller for a scene, only to discover two of the nodes for the buttons were missing. What is the best way to restore the nodes in the Admin Console. I have no idea how they went away.

What if you deleted and recreated one of the scenes that is failing? Does this change anything?

I'm kind of curious if an extra layer of control causes noticable latency.

I second the recommendation you should just test the bulb with your specific configuration directly. There are many Insteon dimmer revisions, all addressing different issues. Some of them I recall related to specific flickering conditions. You may or may not have the revision that addresses the flickering issues. Bulbs themselves have specific characteristics that cause them to flicker on one circuit but not another. It's beyond my pay grade. I can just share with you my personal experience. I'd just go out and get the bulbs and see if they do the trick or not. If not, hopefully you've purchased them from a retailer that has a good return policy for situations like this.

Not really sure how this thread became a discussion about the Nokia Hub; the title of the thread specifically refers to the Insteon hub. If UDI attempted to purchase the unused inventory from the new owners of Insteon and they weren't interested in selling the Nokia hubs for a reasonable cost to repurpose them as hubs, and they require rework of code on the ISY or Polisy, is there any worthwhile value proposition to be considered for the Nokia hub? As mentioned previously, there is a post from another user which asserts he/she was able to take a stock 2nd generation Insteon hub, connect some wires from it to a serial card and use it as a PLM. If the poster is to be believed, no code changes required. Isn't that a worthwhile avenue to explore if PLMs are not going to be available for a long time or ever from the new owners of Insteon?