oberkc

@Geddy Thank you for the response. I reauthenticated and restarted as well. I also saw on the instructions the the PG3 remote settings (in portal account!!?? I guess this node server does not work without portal account.) must be "enabled and active". Mine was enabled, but not active. Somehow, (am unsure what action, if any, I took that caused this) I was eventually able to get it to show "active". My test result now shows "success", but the motion node still remains blank: I am not sure whether this suggests that IoX is not seeing the various states of the motion sensor node. If I cannot figure out what is happening, I may start a new thread, as you suggest.

You showed a picture with a single box having two Insteon (and an additional third) switch, which does not match the illustration. And the wires in the pictures of the ceiling boxes don't match the diagram. Still, I can tell you how to modify the wiring in the illustration. Whether or not this matches your installation, I will leave to you to decide. I am not sure that it does. In theory, each Insteon switch requires a constant line input and neutral. One Insteon switch will directly control the load (the two light fixtures in this case.). The other Insteon switch will not be connected to any load. The two Insteon switches will be put into a scene, with both as controllers. Left switch box: connect lower black conductor to upper black conductor and to Insteon black wire. Connect lower white conductor to upper white conductor and to Insteon white switch. Connect Insteon red wire to upper red conductor. Upper left ceiling box: connect all white conductors together, and to fixture screw (this would be the neutral). Connect upper-left black conductor to upper-right black conductor. Connect upper-left red conductor to lower-right black conductor, and to other screw on light fixture. Upper right ceiling box: connect lower left black to one fixture screw. Connect all whites together, and to other fixture screw. Connect upper left black conductor to upper right black conductor. Put a wire nut on upper left red conductor, not connected to anything else. In lower right switch box, connect black conductor to black wire on Insteon switch. Connect white conductor to white wire on Insteon switch. Put a wire nut on the red conductor not connected to anything else. Put a wire nut on Insteon switch red wire. Tie all bare copper conductors together, in all boxes, and to Insteon switch bare wire. Cross link the two Insteon switches, making each a controller of the other. Good luck.

I cannot see from the pictures (sprayed texture and other obstructions in boxes makes it difficult for me to identify source of the various conductors). For me to even attempt to help, I would need to identify total number of "cables" (cables will have either two conductors, black and white, or three conductors, black, white, and red. Ignore bare copper conductors.) coming into each box and to what each conductor is connected. Does each switch control one fixture? You mentioned "three way". Are there other switches that control these fixtures not shown in any picture?

Nice picture. Is this a ceiling box? You want to install a switch into a ceiling box? Will the switch be wired to any fixture? What was here before you opened it? Do you have an idea where any of those wires go on the other end?

I do not know whether this is related to your issues, but I experienced a problem when the hue plug-in upgraded versions (I was already on IoX 6). Upon the plug-in upgrade, none of my existing hue nodes worked, but the upgrade process created duplicate nodes that did work. Unfortunately, I had to recreate all scene definitions and programs that were affected by the change in hue nodes and delete the old, non-functioning, nodes. One thing I can tell you is that the hue plugin appears to still work on IoX 6 for me.

I have 1.2.6. and ring doorbell. As of now, the motion sensor node has no status or any other parameters showing. If I test the primary "Ring" node, the test result is "failure". Programs based upon the motion sensor are no longer triggering.

When I upgraded to 1.6.3, all the existing nodes in IoX (including scenes definitions and programs) ceased working and each of the former nodes had a duplicate created with different node numbers (without duplicating the scenes or replacing in programs). Has anyone else experienced this?

Log coming soon. No space before the 5 in the local client ID.

I had to get a replacement local hub (original local hub would not show "online"). I now have the 1606 hub installed, online, and apparently running. I can control or see my four yolink devices on the Yolink app. I have installed the production node server, version 1.6.2 (free version for now). I believe I have correctly configured the node server, having added the necessary custom configuration parameters. The node server shows a single node The node server shows up in IoX admin panel but shows status "offline" and "initializing". I have not found a way to cut and past between my iPad and computer, so I have carefully transcribed the various parameters, but it is still possible I have mistyped or misread one or more (I have double-checked each). I will continue to double check these parameters against the app. I have restarted the node server several times along with IoX. Is there something I am missing?

My upgrade was smooth, as well, and I have some z-wave devices. To be clear, however, I had the z-matter board. I am not sure if another type of zwave dongle (such as the zooz) affects the upgrade process.

Is there something other than devices that you would like to delete? I hane never noticed an option to mass delete a select group of devices, or to delete all.

Yes. I am not in a position to refresh my memory on exact details, but there are predefined variables that include month of the year day of the year day of the month, name of the day and similar kinds of things holidays that are on a specific date are quite easy independence day, for example would be month equals seven and day equals four Thanksgiving, on the other hand was a bit harder to program for me, at least. Fourth Thursday of the month of November took a bit of creative programming. Most other holidays in the US are a bit more straightforward. Hopefully, someone can provide more specific details on where those predefined variables come from. I think somewhere system values and others were node servers. I also have a vague recollection of a node server that blinked up with standard holidays or with Google calendar. If I am recallingcorrectly, this is a potential option as well.

Unfortunately, I believe different brands of zwave devices have different parameter settings and I have only found them in the user manual for the various devices. I would have guessed that yours might have had a parameter for default ON levels and, once set, telling Alexa to turn on the light would have resulted in the light coming to that default level. I looked up parameters for one of my zwave switches and found that there is default level parameters for when you toggle the switch but separate default level parameter for when the switch is controlled by another device: Basic Set Custom Brightness On Parameter 34: Set the custom brightness level (or leave the last brightness level) for for Basic Set ON commands when the ZEN72 is triggered by another device in direct association. Values: 0 – last brightness level; 1-99 (%). Default: 0 Size: 1 byte dec Perhaps your switch has a similar parameter?

I am having the same concerns.

This is normal from my experience. As Diesel points out, Insteon devices can only be a controller of one scene. To my knowledge, I have never seen such a popup message. This makes no sense to me.

That has been my experience, as well. I have not gotten this to work, nor in distinguishing "control" vs "status" conditions of zwave devices in programs. At this point, I have decided not to use zwave devices in this role.

Hue plug-in is SOLID for me. They are among the most trouble-free devices I have under control by the EISY and previous versions.

Open Alexa app. On the lower left are some options that include one that is short parallel lines (settings, I assume). From there is the "skills" option. Scroll down to "my skills". Scroll until you see the universal devices skill, which should show you the version.

This is a good point. My experience with the transition from the ISYwas not exactly trouble-free, and much of the struggle was with Z-wave side of things. You describe your z-wave devices as "a few". If "few" means not to many, it may be easier and even beneficial to simply remove them from the ISY network, factory reset the z-wave devices, and add them back.

Not mentioned is the reliance of the hub on the internet and cloud services. Such devices run the risk of becoming a door stop should the cloud service cease to operate. I have always considered local operation to be a major selling point of the ISY series of controllers.

Has anyone noticed a "matter" option on the new hub? I don't believe it yet works, but suspect this is a sign of things to come.

@Panda88: I have yet to install the new Yolink hub. I have had some other issues (such as moving over to the EISY from Polisy) to work out first, but I would be fully understanding of a second Yolink plugin specifically for the local hub, keeping the original version for the original hub. The only downside I could see for you was maintaining two versions.

update...I never did get Polisy to add some matter thread devices (specifically, the nano leaf bulb). I was able to add a govee matter device and a GECync matter device, but I think they were matter-over-wifi. I migrated to the EISY recently, and the matter-over-thread now seems to work. I am now able to add the nano leaf bulbs.

Are you able to access the dashboard for polyglot? Assuming so, can you find the plugins store? Assuming so, can you find the plugin for Govee? Once found, do you see how to install the plugin? Also, in the store listing for each plugin I would expect a "more info" option. From there you will often find some very basic instructions relevant to each plugin. For Govee, it takes you here: https://github.com/UniversalDevicesInc-PG3/udi-govee-nodeserver/blob/main/README.md Once installed and set up, mine found the three Govee devices that I have and once found, the IoX showed the Govee devices as nodes, which can be used like the Insteon or zwave nodes in programs and scenes (with some limitations). Hopefully, along with the response from @dbuss, this will get you started.

I have had some luck adding zwave devices when close to the ISY, then moving to the final location. Many of my zwave devices have additional nodes for which I have no known use. I think some can be used to build zwave scenes, but have never had much luck with this. I suggest ignoring them if you can otherwise make your device function as desired.