MarkJames

Here's the error log - The problem seems to start around 8:48 on July 25th so I've removed the events prior to about 8am so you don't have to wade through it. I don't see anything whacky - do you? I set up a system so that I don't flood the ISY with too many requests. Prior to turning a lot of devices on or off I set a flag called 'oktogo'. When oktogo is true no other programs are making changes. The program sets oktogo to false then starts turning lights on or off with a 1 second delay between each request. Once it's done it sets oktogo back to true and exits - thus allowing other programs to do their thing. When oktogo is false the program waits 2 seconds then re-executes itself to try again. It looks like this Daytime Energy Saver Actions - [ID 00DB][Parent 0018] If $OkToGo is $TRUE Then $OkToGo = $FALSE Set Scene 'Back yard / Back Yard Lights - All' Off Wait 1 second Set Scene 'Games Room / Games Room - All Lights' Off Wait 1 second Set Scene 'Garage/Shop / Garage - All Lights Off' Off Wait 1 second Set Scene 'Kids Floor / Kids Floor - All' Off Wait 1 second Set Scene 'Living Room / Living Room - All Lights' Fast Off Wait 1 second Set Scene 'Garden / Garden Lights - Back yard' Fast Off Wait 1 second Set Scene 'Garden / Guest Lights' Fast Off Wait 1 second Run Program 'Laundry Lights off' (If) Wait 2 seconds Run Program 'Kitchen Lights off' (If) Wait 2 seconds Run Program 'Ensuite Lights off' (If) Wait 2 seconds Run Program 'Eblanket naz off' (If) Wait 1 second Run Program 'Eblanket mark off' (If) Wait 1 second Run Program 'Main floor lights off' (If) Wait 2 seconds Run Program 'Sun room Lights off' (If) Wait 1 hour Run Program 'Blanket Mark Off' (If) Wait 1 second $OkToGo = $TRUE Run Program 'Daytime Energy Saver' (If) Else Wait 2 seconds Run Program 'Daytime Energy Saver Actions' (If) mark https://dl.dropboxusercontent.com/u/18230046/errors.xlsx

Thanks Michel, It's odd that whatever generated that series of errors didn't repeat neither before nor since. Everything is hunky dunky now without having changed anything. I'll clear my error log and start monitoring it. The sockets opening and closing I'm going to chalk up to a lot of beta testing going on at present. I'll often rapidly open a half dozen tabs that each open a socket then close them again. Thanks for going through that. I'll clear my log and start paying attention to it.l mark

Sorry Michel. Here's mine - I saved it just after the problem. There are lots of trivial errors related to messing with the REST interface at first - I just included the whole log even though the problem is in the last 100 or so entries. The 'system busy' non responsive issue started just about July 25th. It seems to be reflected in a series of 'Queue full' errrors. Here's the log https://dl.dropboxusercontent.com/u/18230046/ISY%20Error%20Log.v4.4.6__Fri%202016.07.29%2009.29.10%20AM.txt

Any experience with the Ubiquiti line of these devices? MFI? They seem to have a lot of sensors available - and the intent of the device seems more for tracking than just remote reboot - but the pricepoint is lower and the Ubiquiti products that I have installed have been of excellent quality - perhaps not 'commercial' but definitely 'prosumer' mark

I do a similar thing - a state variable that starts as false and after setting things up the way I want I switch it to true. I've also repurposed a motion detector recently to act as an 'is it light out' detector instead. I just put one facing out the window. When it's light enough to trip the motion detector 'dark' sensor I set a dark=false flag. Conversely at night when the detector decides it's dark enough to need lights I wait half an hour (they trip a bit early I find) and then set the dark=true flag. I never found the sunrise/sunset thing to work very well at my latitude. mark

Oh ok... They weren't doing that when I set up mine. I had to send fake credentials to my 'account manager' who then set me up with an account. I bought mine from Smarthome and they had all the software available there to download. Soon after they pulled it off the Smarthome site and I had to approach Elk directly to get in. That's when the fun started. I guess they had so many unhappy end users that they changed their policy. Good thing, too. Now if only Universal Remote would do the same - I LOVE their products but it's brutal getting the software for them. mark

I'm glad to hear they're supporting end users again. I bought my system about 15 years ago and all the software, updates, etc. either came with it or could be downloaded. Shortly after they put all the software and updates behind a professional log-in page. mark

Thanks for that, Kevin. I hadn't noticed the 'Init to' variable assignment before. I can already think of quite a number of uses for it. That will make rebooting less problematic for sure. My experience has been the same as yours - I very, very seldom have to reboot my ISY. It's the Windows XP SP3 of devices - it just doesn't crash. mark

Sadly not on Amazon.ca (well - there IS one but they want $70 to ship it). The only drawback to adding the ISY is that your variables will all reset to their initial values. I depend on a lot of variables so that wouldn't work for me. If I reboot I'd possibly have to go back and change a few things to after the boot. mark

I'll look more closely at the heartbeat event. I see it come in via the websocket but I haven't parsed it to see its significance. I was looking to see if an IP was associated with it so that I could tell which PC the socket was connected to. There are some 14 pcs, laptops, ipads and android tablets around the house - I was hoping to see which machine(s) were connected. mark

Thanks Scott, I'll have a look at that as well. It's tough to get some of these items up here in the Great White North. While the cost is the same here as there the shipping to get stuff here is outrageous. While you guys get 'free shipping to the contiguous 48' the same item will cost me over $120 by the time UPS finishes raping me. That can be pretty painful on an item that costs $100 or so. My son recently bought a Boosted Board to the tune of $1500 out of Cali. The shipping is free anywhere in the US. It was $140USD to get it shipped to Canada and then Fedex charged another $80 in brokerage fees plus GST and PST. Total FedEx fees (though much was tax) was in excess of $400! mark

That's what I was just looking at. One of the program If conditions is 'is responding' I've never used it before. LeeG would know what that's all about. Maybe if he sees this he'll chime in. mark

That would certainly work - but too many parts.

I'd like that just to know if a circuit has blown. My sprinkler pump is 1.5HP single phase that will run in either 110V or 220V configurations. I've got it wired as 110 (more convenient) and I've hooked it to a 20A breaker. The tables say this should be adequate but it still blows the breaker from time to time. If I don't catch it the sprinkler merrily ticks along opening and closing zones but with no pump running no water moves. It'd be great to have a module that returns a heartbeat every n seconds and when no heartbeat is returned a message is generated. I wonder if that couldn't be accomplished simply using a program that queries the device on a repeat every n seconds and sends a notification if no response is received.... Of course your idea, Larry, would be more complicated and require a unit that could measure current flow. No flow = message sent. It's a pretty simple idea, really - it's been available from ChannelVision for their whole home audio/video systems for years. They use it with their GateIRKeeper so that when you turn your system ON it can detect which devices ARE on for those devices that don't have discrete on and off. mark

I wish I would have seen it before I bought this http://www.netreset.com/ I have 3 Axis video encoders that stop encoding when they feel the urge. I plugged them into the Netreset and it reboots them every day. It's done the job but it's kinda using a bulldozer to do the job of a garden tractor. Now all I have to do is figure out how to get my laptop to stop singing all the time. I guess if I didn't like singing I shouldn't have bought Adele.

So after having had my ISY hang on me while out of the country with nobody at home to reboot it I started looking at different options for being able to reboot from remote should the need arise. I tossed around the notion of an Arduino connected via WiFi or a Raspberry Pi using the GPIO pins. Both of these ideas have merit but I stumbled upon a pretty cool looking toy and wonder if anybody has any experience with it. This is it here http://www.digital-loggers.com/lpcfaqs.html . It's an 8 port 15A rated device that looks like a power bar but you can power on/off/cycle each of the outlets via TCP. So long as my router doesn't crap out and destroy the port forward I would be able to reboot my ISY, cameras, IP encoders, or any of the other devices that occasionally act up. Even PC's that can be set to reboot after power recovery would theoretically work Anybody use one of these? I've ordered one to try out but it's on backorder at the moment. Looks like they make both a single-phase and also a 3-phase unit for those of you lucky enough to have 3 phase power. mark

The only caveat with Elk is that they no longer provide all their software and documentation to end users. Rather, they've put it behind a subscriber only 'installer wall'. Same with Univeral Remote Control sadly (they make the bar none best remote controls on the planet) If you do go the Elk route and need anything then feel free to pm me - I have an installer account and will dropbox you anything you may need. I've just finished integrating my Elk with ISY via my own webpage and websockets. I couldn't be happier with my Elk investment. The peripherals and add-ons are second to none and work flawlessly. mark

Thanks Michael and Michel (lol - being a Canadian that's funny to me - you have the same name but one of you gets an 'eh?') Michel, two questions... how long is the heartbeat period before the socket expires? Is there an ip address associated with the socket so as to know what device is subscribed? I'll check my error log tonight when I get back and see what the problem was. mark

k.. so I've searched the documentation but can't find what some of this stuff means. I see there are 10 entries and 10 is the number of websockets allowed so I imagine there's one entry per available socket. first... isExpired. Is this time based? or inactivity based? What causes a socket to expire? isPortal I suspect indicates if this socket is used for ISY Portal. Is this significant to anything other than internally for ISY? sid appears to be a socket ID where -1 indicates unused? Otherwise the ID's increment as sockets are opened sock is some other socket ID? isReusingSocket? Is this where one browser shares a socket between multiple tabs but with different socket IDs? Sorry for all the questions - I can't find any docs for this mark

I didn' realize I could see that... It shows this <Subscriptions> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="no" isPortal="no" sid="48" sock="28" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="no" isPortal="no" sid="51" sock="25" isReusingSocket="yes" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> <Sub isExpired="yes" isPortal="no" sid="-1" sock="-1" isReusingSocket="no" isConnecting="no"/> </Subscriptions> and actually some of my rest calls are working now too. I'm going to check if the socket is connecting. [edit] no websocket connection and still can't connect to admin console (system busy). I'm connecting ssh to home

First off - should I ask websocket questions in this forum or in the developer forum? If this is the wrong place then please feel free to move this post and accept my apologies. So I've been working quite a bit with websockets lately - purely for my own personal webpage. Basically whenever I open a new tab or home page in Chrome my personal page loads. It's full of my favorite links as well as controls for lighting, security, cameras, etc. As soon as the page loads a socket is opened and a visual representation of all the 108 or so devices gets created. Everything was great but as of this moment I've been away from home for a few days and i cannot access my ISY. All I get is a 'system busy' message from the admin console. It's running - I know that - as scheduled events are taking place - but I cannot access the admin console nor can I get the status of devices through the socket. The REST interface is not responding either. It's just gone non-responsive and needs to be rebooted which I'll have to do when I get home tomorrow. I have no way of rebooting it but I suspect that I've oversubscribed the websocket system or perhaps I have too many browser tabs open with a subscription. Is this possible? If oversubscribing it *is* a thing then what would be an appropriate workaround? Only opening the socket upon request? Closing it when the tab loses focus? Timing it out? All these would work but will they release the resources that the ISY commits to the socket when I close them ie when I issue websocket.close() will this be enough for ISY or is there a *preferred* way to release the socket. Clearly opening a socket everytime the page loads is NOT going to be a good longterm strategy. Apparently closing a tab does NOT close the socket connection - (read this on stackoverflowcom). I find that odd because the socket instance no longer exists so it can't be addressed. Is there a server side - ie ISY side - way to close a socket that's left open or to close them when there are multiple sockets from the same IP? Thanks in advance, mark

I got one of those about 10 years ago and for the most part like it a lot. The only issue I've had is positioning it so that it does what it's supposed to.... I haven't tried mounting it on a side wall - just on the ceiling like they show in the promotional stuff. It seems most useful when the LED hits the dashboard or someplace easily seen even when well lit. Thing is that the garage door is fully up when the car backs in so it blocks all the obvious spots on the ceiling where it would mount - the door is in the way! And if you go too far back on the ceiling to mount it then the laser pointer just hits the roof of the car instead. mark

My car has one of those distance measuring do-jobbies on the back. I generally back up till it says I have 18" behind the car. That time I'd forgotten that my golf clubs were on the floor so it measured 18" off the golf clubs - which put the car too far forward. That'll learn me to rely on tech. that'd be very cool - a la mission impossible. Likely prohibitively expensive. Why does the string need to glow in the dark? You got a disco running in there? mark

As an aside for the OP regarding connecting to Elk... I hooked mine up yesterday and it's working great. I connected it to one of the Elk outputs and trigger it programmatically. It was a real 'rtfm' moment for me, though. I have boxes of electronics around so I grabbed a solid state relay (3-32VDC in) and hooked it to the Elk only to have it not work. So I switched to an automotive 12V relay which also didn't work. Then I went to an HVAC relay which also didn't work. Of course I had to crimp on connectors then cut them off to tin ends and then re crimp new connectors in between each of these steps so I wasted the better part of an hour and a half on this before finally pulling out the Elk manual. Turns out the Elk outputs are meant to drive a relay that draws no more than 50ma. So basically a small reed relay. duh. I have a drawer full of those (didn't use them at first because they're all small and require soldering). Put one of those in place and shazam! works like a champ. The moral - read the f**king manual.

There's a point on every one of my vehicles that can overhang the door beam without tripping it. The part that caused my particular problem was the license plate bracket - which got destroyed by the door in the incident (along with the door top which the garage door company want $900 to replace) Seeing what the door could do to itself and to a couple of 1/4" steel bolts gave me a new respect for just how dangerous a garage door can actually be. It could easily kill/main someone. We don't have small children around us (rural area) so I don't stress over it much - but Teken's advice about checking reversing pressure and beam setting is definitely sound. mark