maxnorth

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.

Update: I checked the PLM Links, and there were none. I Restored PLM and got back 557 links. All seems to be working at this point. Am I correct to assume that this is an early sign of PLM failure? Or is there something else that could cause a loss of the links table?

I've been running 5.0.16 for some time with no issues. In the past few days, all of my wireless devices (2844-222 motion sensors and an open/close sensor) have stopped communicating with the ISY. They flash when detecting motion, but the ISY status is not updated. Apart from this, the ISY is performing just fine: programs are running, network resources are working, Mobilinc, Alexa voice commands, etc. All except the wireless devices. I'm also running Polyglot on a Pi with no problems. The ISY reports zero bad blocks with the SD card. I have rebooted the ISY and PLM. The only issue I'm seeing in the error log is a phantom network resource file ("could not find file /conf/net/64.res") and some http error ("TCP Client Read Response Failed, Net Module Rule: 48"), which I believe is also related to a network resource. Resource 64 does not exist, and resource 48 seems to be working just fine. I suspect these errors are unrelated to my wireless device problem. Ideas? It seems strange that only the wireless devices are affected, but could it be the PLM?

Not sure what's going on with this thread. Maybe the OP wants to restate. As I understand it (please let me know if I am off base), the question is, how to detect if the light was initially turned on by the motion sensor (MS). If it was, turn the light off in 2 minutes. How to do this? 1. When (if) the light is turned on by MS, set an integer variable to 1). This is "On by MS variable". Start the timer program for 2 mins. If "On by MS variable" is zero, the timer program does not start. 2. Use control MS On as a trigger, or create an MS On state variable changing from zero to 1, to detect when the MS turns on. 3.The timer program says that if status of the light is on and the motion sensor is off, and "on by MS variable" is 1, then wait 2 mins then turn the light off. (Alternatively, set the wireless MS to "on only" and use a state variable and timer to track whether the MS triggered On n seconds ago). 4. Create a "manual off" program, whereby when the switch is manually turned off, then "On by MS variable" is reset to 0 (and the light is turned off). 5. Create a program that turns the light off every x minutes where "on by MS variable" = 0, just for those manual switchers that forget to turn the light off when they leave. 6,. I also tend to create "timer override" program that stop the timed off program if I turn the switch "On" when the light is already on. I set an integer variable to 1 in that case, and It's handy way of stopping timer programs when you simply want the light to stay on indefinitely. In that case, you also need a "manual off" program that resets that variable to zero when you manually turn off the light. What am I missing?

Thanks, Paul. Yes, unplug and then plug back in. I had noticed that the wiki instructions for replacing your PLM (as I have done a couple of times) specify plugging the PLM in first so that the ISY does not get confused, which is why it occurred to me that perhaps there was a sequencing issue. This only happens to me sporadically.

We have frequent, short power outages where I live. I do not have a UPS for my ISY or PLM. I've had multiple instances after a power outage where I have poor device communication after power returns. I have solved these by manually rebooting: PLM first, followed by the ISY. It appears that if both these units reboot simultaneously without intervention (as would normally occur when the power comes back on), then the system does not function properly. If this is the case (I'm asking), would it not make sense for UDI to change the ISY firmware so that there is a reboot delay, giving the PLM time to reboot fully first?

Same problem in California. All skills and SmartHome, not just ISY.

Thanks very much for the detailed explanation, Taken. This is now working for me.

I do not understand step 2 in your instructions. I do not have that option in my File menu in the Admin console.