larryllix

Does your "Status 'Open-Close / Shed-Opened" show 'On' in it's device status page?

I don't think Alexa knows the difference between scenes, programs and devices so you cannot overlap names at all. Only at some point in the portal to ISY is the scene, program, or device differentiated. Click "discover" in the setup app or say "Alexa. Discover"

It is quite ironic that the most automated things take so much manual effort, at first.Who reads the manual though?

Post one of your programs that is responsible and people can take a look at the logic.Right click on the program in the program tree and select "copy to clipboard"

Sounds like it fits the bill perfectly! So you can trigger the thing with a Network resource from ISY and have the power cycle to ISY, then? hmmmmmmm... trouble with that logic is if you can remotely cycle ISY or have ISY cycle itself then ISY and router, or just ISY, is functioning reliably enough to do it. I have to assume it can do this on other stimuli, also. The sequencing sounds good. I find the Echo doesn't sync up with my router and gives up.

Have you run test notifications to see if the messages are still being sent out, identifying whether the problem is in the programming or the email system?

Yeah and it's always a case of where do you mount the silly relay, get an expensive box and clamps, terminal block etc... It all adds up project wi$e. Never tried it but, ISY cyclic query an OnOff Module, used to control the device?

SynchroLinc detect and report loads over a certain programmable level. The trouble there is when the circuit is dead it can't report in but there should be ways to detect that if the turn on event is known and it doesn't confirm it. The usual way is a IOLinc and a 120vac relay to get a dry contact to feed the IOLinc.

I always though there should be a way to modify or purchase an Insteon module / watchdog that would contain a monostable watchdog circuit to power cycle anything plugged into it. To use this would take an ISY program to hit on it every say 1 - 5 minutes, maybe user programmable, and if no "hit" is experienced it would switch the load off, wait 30 seconds and then power it back on. This could be used for routers and ISY itself for catastrophic failures, should one ever occur. This would be really cool of somebody could find a simple capacitor addition mod for an OnOff module. A charged cap to hold the relay on and an ISY program t flash the module on and then off every 3 minutes keeping the cap charged. May take some cutting of PCB lines before the relay driver transistor. Please note I never mentioned Brian at all.

That sounds really cool and a real step toward voice control Mr. Chekov. The only two commands available should at least be located together, not one at each end of a potential 500-2000 line document / list. I wouldn't have had a duplicate list so long if the disabling of the skill had worked as stated:. "Tip: You can forget all devices by disabling the skill in the Skill section of the Alexa app." As you posted, it's a done deal now, and it wasn't that big of a deal, just annoying that the function was so hard to find and differently presented than the "Discover" function. I would have never looked there and wouldn't again in future but now I know, just in time for it to be changed for next time. Thanks!

I found the spoken in Admin Console was a complete dud, not functioning Run this instead https://my.isy.io/index.htm Then use "alexa. Discover"

I said "forum", using it in an analogy to demonstrate the ridiculousness of the hindsight advice, by exagerating one of the aspects involved, to exemplify my point. The new kids should be scared, with pages that are thousands off lines long and the advice is to read it all. But they are not scared, as that is the way they are raised today. You just hack at it and research only when needed. Sometimes we need to get things accomplished and not dilly-dally with details along the way. I had a boss like that once. Instead of using an IC by the specification of the I/O he had to study the internal chip schematic and never got past the basic logic gates. That's is just the way it is these days of GigaBytes of information coming at us and no instruction manuals or directions, typically.

OMG! Now I have to read the whole forum before posting? What manual? We don't expect luxuries in this ground breaking field.

Thanks Stu! I would have never found that at the bottom of several hundred devices listed....and I didn't, even looking for it, thinking..."this is ridiculous". but... where there is a Stu will there is a way.

I didn't receive any notice but I may have installed after the notice. I just wish the remove all devices button was at the top of the page instead of underneath a few hundred lines of devices. It takes a long time to delete that many devices, one at a time, with confirmations.

Typo there. Probably a slip of the logic tongue If you know you never would want to use the variable you are creating as a condition program trigger, go ahead and make it an Integer, but if you think you'll ever need to use that variable to trigger a program, make it a state variable; you can't go back and change type later. All variable types can be used as a condition, just not a trigger.

State variables, when the value chnages, cause ISY to run through your programs looking for usage of the variable that changed and evaluate the condition logic and run Then or Else, depending on the outcome of the logic. Integer variables do not do this so you can use hundreds of them and not slow down your ISY trigger engine. BTW I use two variables called $cTrue and $cFalse permanently set to ...you guessed it... 1 and 0

I had written a series of programs to do just what you are doing using select temperatures, finer in the areas of interest and coarser outside those ranges. Here is my preferred source and program to sample the humidity from Venstar stat ->NodeLink -> ISY variable. Sync.inHumid.Venstat - [ID 00A3][Parent 0101] If $VenStat.updating is $cTRUE And 'Gathering Room / GathRm VenStat' Humidity <= 65% And 'Gathering Room / GathRm VenStat' Humidity >= 15% Then Disable Program 'Sync.inHumid.Insteon' Wait 10 seconds $sHouse.humidity Init To 'Gathering Room / GathRm VenStat' Humidity % $sHouse.humidity = 'Gathering Room / GathRm VenStat' Humidity % Else Wait 10 seconds Enable Program 'Sync.inHumid.Insteon' If the Venstar comm fails I fall back to a direct Insteon thermostat. Notice the "disables" of this program in the previous one? Sync.inHumid.Insteon - [ID 010B][Parent 0101][Not Enabled] If 'Utility Room / Util Therm' Humidity <= 65% And 'Utility Room / Util Therm' Humidity >= 15% Then $sHouse.humidity Init To 'Utility Room / Util Therm' Humidity % $sHouse.humidity = 'Utility Room / Util Therm' Humidity % Else - No Actions - (To add one, press 'Action') For the Network module method you use a Network Resource containing a URL with device value substitution that writes the parameter directly to an ISY variable using it's REST interface, documented in the ISY wiki. So IOW, ISY talks to itself. Yes you can go back to ISY v4, but once you have written programs using the newer features you will not be able to support them in v4. V5.0.4 has a few parameters missing from device status pages yet, needs some gui tweaks to clean it up (boxes off small monitors screens), but has never failed me in months of use. All program stuff works flawlessly from what I have seen. No, v5.0.4 is not even beta, but rather alpha. UDIs alpha code is still more polished than many small company's finished products, from my experiences.

All the temperature, humidity and set point synchronisation programs can be replaced with one for each parameter (3 programs) with v5.0.4 or using the Network module. Temperature grab/synchro programs from 88 degrees and up all have logical errors in them and cannot function properly Initiating programs are all disabled and could not have ever triggered, as listed. No program would ever run. Turning the A/C warmer, while not home would never work for me, as I would just live in a hot and humid house. Our humidity peaked at 92% on Tuesday and allowing the house levels to rise takes days to recover back to a comfort level. My A/C runs about 90% of the time to keep the house regulated, by design. Less on time duration ratio does not remove the humidity and molding may result. This may make more sense in the western provinces or states where humidity isn't a factor, and temperatures can be reduced 10 degrees F in an hour or two. Here that would be 36-48 hours minimum.

If the ZTH stats were $39 it would make more sense. I blame the stats as well as UDI for not having support for these devices, years after release to the market. I have one earlier firmware that works almost perfectly except for when I upgrade ISY firmware. It did correct some of the parameters dropped when I factory reset it. This was not unit as the subject of the previous posts I made but a second unit.

Thanks!!! Switched over to v2 but I had to delete every old device/program/scene as the discovery duplicated everything. They were all listed as xxxxx(offline). I could not find any way to mass delete previous devices. Are the thermostat patches compatible with NodeLink devices?

If my A/C could only run 15 minutes per hour I bought too big of a unit or I don't need one at all. You could do a text save of the programs and zip it it leave it raw for examination. Having thought about many HVAC algorithms, myself I would very interested in seeing what you have done. Heck, I even have cold well water running through my concrete floors.

Those variables are only available to special people.

These synchro programs can be difficult to keep running despite power blinks and user interaction causing them to stall. This is how I do it. Note I use scratchpad variables to do my calculations so programs don't uselessly trigger from the final state variable. Set MM.DD - [ID 00B8][Parent 0006] If Time is 12:00:01AM Or Time is 3:00:01AM Or Time is 6:00:01AM Then $sISY.DayOfWeek Init To [Current Day of Week] $sISY.DayOfWeek = [Current Day of Week] $sISY.DayOfMonth Init To [Current Day of Month] $sISY.DayOfMonth = [Current Day of Month] $ISY_Date.scratchpad = [Current Day of Month] $ISY_Date.scratchpad /= 100 $ISY_Date.scratchpad += [Current Month (Jan=1, Feb=2, etc.)] $sISY.MM.DD Init To $ISY_Date.scratchpad $sISY.MM.DD = $ISY_Date.scratchpad Else - No Actions - (To add one, press 'Action') I use the resultant $sISY.MM.DD variable for Christmas lighting and other annual events program triggering.

I hope you realise that 4kW off a 12 volt battery is almost impossible! At 80% efficiency you would be drawing 420 amperes off a 12 volt battery bank. If you have any impedance or a battery that isn't rated at way over 400-500 amperehours your impedance in just the battery will probably never afford it. You will need huge wiring and do NOT solder connections as solder is a poor conductor and recommended against by any power connection industries. It can vaporise and explode on heavy currents.