maxnorth

Thanks, Bob. This is very helpful. A couple of remaining points: 1. When EPA AQI is recalculated, which should happen each time GV0 changes, should I also expect to see the updated GV10 value in the log at that time? I don't. 2. My EPA AQI values are not always correct, either not updating when they should or miscalculating (I don't have enough data to tell which). Example: Over the last few cycles, I've seen PM values of 2.3, 2.4, 2.7, and 3.3, all with an AQI value of 12 and none with a GV10 value in the log. The correct values are 10, 10, 11, and 14. Just now, the PM value updated to 2.6 and I finally saw a GV10 value in the log of 11, which is correct. So, I guess my suggestion to you is that GV10 is not updating reliably when it should be.

Bob, I've just got a new eisy and PG3 up and running and am trying to decifer how this is working. I have previous experience with the PurpleAir api and calculating AQI myself using PM2.5_10minute. A couple of questions: 1. On startup, the server retrieves and sets the values for all variables (e.g., GV0-GV12). But I notice the log for the server does not report the updating of all values for each subsequent 10-minute polling interval. For example, it might report only GV0, GV3 and GV4, or something. I have tried it with different sensors and get similar results. Comparing this to results I get when I poll the api directly, it appears that your log is only reporting values that are updated/different than the previous values. Is this correct? I ask because my log also shows "error sensor: poll:loading stats" at each poll. I want to make sure it is operating as expected. 2. Are you pulling the stats only from the "stats_b" dictionary returned by the sensor? 3. The "EPA AQI" stat, or GV10, is not returned by the sensor but is calculated by the node server: Is that correct? I assume the calculation is derived from the PM2.5_10minute stat. What can you share about the calculation?

Overall, my upgrade experience was fine and I found the migration documentation to be fine. A few points to be aware of: - If you want the IP address of your EISY to be the same as of your ISY, as I did, then you might want to make that happen before doing the migration. In my case, I use static mapping in my Ubiquiti router, so I deleted the old mapping and added a new one using the mac address of the EISY. The EISY admin console itself does not permit static mapping anymore, but this worked fine for me. It's just more difficult to do it after the migration, as there will be more reboots and anxious moments. - I did not realize that the EISY now forces you to use port 8080 for http access to the unit rather than port 80. Unfortunately, I have numerous outside integrations using REST and such that all needed to be changed manually. For example, from "http://10.20.30.xx/rest/programs" to "http://10.20.30.xx:8080/rest/programs". - I did not realize that the EISY would break my integration with Homebridge, in which I used the ISYMaker and isy-njs plugins. This means it also broke my integrations with HomeKit and HomeKit automations. (And when a HomeKit device goes missing, a HomeKit automation using the device is automatically deleted, so it's a real pain to recreate them). These plugins simply would not work for me (and they are no longer being supported), even after changing the port to 8080. I am now implementing Home Assistant instead. So far, I can do everything I need to do in HA, and it's actually better in some ways as others have pointed out on this forum. - The experience with PG3 has been good. In many ways, I even prefer the experience with the Elk server to the old integrated experience. However, I was on an old version of PG2. So, migration was not available -- no problem. But delete your old PG2 servers before you install any PG3 ones. Also, PG2 authentication was not integrated with ISY, as it is now for EISY. So, your old PG2 password may not work on PG3. Use your EISY password to log in to PG3. Magically, many of my polyglot devices were preserved in the transition, in my programs, which reduced the editing task. - Be sure that you first do an export of all of your programs into a text file. This made editing programs for replaced devices so much easier. - A minor pain updating the network resources. Click on them to open in edit mode, then click save, then click save again at the bottom of the list of resources. I did this for each one just to make sure each was saved after I opened it. That was all that was needed.

Edit: This has magically started working again for me. No errors. Both LAN and Cloud options.

I am having the same problems. Cleared the java cache, all three boxes. Downloaded fresh start.jnlp. I am getting the "not found" error but am unable to open the admin console even though it displays my ISY. I rebooted the ISY, no change. I can log in to the admin console over the portal, and UD Mobile seems to work fine. I had not logged in to the admin console in several weeks, so I can't say when the problem might have started. MacOS

Thanks! Now that I know it's an issue, there are a number of simple fixes.

My ISY994 time adjusted fine to DST. But I noticed that all of my running programs stopped running. I have a number of programs set to run on startup and they were not running anymore. Most of these are of the "repeat every x minutes" formulation. Perhaps that is thrown off by the DST change? Perhaps there is some other cause, but it seems too coincidental that is happened at this time. A simple reboot fixed it.

I appreciate all of your efforts. Looking to make the move to Polisy and PG3 soon.

So, to summarize: PurpleAir will no longer work on PG2, but the PG3 version works with their new servers. Is that a correct statement?

I've been running the Purple Air node server on my RPi for the last year or so, flawlessly. PG version 2.2.1. About a week ago, it stopped connecting, with no change in config on my end. ("Connection issue: <Response [500]"). My understanding is that this is an issue on the Purple Air server end. If so, are others having the problem? (I've tried it with multiple sensors) If not a Purple Air server issue, is there something else going on, with PG2 being deprecated? I don't even see Purple Air listed as a PG2 node server anymore.

Yes, the PG2 list is not useful for those evaluating PG3. And the thing about the subforum list is that it simply contains placeholders for anyone wanting to post to the forum for individual node servers. This is useless for those of us trying to determine (a) that a particular PG3 node server has actually been released, and (b) how to quickly get to the GitHub page for the node server so we can compare it to the PG2 version and evaluate whether it can be deemed sufficiently functional for our needs. For myself, I can say that a rich PG3 environment will be the thing that pushed me to go with IoP. And the fact that a particular PG3 node server "exists" is not sufficient. I need to verify that it has the functionality needed for my environment. If I were UDI, I'd find a better way to make these PG3 node server details easily discoverable, as a way to ease the Policy purchasing decision.

Thanks, Michel. Do you plan to add anything to the migration section about migrating from PG2 to PG3?

I'll respond, but first some updates that relate to this thread more broadly: 1. I am now using HomeBridge (on Docker) with ISY Maker and exposing ISY variables to Homekit where they can be accessed by Siri shortcuts. Just "Get" the value of a variable in a Siri Automation. It has been completely reliable. 2. I am using the Nest plugin for Homebridge to integrate my thermostats into ISY. 3. Thermostat/Sensor changes can't be used as triggers in Homekit, so how to tell ISY that a temperature has changed? I use the Controller IOS app. It allows you to create shortcuts that use these things as triggers. But Controller does not play well with the Siri Shortcuts app, so... Create a dummy switch in Homebridge (Dummy plugin). Use a Controller automation to turn the switch on when the tstat temp changes. Then, create a Siri Automation that runs when the switch turns on and retrieves the current temp from the tstat and updates an ISY variable (via a set command) with the current temp. From there, you can use ISY programs to do whatever you want to with the variable, including having a network resource send a notification. Because Siri automations can be triggered remotely but run locally (local Homekit devices, like Apple TV, function as servers), I am able to use a local address (192.168.1.xxx) for the Siri GET/SET statements. I do not need to go through the UDI portal. Example: https://username:password@192.168.1.xxx/rest/vars/set/2/29 (where xxx is the local address of my ISY) 4. For ambient weather issues, I use nearby PurpleAir sensors and Polyglot, so that's a different workflow, which does not depend on HomeBridge or Homekit. 5. As to your question about "how" to write an IOS Shortcut that will call an ISY Portal entry, a couple of clarifications. I won't address the Alexa question (I would use Siri instead since it is always on my wrist). And I won't get into the details of writing Siri shortcuts, since that's a deep dive. But basically you first create a webhook at the UDI portal (Select Tools->Connectivity->IFTTT Webhooks) and set up an ISY scene, device or program to trigger on receiving a GET command. (For clarity, this does not rely on the IFTTT service at all). You might create one called "garage_open". Then, create a Siri Shortcut called "open garage door" that will send a REST statement to the Portal to trigger the command. That assembled command would look something like this: https://my.isy.io/api/ifttt/garage_open/key/your_portal_api_key

I have not tried to those apps. I'll check them out. Thanks!

Related: Does anyone know if Home Assistant will accommodate these use cases natively?

So, with ISY Maker. I'm trying to understand how it might benefit me. My use cases: - when the ambient temperature of my Nest thermostat changes, update an ISY variable with the value of that temp. -- This does not work because temp changes can't be used as trigger in HomeKit. (And if I can't get a native trigger, then I can't leverage the power of Shortcuts). - when Nest thermostat is changed from Off to Heat or Cool, update a ISY variable. -- This does not work because Heat or Cool are not recognized as triggers, only Eco On or Off. What am I missing? Even if ISY Maker enables me to create a variable with a "temp" service type, I cannot update it automatically, because the Nest temp change will not act as a trigger within HomeKit.

This process for retrieving a variable's value works for me. In my case, I simply want to know the value; I am not doing anything programmatically with it. 1. Create a network resource in ISY that will send a notification with the variable's value contained in the body of the notification. I use Pushover for all of my notifications and I include ${var.1.x} in the body of the notification, which will pull in the value of the variable (you will replace 1.x with your particulars, which I can see you already know how to do). 2. Create an ISY program that will activate the network resource. In my case, it has no IF or ELSE clause, just a THEN. 3. Go to ISY Portal and create an entry that will call the THEN clause of the program. 4. Write an IOS Shortcut that will call the ISY portal entry. 5. For my garage door, I want to know if the state is 1 or 0, and here is the text of my pushover message (without the API or user keys): "The garage door state is ${var.1.7} where 0 is closed" My implementation for my entire house uses a single Shortcut, but that's is a more complicated discussion. Also, @ahwman I've got a question for you about ISY Maker, but I will post that in another reply.

This may be overkill for you, but I decided I wanted to know if the AQI was increasing or decreasing. I have two thresholds, T1=50, T2=100. I am notified whenever the AQI goes above or below a T. My notification might be, for example, "the AQI in [city] increased above 50 to 62." So, to do this, I needed variables to store the current/new AQI and the previous AQI. By comparing the two, I can tell whether it is increasing or decreasing, and by comparing it to the threshold, which is also a variable, i can tell whether it went above or below the T. I used state variables, except for the previous AQI. To set the previous AQI, I simply evaluated the current AQI, waited 15 seconds, during which my comparison programs would run and my notifications would trigger, and then set the previous AQI to equal the current. The previous AQI is then available for the next evaluation. I did this for sensors in three different cities. I needed four network resources for notifications in each city (increasing T1, increasing T2, decreasing T1, decreasing T2).

Yes. Perfectly. Sent from my iPhone using Tapatalk

I have this same exact problem with polyglot on iPad and iPhone. Even though it logs in successfully, one symptom is that it is not possible to view the Polyglot log. It behaves as if the login is not complete/successful.

And keep in mind that the flicker can be caused by bulbs in other devices. That was certainly my situation. I'm not certain if it's only other devices that share the same KPL or not.

As the OP, I've got some good news for those interested in this topic. I have a single chandelier that uses 4 A19 bulbs. I had severe flicker issues and, to be clear, this was not related to dimming. The flicker would happen when there was sensor activity or other network traffic. I was using Feit. I replaced all the bulbs with Phillips Warm Glow, and the problem is now completely gone. What is very interesting is that my flicker problems on some other fixtures are now much reduced as well. I'm feeling much better about the prospect of replacing all of my incandescents with LEDs now.

I'm surprised that there aren't many postings here on the problem of LED bulbs flickering when Insteon events are transmitted over the power line network. This is a huge problem for me (maybe it's only me?). I'm increasingly worried about this as incandescents go away. My environment is ISY994 using only three-wire toggle switches and KPLs -- no two wire. I have the flicker problem both with A19 style LED replacements and with a couple of native LED fixtures I've bought (no bulbs). When there is traffic -- an Elk sensor triggers, for example -- the bulb flickers. It seem to flicker also where a program executes, at least where that program includes that fixture. True with toggle switches and KPLs. Nothing unusual about my wiring setup, as far as I know. I have not determined whether this only happens where scenes are involved or not, but it is possible. I don't seem to have the problem at all with R30 style LED bulbs. I have not tried the Phillips Warm Glow. Is this just a problem with using cheap bulbs, or is there some line filter I can use to eliminate the problem. It's really not acceptable in the current state.

Michel, This is interesting, but perhaps I am missing something. How does the notification program send an email if the internet is down?

It's been in use for 3.5 years after I replaced the capacitors. Not too bad. I've got a second one on which I have not yet replaced the caps. Are you saying that the new ones are likely to have a longer life? If not, I'll probably refresh my second one and use that.