oberkc

I already have such a program and have had for several years.

Has anyone updated to this latest version. My update to the version before this one created some problems which cost me several hours to fix and my confidence in these upgrades is shaken. I am hesitant to upgrade again without some confirmation that it is a smooth process.

Well, I can tell you that not too long ago, mine had the status for a few parameters, including motion. Blank is a relatively new thing for me. Mine is a hard-wired doorbell. No battery. Thank you both for the responses. Perhaps mine is working fine without the expected parameters being displayed. I know the other night it did not trigger and my wife was not happy. In the past, this has been quite reliable.

@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.

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.