carteriii

@Jimbo.Automates I try not to tag people because I know it can be perceived as slightly obnoxious, and this is not urgent, but I'm assuming at this point you may have simply forgotten about this and hope you can get back to it whenever is convenient for you. Thank you!

My other thread was automatically closed, so I'm effectively re-opening it with this new thread. The history is here: Where we left of is, you posted this screenshot, implying you can both test & set the chime mode: Unfortunately I do not see the chime mode static settings (e.g. "off") as selections. In my second to last post, I showed a screenshot of what I see when trying to test the value, which I'll include again here. Given the screenshot of yours immediately above, shouldn't I see a potential value/selection for "Off" in my screenshot below, where instead I only see Unknown, Silent, Single Beep, etc.? Thanks in advance!

I have a thought for your consideration . . . I upgraded from an ISY994 to my Polisy. Part of the process for this was creating a backup from the ISY994 that I restored to the Polisy via the admin console. Could it be that I'm only seeing menu selections that would be available on the ISY994, even though I'm definitely now running on the Polisy with the latest version of everything? That is a wild guess on my part, but at a minimum the upgrade situation seems potentially relevant.

@Jimbo.Automates I hope you don't mind me tagging you directly, but since you posted above, I'm hoping you can perhaps share a screenshot from your admin console that would confirm whether (a) I'm being stupid, or (b) something is missing from my installation. For what it's worth, I notice in your screenshot above that you are testing and setting 'Alarm-Elk / Home' whereas instead I see only the area name without the pre-pended alarm name. The only places I see a similar concatenation is with the list of tasks or outputs (e.g. "ELK Controller / Output-001"). My area "Main Floor" shows at the same level as the controller itself: I thought it might help to also post a screenshot of what I see when testing the chime mode. My area ("Main Floor") does allow me to test the chime mode, but does not show a value of "Off" as yours does. Instead I have "Silent" and "Single Beep" as you can see below. Does this indicate a version difference? IoX v5.8.4 shows a date of 2024-06-27 (shown in my earlier screenshot) so at a minimum it doesn't seem old. Any thoughts, or is it time for a support ticket?

I do not believe that I have that option. This is using IoX 5.8.4 on Polisy. To make sure I'm thinking of this correctly, let me first show a screenshot of the ELK plugin, showing the nodes, showing that "Main Floor" is my 'Area 1' (similar to your 'Home'), also showing the Chime Mode as GV2 that I mentioned in my first post: Now let me show a picture of the dropdown selection list in the admin console: I feel like I must be missing something obvious, but I can't figure it out. Perhaps I'm just being an idiot (it's been known to happen). Could IoX not be showing all the options? I'll paste the "About" from the admin console here, and you can see my ELK version in the first screenshot above.

The chime mode is clearly visible through the area.GV2 variable, but can we set that variable directly? When I create a program, the only options in the drop-down for setting the area are Query, Bypass, Clear Bypass, Set Armed Status, Set Poll Voltages, and Set Additional Trigger. Is there another way, or would this be considered a feature request? If it matters, my use case is similar to my use of Alexa announcements for doors opening (e.g. "the front door just opened"), but we've also used the chime since the Alexa announcements can have such a delay. I disable the Alexa announcements when we really want things quiet, and I'd like to be able to similarly disable (& later re-enable) the chime.

You (@Jimbo.Automates) were exactly correct that there were Python installation issues that support helped me address. The ELK plugin came up as connected as soon as everything was restarted, without needing to do anything else. I now see all the nodes for my system, and I am seeing logs. Now I need to finish my ISY994 migration, but the basic install & function seems to be working well. Thank you!

Ah, duh! Sorry. I really did do a recursive "find", but that directory cannot be viewed by even admin without a sudo so it missed it. Sorry. So interestingly enough, it says pip3 (called from line2 of install.sh) cannot be found -------------------------------------------------- Installation date: Wed Sep 11 13:34:33 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 12:23:08 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 13:03:47 PDT 2024 ./install.sh: line 2: pip3: command not found -------------------------------------------------- Installation date: Sun Sep 15 16:12:50 PDT 2024 ./install.sh: line 2: pip3: command not found If it matters, the only command in install.sh is "pip3 install -r requirements.txt --user" That led me to find this post, in which someone mentioned the symbolic link from /usr/bin/pip3: That in turn points to /usr/local/bin/pip-3.11 (which does not exist). lrwxr-xr-x 1 root wheel 23 Sep 15 16:12 pip3 -> /usr/local/bin/pip-3.11 From the previous forum discussion, I tried the following, which did not create a new symbolic link or update anything. sudo unlink /usr/local/bin/pip3 sudo pkg upgrade udx I've also tried to "sudo pkg install pip311" and variants like pip3.11 but can't figure out the name of the package through the udi repository. I've searched all these forums and done some google searching, but can't figure it out. If anyone knows how to install pip3, that would seem to be the root cause of these current problems.

Thank you! Where in the install.log? I just looked in /var/log, /var/polyglot/log, and /var/polyglot/pg3/logs and do not see it anywhere. I should add that I've also restored a backup of my ISY994 to Polisy, and that obviously used the ELK module. Do I need to delete the module from IoX before trying to get the nodeserver running? I haven't seen any wiki doc or post suggesting that, and I'm obviously hoping not to have to re-do all my programs from the isy994 that currently reference elk zones & conditions. I ran the upgrade packages and according to that log, nothing had to be updated. I rebooted anyway and don't see any change. I did note that the logs include the question, "Is client running?" when it says that the log file doesn't exist. Below are the log lines from when I clicked to stop the ELK plugin and then start it again, and that "Is client running?" line is the last of this section that I've copied. 2024-09-15 14:44:06.234 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: stopNs 2024-09-15 14:44:06.260 [pg3] info: [ELK(1)]: Stopping Nodeserver 2024-09-15 14:44:06.261 [pg3] info: call_udx: Making request to socket with url /rest/pg3.stop.ns 2024-09-15 14:44:06.574 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:06.582 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:19.062 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: startNs 2024-09-15 14:44:19.073 [pg3] info: startNs:: ELK 2024-09-15 14:44:19.074 [pg3] info: startNs:: ELK is valid 2024-09-15 14:44:19.342 [pg3] info: checkLicense:: ELK Valid subscription license found. Expires: 2024-10-11T20:33:48.000Z 2024-09-15 14:44:19.356 [pg3] info: startNs:: ELK finished update check 2024-09-15 14:44:19.359 [pg3] info: startNs:: Starting ELK 2024-09-15 14:44:19.360 [pg3] info: call_udx: Making request to socket with url /rest/pg3.start.ns 2024-09-15 14:44:19.395 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:19.402 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:19.537 [pg3] info: startNs:: ELK starting polls 2024-09-15 14:44:19.543 [pg3] info: Starting ELK Expire Check timer 2024-09-15 14:44:19.545 [pg3] info: Checking if ELK has expired 2024-09-15 14:44:19.545 [pg3] info: Starting ELK Info timer 0 2024-09-15 14:44:19.558 [pg3] info: startNs:: ELK updating database (enabled, timestarted) 2024-09-15 14:44:19.559 [pg3] info: startNs:: ELK started. 2024-09-15 14:44:19.733 [pg3] info: Received commands on topic udi/pg3/frontend/system/admin: getStoreEntry 2024-09-15 14:44:19.740 [pg3] info: Getting Node Server store entry for nsid c7297a6e-f1c6-4c12-8b66-532a6721431a from store Production 2024-09-15 14:44:51.402 [pg3] info: Received commands on topic udi/pg3/frontend/ns/admin: startLogging 2024-09-15 14:44:51.409 [pg3] info: Is client running? /var/polyglot/pg3/ns/000db9552474_1/logs/debug.log does not exist.

Running PG3x 3.2.27 with a brand new install on Polisy. Added ELK trial plugin. I entered config information that has been running on ISY994 (so I know what the user code it and it's right, and host is 192.168.1.15:2101 and I know 2101 is right and it still works from the ISY994 module). I did not enter a value for "outputs" since I haven't been sure what that is. ELK 3.10.15 shows disconnected, so I want to debug. I click the button/tab for "Log" and always see the message, "Starting events log", but never see any things displayed to the screen. I switch the log level to "Debug", and I have rebooted everything, including the Polisy itself. When I click to, "Download Log Package", I get a message that /var/polyglot/pg3/ns/000db9552474_1/logs/debug.log does not exist. I ssh to Polisy and found that the "logs" folder doesn't even exist: I'm clearly missing something, but have no idea what to try next. Why don't I even get any logs? Any suggestions? Thanks in advance.

Update. This morning is two weeks after I posted here, and "magically" the announcements started working again. Based on another thread in these forums, I did call Amazon (2 weeks ago) and go through the pain of getting to a human and "filing a case", but I cannot know whether they finally got around to it or if something else on their end simply refreshed. I guess it's good confirmation that there was never a problem with the ISY Portal or my ISY, but it's also frustrating that this could happen at all. Thanks to everyone who helped me here, contributed to previous discussions, and even read this thread!

The java update and updated start.jnlp eliminated the "Not Found" error. My JRE install was only a few updates old, but my previous start.jnlp appears to be about 2 years old so I went through the full process you outlined. Thank you. I have not made any network changes in a long time, BUT I live in California where the recent rains caused MANY outages of my internet service provider (Cox, who gets their hardware & software from Comcast, so they don't even have experts to know what is happening, and whose support is even more useless than you'd expect). In the past month, I've had at least 5 or 6 extended outages, and at least twice last week which could coincide with when everything stopped. Unfortunately that didn't occur to me at the time I started debugging. It's still purely a guess on my part, but that likely caused the problems. As you pointed out, I have disabled & re-enabled the skill, re-created a few Alexa routines (not all), and I even defined an entirely new state variable with an entirely new Alexa routine, yet the routine does not fire even though the state of the contact sensor is clearly getting updated from/through ISY Portal. This now appears to be 100% an Amazon problem, and I fought through their support system to get a ticket logged because of course the phone support person wasn't able to do much more than help people. Maybe things will magically start working again in another week or two as it has for many some other users in the past. I did just check my Portal license and it's good now, but looks like I need to update in the next month. My licenses imply that I've had all this running very stable for about 4 years now. Nice! Now I just need to get un-lazy and upgrade off the ISY994.

My routines are still not triggering "when" the ISY "contact sensor" is opened. I even created an entirely new variable, new device contact sensor on the ISY Portal, and it all shows and updates properly according to the Alexa app. Ironically a Google search returned a link back to this forum which I missed when searching here. It seems others may have experienced a similar problem in the past with Amazon simply not properly triggering the "when" condition of a routine. I clearly cannot be certain, but it sure feels like this now. For future reference, I thought it would be useful to include a link to the previous discussion. https://forum.universal-devices.com/topic/38947-alexa-motion-sensors-not-triggering-routines/ https://forum.universal-devices.com/topic/42386-routines-not-working/

I just deleted a routine and re-created a routine from scratch, but it still doesn't play the announcement even when I open the door AND I do see the status change in the app. That seems to clearly imply it's now an Alexa problem. The announcement does work when I press the routine "play" icon in the app, but the routine doesn't seem to fire when the door itself opens, even when I am looking at the door contact status in the app and it shows the change. I'll now keep playing with Alexa, and maybe it needs some time for the routine to truly become active with it's "when" evaluation. At a minimum, I do feel whatever was previously NOT updating the device state in Alexa is now working. I'm assuming you saw or did something to get it going and would love to know what you saw. Thank you! I'll post an update after I keep playing with Alexa more and see why the routine isn't firing.

Yes! I now see the state change. Having said that, it seems to be new behavior. Did you change anything? I'll include a screenshot below that shows one door status had not been updated for 3 days (Feb 21 in the screenshot and it's now Feb 24), but when I just manually updated the state variable, it changed, and now when I open the door, it also changes (as it should). I'm still not hearing the announcement, but I'll try deleting the routines that do the announcements and re-create them again to see if things now work.