MrBill

Specifically I never leave the admin console just open. Only if i'm working in it. Previously the only time I have ever had reboots that were caused by some mistake I made. Not the case today. I added a few more Insteon modules and added a program in the last week, but nothing major nor complex.. and the system has been running stable for 56 days, the point of my post is to attempt to figure out the root cause of the random reboot because if there is an issue I need to resolve it before being away for nearly two weeks in the near future. I have absolutely no idea why this would have happened, that's why I came here to seek help, sorry that I was unclear.

My normally stable ISY rebooted this morning, never had that happen before except when i screwed something up. I was in the yard, when i got the notification, the admin console wasn't open. I count uptime hours and that variable was at 1349 (or around 56 days). Checking the error log at the time of reboot I find: Version 5.0.13D Anyone have any idea what might have occurred? I'm getting ready to be gone for an extended period and need to deal with anything quickly. Thanks.

I see that now. I'm on mobile, its shows the information differently there, but does show that. I had scrolled all the way to the top of the page and clicked Universal Devices, which lead to me what I thought was a UDI storefront. But I do see the quantum networks info now. in any case it's all confusing, and actually misleading, when it comes to the the mobilinc tie-in.

I just stumbled on ISY’s on Amazon. It’s awesome that ISY’s are Prime items! Thought I would point out something that might be confusing to a shopper not as familiar with UDI as I am. The very first most important thing listed in the “Features & Details” section makes it sound like you don’t get warranty if you buy this item thru Amazon. While I completely understand that Universal-Devices is the seller, and the warranty and support would apply, this statement appears to say if you buy through Amazon it’s not one of the official distributors therefore you’re screwed so don’t buy via amazon. Also why is this the very first point listed, shouldn’t it be last? Or does it need to be included at all? Or is Amazon a rouge distributor, and this statement is valid... lol. Another issue with the Amazon listing is that it prominently features MobiLinc without mentioning that it’s a 3rd party paid app while also failing to mention other 3rd party paid apps such as eKeypad. I probably read too many details, but I’ve written and proofed too many documents and details like these jump out at me. Just thought I’d point it out.

My pool literally has a toilet float. It's located under a pop-off cover that from the top (on the pool deck) looks like a skimmer cover, but pop it open and literally the inside is a Fluidmaster 400AHG toilet float valve. It's water source/fail-safe is a dedicated zone on the sprinkler system, we just set the pool to water from 6-8 at night, if it's full the float valve is closed. The problem is: if this wasn't plumbed in during construction, it still involves breaking concrete. It would be possible to plumb in to existing plumbing, away from poolside, but would have to be made to only fill when the pump is NOT running since it uses the principle that under rest water seeks it's own level.

Just a question/comment related to the forum, not the portal maintenance that was completed Friday. <Rant mode> Why are there 8 old portal maintenance notices "pinned" to the top of this section of the forum? I could understand why ONE would be pinned PRIOR to the announced maintenance, but I would expect it to get unpinned when it's no longer relevant. It also appears that there has been a "rule change" and no new portal maintenance announcements are pinned now. So again I ask why are the old announcements still pinned? As is, I can't imagine why portal maintenance announcements from 4/10/2016, 10/9/2016, 10/16/2016, 2/19/2017, 3/19/2017, 4/14/2017, 7/16/2017, and 9/10/2017 would be considered a relevant announcement that should be seen immediately by anyone visiting this section or board in the forum. If all 8 of these were to be Unpinned it would leave 3 pinned posts that are relevant for pinning and in fact make those 3 posts easier to find/see (less noise). Actually the whole forum/community suffers from pinning "noise" or "pin pollution" at the top of each section or board. Someone with the power to unpin should review every section. "As is" users will simply develop the habit of downward scrolling beyond the pinned thread without even "seeing" the pinned topics anymore. This completely invalidates pinning. Disclosure and additional comment: I used to work for a social media provider that provides hosted forums to many of the larger corporations worldwide that offer a forum. As a community specialist the advice we gave customers was to 1) be careful not to over-pin 2) be certain to "unpin" when no longer relevant 3) make certain that the first unpinned thread was "above the fold" (see note below), that is, the first normal user thread should always be visible "above the fold". Today, #3 is harder to deal with because there are so many screen sizes and screen resolutions possible. But the general idea still holds true: Keep pinned threads at a minimum and get the user directly to the content. ("Above the Fold" is a term borrowed from the newspaper industry. In the newspaper industry, "above the fold" refers to the upper half of the front page that shows when displayed on the newsstand. It's the meat that must grab the reader and "sell" the paper. In the web hosting/web application world "above the fold" refers to the portion of any page that appears after the page is loaded WITHOUT scrolling. A general rule of thumb is that the user should become engaged with the content without scrolling on most browsers.) </Rant mode>

that link to a relay with base is actually 99 cents with free shipping for me, at the moment. Shipping from China tho.

I may have the letters mixed up... Haven't touched that level of technology in years. The chips did have a window and were erased with UV. My college project that almost made me famous (not!) used apple ][ (also 6502 based) and a Novation modem which had the ability to decode DTMF. It answered a landline, then an external speech synthesizer said "Hello Please enter the codes". The correct hard coded 4 digit PIN, followed by 2 digit device, followed single digit command would control a light via X10! That was remote control at it's finest! You could control a light from anywhere in the world! (any location that had a touchtone landline phone anyway--many landlines were still rotary dial.)

I don't understand then. The 2635 device literally controls the fireplace. It is cycled with the 2 programs based on temperature. To manually control that with the app makes no sense to me. The point of the KPL buttons being lit is so that there is indication the fireplace is "on" (has the capability of cycling), turning off the scene via the KPL stops the temperature based cycling.

My first home automation controller back in the 80's, the Hypertek HomeBrain, used a 6502 processor. It literally evaluated "everything" in every loop of its operating system. It had a whopping 2k of RAM (the OS was indeed 'firmware'-- to update it required burning a new PROM--Not even EEPROM... the PROM the could be erased and reused just a few times by peeling a sticker off the chip and "dosing" it under UV light.) BUT hey... this modern marvel of the 80's spoke and listened to X10 (then called BSR) on the power lines!! Memory was very limited, as I recall there were a whopping 32 (or 64 for an upgraded model) memory locations (variables) available for program use. (I was a dealer at the time--we installed a whopping 5 units in 4 years, I still had 2 new in boxes until about 4 years ago.) Compared to what I once knew about how the HomeBrain OS worked, I know literally nothing about the ISY's OS, but I can't imagine it not using Event based processing where a change in value results in queuing. Anything else is a waste of processing power.

Right Click My Programs and pick Find/Replace. Change the first dropdown to Variable.

I also have a ridiculous number of integer variables because I decided to have two per wireless transmitter to count total transmissions and battery days. That was a nerd curiosity thing since open/close sensors don't send low battery-- i did it for the recessed door sensors tho too... (17 transmitters x 2 variables each = 34)

Curiosity... I added 55 state variables the other day for CAO gadget tags... My list is now just over 100... I'm actually going to drop 22 of those because I'll never use some of the functions and why have the tags update something i'l never use... and another 11 could fall into that category too.. it was worth setting up that way to start to understand and experiment. I wonder if I need to be conservative with variable creation, or don't care because I'll never run out.

Actually I never knew the real inside temp of any freezer in the house before this point. "Settings" on 3 of the 4 freezers consist of an arbitrary number.. the forth does have a digital control degrees is actually set. The temp sensors are all mounted "almost" suspended in air..that is they have a velco strip mounting, and they are all attached on the ceiling away from air vent flow. The icing occurs on the INSIDE of bags or containers that contain air... factory or food saver sealed vacuum packages (most of it) doesn't show icing inside. On the other hand, ziplock a steak, squeeze as much air out as possible and freeze it...it will ice crystal inside the bag in no time at all. I've never understood why until now. I've always been under the perception this was the coldest best deep freeze in the house. I'm now learning it's the opposite, wide temp delta's over short time and now that i've maxed out the control, it "averages" closer to zero than the manufactures "suggested" setting of "4" to achieve 0 degree's F. You did make me think though... moving the sensor around some to see other results... I don't really care about burried in a pile off packages, or a bag of sand) i'm sure that will be more consistent... i do want to find out of the 14 degree surface temp change is real tho.

Actually that sounds like how I had this visualized as working at one point. Then I kinda stumbled into how I did it, It actually works great, and i think for the most part is better with the added advantage of instant on/off from the KPL's and the fact that the scene would still work manually if the ISY is gone or not working). [i could always work around the issue if I was home, however a design consideration is always how the system could/might fail if I was out of town and my wife tried to turn on the fire, for example. Because the scene remains intact under my method it would still work if programs didn't.. a better situation than my wife reporting...THERE WAS NO WAY IN HELL TO MAKE THE FIRE COME ON LAST NIGHT...] The only part that doesn't work is changing scene status via mobilinc (or the admin console but I don't care about that).... I'm surprised there is not a if STATUS "scene"... or CONTROL via system/isy...

This freezer shows more what I would expect to see.... a 5 degree temperature variation over a slightly wider (per cycle) time period. (All that IS hard to digest because the graphs auto-scale... it's very difficult to compare graph A and graph B because the scales (may) change based on data.) in the FIRST example... the temp delta is almost 14 degree's over a shorter 45 minute cycle.. it really explains why icing occurs if there is ANY air in the package. The freezer is in an unfinished basement room, no direct sunlight..It full of dense food, but nowhere near packed to the point that air circulation is any sort of issue. I actually have 7 tags in refrigerators and freezers, all behave about as I would expect... Except the name brand (but I think on the low end of the product line) freezer that had a rebate from the power company for purchasing it...lol My son has a freezer in his garage... not only is it not healthy for it to sit in heat it creates more heat in the space.. it also doesn't help that the only time the coils ever get cleaned is if I notice them and just do it... I

A friend of mines company can't ship to Canada because they don't have a French website and French documentation for the product... they used to ship to Canada... until they got ordered not to.... it's Canada's weird bilingual laws AND the Canadian Govt's insistence on enforcing those...

A better restatement of the problem: Start with everything off... module, scene, buttons, and $FLAG.LivingRmFireplace.cycle = 0 (a.k.a. the OFF state) We press either KPL button... the scene turns on, the module turns on (the flame lights immediately), because the of that, the program "Fireplace downstairs on" runs and set's $FLAG.LivingRmFireplace.cycle = 1. This enables the "Fireplace-Cycle off" and "Fireplace-Cycle on" because $FLAG.LivingRmFireplace.cycle = 1. Those programs cycle the module alone on/off based on the temp of the room. All the while the scene (and KPL buttons) stay ON... indicating the system is ON, even if the fire is currently in an off state due to temp.... When the scene is turned off via a KPL button, the scene returns to the off state, and $FLAG.LivingRmFireplace.cycle = 0 again, which stops the cycling. This all works perfectly, until the scene gets turned on or off via mobilinc. AS discovered above, it appears the this can be half solved: From the Off state of the system, STATUS is NOT off of a KPL button can be used to set $FLAG.LivingRmFireplace.cycle = 1, but the opposite does NOT work STATUS of KPL button is OFF can't seem to trigger the program to get $FLAG.LivingRmFireplace.cycle = 0 back to zero.

That won't work... it's being cycled via cycle off and cycle on programs (it's a responder rather than controller in the scene) what we are trying to trigger in the "Off" program that sets $FLAG.LivingRmFireplace.cycle = 0 -- which then prevents the cycle programs from running...

Actually I spoke too soon.... STATUS is NOT off ... correctly works for the KPL button turning on and set the cycle variable to 1 however STATUS is off doesn't work to detect off and set the cycle variable to 0 weird...

Well you solved this in one post, after I've been thinking about it for 24 hours.... The reply I was typing said "but there is a no status (or control) for a "scene" .... BUT....as I was typing that sentence I wondered to myself..."HMMM, is it possible to check the "status" of a KPL button in a program. In fact, thats the answer--the scene status can be determined by the status of KPL buttons that is a controller in the scene. (actually I have used "status" of the on/off module itself in another program that makes certain the ceiling fans are running.. but i hadn't considered the "status" of the KPL buttons) thanks!

Is there a limit to the number of variables that can be created? I know from the graphic on this page that number of "programs" max out at 1000. Is there a limit (practical limit or hard limit) for the number of variables that can be created?

Gas Fireplaces is the topic. I almost have this working the way I want it to, except one detail that I can't seem to work out. Prior to yesterday, it was a simple manually controlled scene. Each fireplace has one 2635-222 on/off module that powers a relay with a 120v coil. Each 2635-222 belongs to an scene, along with 2 KPL buttons, all 3 devices are controllers. Works great. Habits formed, my wife almost always uses the KPL buttons, I most always use the scene on the mobilinc dashboard or today screen to control. I've always had on my list to automate the fireplaces based on room temperature but had trouble finding the best temperature sensing device for the project. This forum introduced me to CAO wireless tags and I ordered and received this week. What a wonderful product!! (I will say that although this product doesn't have a cloud dependency in the sense that it requires portal etc to work, it does have a cloud dependency in that if the company ever ceases to exist the product will no longer work without its cloud. It's also scary that the tag manager has the ability to generate http calls on the local network based on what the cloud servers instruction......) ((Off-topic: I always knew I hated the way our deep freeze keeps food, I never realized the REASON. The CAO tag tells the WHOLE STORY, every hour the temp variation inside the freezer is almost 15 degrees!! Time to buy a better freezer!!)) Anyway enough back-story and side-story...back to the topic... fireplaces: As mentioned, with habits already formed I thought that I would build new control programs based on those. A few quick programs and everything works exactly as expected. EXCEPT one thing, controlling the scene from mobilinc. (Current programs included at the bottom of this post). If the scene is turned "on" from the KPL button, The scene is turned on, and the "cycle" variable gets set, when temp is reached ONLY the on/off module is cycled off and on based on temp, the scene (and button backlights) stay on. If the scene is turned "fast-on" from the KPL button, The scene is turned on, and the "cycle" variable doesn't get set. The fireplaces just stay on. If the scene is turned "off" or "fast-off" via the KPL, then the scene is off and the variable is reset so that it won't come back on as the temp falls. This all works great. The problem is it only all works great when controlled via the KPL buttons, if I pull Mobilinc out of my pocket and turn on the fireplace scene (my habit), the cycle variable never gets set because it is triggered via "control" of the KPL buttons. So what's the best way to control this logic via Mobilinc--with a single button on the mobilinc dashboard? (I know that I can create programs and migrate to TWO "buttons" on the mobilinc dashboard--one for on and one for off. I resist that tho because the scene status is not as apparent, and because it's two buttons. I'm looking for a solution with one dashboard button, like this: However there is no "control" (or "status" for that matter) that allows for capturing scene control via an IF statement of a program. Suggestions? Thanks... =================================================================================== Fireplace-Downstairs - [ID 007C][Parent 0001] Folder Conditions for 'Fireplace-Downstairs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Fireplace-cycle off - [ID 0078][Parent 007C] If $FLAG.DownstairsFireplace.cycle is 1 And $DownFireplace.temp >= $DownstairsFireplace.setpoint Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-cycle on - [ID 0079][Parent 007C] If $FLAG.DownstairsFireplace.cycle is 1 And $DownFireplace.temp < $DownstairsFireplace.setpoint Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-off - [ID 007B][Parent 007C] If Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched Off Or Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched Fast Off Or Control 'OUT Lower Fans - High / DN Fireplace' is switched Off Or Control 'OUT Lower Fans - High / DN Fireplace' is switched Fast Off Then $FLAG.LivingRmFireplace.cycle = 0 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-on - [ID 007A][Parent 007C] If Control 'Living Room Fan Lights+ / Fireplace' is switched On Or Control 'DN Back Door Recessed+# / Fireplace Downstairs' is switched On Then $FLAG.DownstairsFireplace.cycle = 1 Else - No Actions - (To add one, press 'Action')

Whenever I read threads like this one, I always want to ask "What Changed". The OP implies everything worked fine "before" but then "The last few days the wait time is screwing up the last action." Why did it work before and suddenly stop? Was a program changed? Did the batteries in the motion get changed? When a working system suddenly stops working, the first question always has to be "what changed?"

2 amp at 5 volts = 10VA 2 amps at 12 volts = 24VA 2 amps at 30 volts = 60VA huge differences there...