larryllix

I doubt ISY will ever see multipermission levels on the current box or underlying OS. UDI is busy porting ISY to polisy and HTML5/CSS/js and a third party OS.

I use Alexa commands to activate my security system and deactivate it now. Works better than the keypad when you have your hands full. I don't use routines for any sequences. I prefer ISY for that as @Goose66does.

Ever think about cutting his web access off in your router? Most routers have complex routines that can cut off/restrict/block by IP address, URL, timeframe, wording etc.. combinations. It might be easier to just kill his MAC address at bed times. I don't know if they can work independently though. He certainly couldn't play multiplayer games. My kids are big on those but at 43,41 and 35 they need to find their own way now!

Nice and exactly what I was thinking but..... just thought of another method...maybe? Two programs so that the syntax would go like this. Alexa set lamp timer to 15 Sets the variable to 15 (minutes) Alexa turn off lamp - Runs Then or Else of a program labelled "lamp" The On is immediate On/Then while the Off/Else looks at the timer and if = 0 does it immediately or runs your countdown. Hopefully this could be "logic'd" out in two programs. Put the -1 line below the Off action?

Those are fuses. When the fusible link blows, the spring retracts and allows the fuse "door" to fall down, making it obviously visible to the lineman. A line surge can be absorbed by the transformer the fuse feeds, when the high voltage saturates the transformer core. This helps limit the high voltage induced into the lines going into your house also. This can cause the fuse(s) to blow sometimes when the transformer acts like a short.. There also some comm antenna on the post so the utility likely knew about it within minutes. See the small loops in the end of the fuse? The lineman will use a switch stick, a long fibreglass stick with a hook at the end, to close the fuses after replacing the fusible element. This gives him/her some distance from the blast, should the fuse blow again. Some fuses have explosive powder in them to accelerate the speed of the gap widening upon a fault. This reduces arcing in the fuse element. You don't want to be close to them when the explosion happens. Just looking at Teken's video. That is what happens when the explosive element doesn't fire in a fuse. There was no transformer there, (possibly a "metering unit" with very small transformers/CTs) just a failing fuse. Underneath was a three phase riser where the phases would go from air gap insulation into insulated conductors to go into the ground somewhere. The insulators have some semi-conductive material inside to adapt the change in impedance from free air conductors to a "shielded" conductors. Sudden impedance changes tend to make lightning and surges reflect back down power lines and cause standing waves, which can increase the voltage of the disturbance.

I have used a few methods to avoid negative tallies. Here is the simplest. Meter Output - [ID 0010][Parent 000E] If Elk Zone 'Water Meter' is Violated AND $Water_Remaining > 0 Then $Water_meter_daily += 1 $Water_meter_Monthly += 1 $Water_Meter_Output += 1 $Water_Remaining -= 1 $Water_meter_Monthly Init To $Water_meter_Monthly $Water_meter_daily Init To $Water_meter_daily Else - No Actions - (To add one, press 'Action')

The phrase is incorrect and should have read. "The program's conditions can be reevaluated each time a Wait statement is encountered" Unless some trigger is involved, nothing is re-evaluated anywhere. ISY is a trigger based engine from end to end.

Right click on your program, copy to clipboard, and then paste here.

I played around with the SET verb in the ISY Portal thinking I could create a variable timer in ISY programming. It can be done but the verbal needs to include the word PERCENT and sounds clumsy. Alexa ...set lamp off to 32 percent Can cause a "lamp off" named variable and cause a device to turn of after a 32 minute timer.

Alexa has a sleep timer but I am not sure whether she will use it on devices. It works on cloud music she plays. Alexa... play some sleeping music. Alexa. set a sleep timer for 30 minutes. Alexa will respond with a confirmation of turning off the music. I would use ISY so haven't tried it.

All my lighting devices, including ApplianceLincs, OnOffLincs, LampLincs, SwitchLincs are mostly all original from six years ago (Jan 2014) . I have had one OnOffLinc module send out bad codes, instead of NAK, which a simple power cycle cured for about three years ago. Other than that no basic lighting modules have ever given me problems or needed replacing. However, I had had a SynchroLInc burn out, a KPL act up when new and was replaced, 3-4 MS I units go nuts/bad and need replacing, a iRLinc came with reversed sensor wiring and also would never program from ISY, but never any basic lighting or appliance components became questionable. What else would basic lighting components ever want? Temperature sensor functions that show the internal heating of the electronics? Power consumed of the 100 Watt bulb screwed into the fixture connected? An occupancy sensing SwitchLinc Dimmer?...OK I'll give you that one. While I agree SmartHome has really become a deadbeat company, what we really need is the fancy stuff, especially battery operated devices instead of the junk they accept from Chinese developers, with no QC at all. I won't go into a gadget company trying to understand what a thermostat is supposed to do.

Did you .... Alexa...discover ? Sent using Tapatalk

I found I had more problems with routers that did not want to heal well with devices. I never found the ISY to be in that category. I found Venstar stats the worst and the router had to be rebooted followed by a complete power cycle of the stats almost every time. Later I discovered soft rebooting a lot of things didn't work mostly. A few routers and dozens of router upgrades, and a different brand of stats later, things have settled down a fair bit now. I discovered my UPS didn't like the power blinks we get here (rural with high winds) made some equipment reboot and some lasted through it. My router seemed to be especially bad with a 10 cycle grid switch over caused by a 1 second grid blink so I adjusted that to about 3 cycles for UPS switchover. Yeah I run a 6KW 48V 125Ah battery carry over system but only use it for my router, TV, select lights, and select receptacles but not my ISY. I fear the grid supplied PLM to UPS fed ISY would cause serial port burnouts and I would lose my ISY or PLM on a regular basis....maybe. Rebooting ISY is a b/tch as there is always something that isn't perfect and it takes a lot of logic sweating. There is always something more.

What would a running ISY control in a power failure and a dead PLM?

Yes. That was my point. It doesn't happen with ISY arithmetic. It appears the NS pulldown menu with the value groupings are not being substituted into ISY's arithmetic capabilities properly. This suggests that the NS substitution table is incorrect, not ISY arithmetic processing. I don't use this particular NS, but the ones I have tried (including NodeLink), and logical deduction, tells me the pulldown menus do not deal with actual displayed values, but rather only a numerical representation of each value or group of values. I have written ISY programs utilising this fact where say an ecobee climate style is represented by 0 - 5 but the human sees. 'Away' ,'Home', ''Sleep', etc.. eg. If stat mode > 0 would include 'Sleep', 'Home', 'Wee Hours', Extreme Cold' etc.. IMHO this is the case of this, and all, NS/device pulldown values also. The OP is dealing with 0.000-0.400, represented as value 0, 0.401 - 0.500 as value 1, 0.501 - 0.550 as value 2, and so on. Where the actual value substitution is made is unknown to us, but IMHO is where the bug is happening. Other NS users have not reported this.

@kclenden I have experimented with three decimal place variables against 1 decimal place variable and vice versa. The precision conversions always worked flawlessly. Since the OP program is showing three decimals of precision in the comparison, along with superfluous zeroes, I have to conclude this is a problem with the NS supplied values and not ISY arithmetic, or precision conversion. When a floating decimal value is used in any 'If' section comparison, the trailing zeros are always truncated and never displayed, as in the OP program. These must be predetermined pulldown menu values supplied by the NS. In the If line: 'PolyGlot / WeatherPoly_Acuparse / WeatherPoly / Precipitation' Daily Rainfall >= 0.400 Inches "0.400" is a predetermined selection made by the NS and I suspect the decimal arithmetic is is being done correctly by ISY's arithmetic engine but using incorrect values supplied by the NS software. Test decimals - [ID 00D0][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $Test_terminate_value = 0.5 $Test_Ramp_var = 0 Repeat While $Test_Ramp_var < $Test_terminate_value $Test_Ramp_var += 0.001 Else - No Actions - (To add one, press 'Action')

10 seconds is probably a waste of bandwidth. Ecobee can only be polled every 3 minutes (180 seconds) or ecobee will cut you off. While I think 3 minutes is a little slow, I don't see faster than about every 30 tp 60 seconds, as necessary or useful. Thermostats are not that real time and temperatures and settings do not change that often anyway, to congest up any comm channel. With MSes and other devices that may be important. Even the 3 minutes update can live with some minor workarounds. I have a few to check updates are processed 100% and they always work, eventually.

? FreeBSD 12.1-RELEASE-p3 r359260 POLISY Welcome to Polisy! [admin@polisy ~]$ sysctl -a | grep temperature dev.cpu.3.temperature: 54.0C dev.cpu.2.temperature: 54.0C dev.cpu.1.temperature: 54.0C dev.cpu.0.temperature: 54.0C

FreeBSD 12.1-RELEASE-p3 r359260 POLISY Welcome to Polisy! [admin@polisy ~]$ uname -a FreeBSD polisy 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 r359260 POLISY amd64 [admin@polisy ~]$ FreeBSD polisy 12.1-RELEASE-p3 FreeBSD 12.1-RELEASE-p3 r359260 POLISY amd64 -bash: FreeBSD: command not found [admin@polisy ~]$

A 9v or 12v power supply, as @Brian H pointed out above may have more noise resistance and better filter capacitor life.

sysctl dev.cpu.0.temperature returns command not found on my polisy also

Router DHCP failure? Sometimes my router previously would not reconnect with some equipment when they all reboot at the same time. At times a reboot wouldn't do it...I had to power cycle it. My ISY usually reconnected better than some pieces of equipment, especially thermostats. It is better now with dozens of firmware upgrades now, and switching to ecobee thermostats.

All good logic but in many years and so many users out there, I don't remember hearing of a program running by an incorrect trigger. Many times we thought we had trapped a bug of this nature but it always turns out to be some sneaky trigger or other source of the erroneous event. Of course anything is possible. We have had some variable roundoff errors before. Myself, I would be trying to eliminate more possibilities, by disabling the each of the programs affecting the same variable and eliminating all but the one in question. Then polyglot could also be inflicting variable changes. I have complained about the rest interface having no data security before and anything can be changed in ISY erroneously by a runaway box containing your ISY credentials. There are no boundaries. Then possibly trying a factory reset and reload everything before opening a ticket. OTOH, Michel may like to see this in action and do some digging of his own, before the possibility of it just disappearing into the unknown. This will definitely be interesting to find out what is happening here.

Because there are at least 6 programs that affect that variable due to unforeseen triggers. Many times we save a value and then another program changes it and destroys the evidence. As an experiment try changing all those lines from "=" to "+=", then clear the variable to 0, and test. This should show a cumulative result from every program that triggered. None of the other programs will show True (Green) as they will all trigger False when another program becomes True. This also hides history. I have many of these "selector switch" type banks of programs in usage and they can fool you. Also, "selector switch" type program banks cannot ever have Else program lines.

"Daddy! Thanks for the new skipping rope!"