-
Posts
14922 -
Joined
-
Last visited
Everything posted by larryllix
-
Wait does not cause re-evaluation of the If logic. Wait allows the ISY PLC processing to run other tasks (gives up it's time slice control for the Wait time) which may include evaluating the If in the same program if a trigger element changes. It may only be ISY sending out an Insteon command.
-
How about any boxes using the Rest interface or Kodi app?
-
Either it is licenced or, if it ever becomes anything, it will disappear or else pay the $2 Million law suit, and then disappear.
-
Yes. Having a common variable for inside darkness has it's advantages, including adjusting sunset for a darker or lighter house construction, tree leaves in the summer vs winter, etc,,
-
Yes, post program so we can view it. Use "copy to clipboard and paste here. You cannot check an MS battery. You wait patiently for a one time LowBatt signal and it is transient. I send notification and then record all my LowBatts in a variable list to keep a record of which ones reported in.
-
They have knowingly put out so much crap for so long now and with the HA boom going on without them? If I was SmartyHome I would be shaking in my boots and starting to sell other brands and lines of equipment. Oh wait! They already have.... They have one supporting control intelligence company that wants to support them and what do they do? Not allow them to promote their products by refusing them any rights to their technology but get in bed with other companies to support a cloud based logic home controller. I guess in this day and age of CPU's in every toaster and walwart they don't want another one in a HA controller! The extra $0.30 cost would cut into their intelligence. (sarc) When will they learn Mandarin so they can understand what is being designed for them?
-
I use an All Off program at 4:00 AM every night but not in a scene. I switch every light off one at a time with a few seconds delay between each just to help any Insteon traffic jams I would cause and be more sure they all work. Also outside observers would see a progression for a more human action look if everything was on for some reason. I also do have an ALL Lights and Front Doorbell scene for intruder repulsion.
-
I think I have it. It's late and I am having trouble focusing so nothing guaranteed, Cody Bath Manual Switch - [iD 0023][Parent 002A] If Control 'Shower Bath - Room' is switched On Or Control 'Shower Bath - Room' is switched Fast On <--- I would save Fast On for other functions <---no condition needed as far as I can tell Then Set Scene 'Shower Bath Motion Light' Fast On <---- just set the light on without the scene. Disable Cody Bath Motion Disable Program Cody Level Ramp Rate In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 100% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 0.1 Sec (Ramp Rate) Wait 2 hours Run Cody Bath Switched Off (Then path) <---- use other program to restore everything Cody Bath Switched Off - [ID 0056][Parent 002A] If Control 'Shower Bath - Room' is switched Off Or Control 'Shower Bath - Room' is switched Fast Off <----could be used for other functions Then Set 'Shower Bath - Room' Off Run Program Cody Level Ramp Rate (If) Wait 1 second Enable Program Cody Level ramp Rate (If) Enable Program 'Cody Bath Motion' Else - No Actions - (To add one, press 'Action')
-
No "delete direct link". Delete the line, there is already a direct link. sorry for the shorthand.
-
Motion Program Cody Bath Motion - [iD 0049][Parent 002A] If Control 'Cody Bath-Sensor' is switched On Then Set Scene 'Shower Bath Motion Light' On <---Delete = direct link between devices Wait 1 minute Set Scene 'Shower Bath Motion Light' Off Else - No Actions - (To add one, press 'Action') --------------------------- Night Ramp Program <---looks good Cody Bath Ramp Rate - [iD 0044][Parent 002A] If From 10:00:00PM To Sunrise (next day) Then In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 30% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 4.5 Sec (Ramp Rate) In Scene 'Shower Bath - Room' Set 'Shower Bath - Room' 30% (On Level) <----Delete, wrong scene In Scene 'Shower Bath - Room' Set 'Shower Bath - Room' 4.5 Sec (Ramp Rate) <----delete, wrong scene Else In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 100% (On Level) In Scene 'Cody Bath-Sensor' Set 'Shower Bath - Room' 0.1 Sec (Ramp Rate) -------------------------------------------------- The rest of this confuses me. I started to renovate it but it got too confusing with this small editing page. It doesn't look anything like my original and I do not understand what you are trying to do with different logic. You have attempted to split the one program into two also. That can work but isn't necessary. It does make the compound If conditions easier to understand though. Here is my original program that does both. Some disables need to be done and calls to the resstting of the levels program needs to be done and have been attempted to shortcut. I suggest you copy Then and Else into your individual programs changing devices and program names, to suit, as you copy over each line. MBR Lamp.manual - [iD 0038][Parent 0017] If 'Master Bedroom / MBR KeyPad.A' is switched On And 'Master Bedroom / MBR KeyPad.A' is not switched Off Then Set 'Master Bedroom / MBR Wall Lamp' Fast On Disable Program 'MBR Lamp.auto' Disable Program 'MBR Lamp Level.adjust' In Scene 'Master Bedroom / Motion.MBR' Set 'Master Bedroom / MBR Wall Lamp' 100% (On Level) Wait 2 hours Run Program 'MBR Lamp.manual' (Else Path) Else Set 'Master Bedroom / MBR Wall Lamp' Off Run Program 'MBR Lamp Level.adjust' (If) Wait 1 second Enable Program 'MBR Lamp Level.adjust' Enable Program 'MBR Lamp.auto' Lamp will get direct hit by MS so adjusted scene level so it can't be noticed.
-
It would seem you are thinking of X10 signals where All Lights On would only affect units on that housecode. In Insteon this would turn everything On/Off, including furnace fans, heaters and bathroom exhaust fans etc,,, The toggle mode is only preference but I set mine up to non-toggle. Each button sends a distinct On command only. In toggle mode each button alternately sends out an On and then an Off command. So a receiving program might look something like this. If control KPL.botton.A is switched 'On' Then set Light A off set scene GroupOfLights off Else -- making sense?
-
Where are you trying to send an All Off command from? This is a usually avoided command that most of us never use. If you have the six button KPL then the two larger buttons at the top and bottom control the attached load. The rest only send Insteon signals. There is no All Off/On on a KPL.
-
As per Stu's post above you have to select the scene and scroll the other way to find the controller device. It's not really a scene name but rather an initiating device name. Here is some examples. Note the different icon symbols and the name xxxx.motion.MBR which is my name for a motion sensor, not the scene name. Note the layout may be slightly different as I am using v5.0.2 beta.
-
IIRC the option was only at boot up time and you are right...it only suffixes values. A while back I wrote a series of programs to interrogate a thermostat and put the result in a variable. This was before v5 and there was no capabilities to do that. It takes a program, that calls one after the other in a daisychain fashion, for each value you could expect. The starting program triggered from any temp change for the stat and also has several times each day to trigger, just in case. The series ran a linear approximation until the logic switched and then you had your temperature in the variable. Of course this would all be replaced once the F/C problem gets fixed from the manufacturer.
-
Have a read at this. IIRC this should cover all the bases for you. http://forum.universal-devices.com/topic/17495-how-to-use-a-ms-with-lights/
-
Have you examined the data stream in the events log to see what the actual bitcounts look like? perhaps UDI needs to change the interface t match the ISY settings. I would write software to change the value to Celsius in ISY. If you can trigger programs on temperature reports from it you can extract the temperature reported to calculate from. This would be temporary until complaints get some action from the manufacturer about their defect. Other hardware needs to do it's own thing with the data stream values or have ISY send out your calculated results..
-
I have never seen a thermostat that can't display Celsius temperatures and all mine display C in the ISY admin console. Is your ISY set to use C or F?
-
This isn't really the limitation with ISY but rather the Insteon system itself. HA systems were based on turning lights and appliances on and off only. Analogue is really something new. ISY has provided for this expansion quite well with it's REST interface and now Node interface that are gateways to the rest of the world and could leave Insteon in the dust. IMHO Insteon is still the gold standard of non-hardwired HA though but SmartHome is just fumbling too badly for the speed of popular wants. They probably just don't understand the Chinese documents for the latest developments presented to them I have a WC8 PLC board stuffing windspeed, gust speed, inside temp. outside temp, hi and low temps for the day, a RPi stuffing every aspect of my Venstar T7900 thermostat into my ISY and use most of the parameters for logical HA responses. These are all analogue inputs. Currently ISY reports my cold cellar ventilation, HRV, and HVAC heating times each day via text message for monitoring purposes. ISY is not limited by Insteon, just our imaginations.
-
Metric or Foreignheat make no difference to ISY or io_guy's NodeLink or VenLink. Temperatures are just numbers to be interpreted by the end user in whatever form YOU choose. Depending on C or F selected in ISY it only assigns the correct suffix to the number in notifications etc.. In the serious world of data acquisition values are not sent in engineering units but in bit counts to take advantage of the best resolution available with the hardware in use. IOW if you have a 16 bit channel you don't send attempt to send the result of a 10 bit A/D conversion down the pipe. You attempt to send the best resolution you can to take advantage of the channel resolution. If this means a transducer with a range of 10 degrees to 20 degrees is represented by a 16 bit A/D converter then 0 counts = 10C and 65535 = 20C. The end user has to scale the bits and add the zero offset to achieve engineering units for the human to look at. You wouldn't have equipment massage and manipulate a raw data value and then give it to another piece of equipment to rescale it down or up. Resolution accuracy can be lost each time. This become evident in many Insteon analogue channels. The 2441ZTH converts it's temperature measurements to C or F and then ships them out Insteon in a 1 bit - 0.5 degrees format. Any further resolution available from the A/D temperature measurement is lost regardless of what the end user wanted. Compensation scales, calibrations and/or end user scaling/offsets could have been done to increase accuracy but it's too late once the truncation has happened. Having said that the Insteon analogue channels can be very limited in bits.
-
Stuffing the result in a variable can trigger any program to run and cause anything to happen that ISY can perform. Do you understand the difference between Integer and State variables? I have no Zwave modules but I would be sure their values would be usable for variable substitutions in V5. If not yet they will be soon and that means you can set your variables via Rest calls and work from the values from the resultant triggers in ISY. Are you familiar with the Network Resources and how they work as well as variable substitution? Maybe there is some waiting time yet for Zwave modules but it will come. Variable substitution is new in network resources but has existed in notifications for some time now. If you are programming familiar then it shouldn't be too hard to create a series of Zane input module programs to get values into a variable and massage as needed. Later when advancements are made just swap out your modular code for simple methods available.
-
A program should be easy You would need a scratchpad variable and a finished product variable. Set them both to one decimal point of precision (v5) If the temperature_reported < 999 (must be enabled to trigger on every change) Then scratchpad = temperature_reported scratchpad -= 32 scratchpad *= 5 (for v5 with 0.1 precision) scratchpad */ 50 (if using v4 for temp x 10) scratchpad /= 9 finished = scratchpad Else -- The Insteon 2441ZTH reports in C just fine. There is an option in ISY to report in C at bootup time. Can't remember how to get access to it though.
-
If you have reformatted the SD card I see no way out except to contact UDI support.
-
Just to add more fuel to the evidence. Case in point, I have ten active Insteon MS units and have never experienced an All off/on in two years now. I have experienced massive retries from MS units that get no response and would venture to say, without testing to back this up, that multiple retries don't happen once the MS units are directly linked to a Switch link or other Insteon device that acknowledges the command send out, and no ISY intervention is involved. My suspicions are that this "signal clash" is a problem with the serial port driver in ISY not handling Xon/Xoff or other control characters in the data stream from the PLM. As I understand it, the serial port is a proper three-wire EIA-232 signal protocol and signals inside of other data packets can be hard to handle without problems. Buffer overrun is usually the result and erroneous data can be sent if not handled correctly at either end.
-
Q? Do you have Insteon motion detectors?
-
With my X10 system I always used a time of about 4 minutes in the MS units. My programs would be set to cut this time short to 30 seconds, 1 minutes, or 2 minutes, always faster, The X10 Off in the MS (not avoidable) would act as a backup signal to insure the device turned off. The programs just shortened the time based on logic conditions. Of course, and I still do it with Insteon as well, I have a 4:00 am program that shuts everything off for the just-in-case scenario.