larryllix

Welcome to the forums! You would still use "Get". This is not an information direction but rather a Ethernet protocol specification where all the information is carried in the URL.

NodeLink has an option to reboot ISY manually or automatically upon NodeLInk update.

Well, the stack thing was a bit of a jest and probably not worth all the effort, but it is good to know about the strings in progress. I have used shifting list algorithms in ISY before with up to 10 variables. A small ISY program handled it satisfactorily.

Sounds like a variable state stack process starting here. UDI! Can we have stack type variables where we can push and pull values in/out of a stack type variable? We should only require a depth of up to 32?

Can you post examples? This could be real interesting to many here.

Here you go. Looks like UDI is starting to investigate. Further input may help.

Stusviews uses a spare SH Hub to program them.

No. Please join into Apostolakisl's current thread regarding this.

Doesn't it come with a 6' cable?

Separate scenes for each level you want to have are necessary to do this with scenes. This may get complicated but one step at a time.... Create all the scenes you want to use. Create a program for each scene and in the If sections put a STATE variable equal to a different value. Like this If ....$sVariable = 1 Then ....set DimScene On Else ....blank For all the rest of the scenes add one to the number so $sVariable = 2, 3 ,4 etc.. Always add an Off scene and a program with If ....$sVariable = 0 Then ....set sceneOff On You can drop these into a custom folder you create, so you don't have to ever see them again. Now to prove these are working go to your $sVariable you created in the State folder, and type some values into it to test them out..... Cool eh? Now you can write your programs easily testing what state the lights are in and do things based on that. If ....(Control Switch1 is switched On ....OR ....Control of Switch2 is switched On ....) AND ....$sVariable < 7 <----maximum lighting = full on Then ....$sVariable += 1 Dont forget this one If ....control switch is switched Off Then ....$sVariable = 0 I suggest you use numbers that are in some kind of order to make it easy to just increment the $sVariable when you want brighter or decrement it when you want dimmer. Or you could do it by expected order in time.

Another obscurely documented feature of the older style, and I imagine they kept it in the newer units, is the immediate send of dark detection. Tap the button seven times very quickly and it will send it's current light detection level without any delay of sensing. Well it still has a delay of about 5 seconds to detect instead of 3-5 minutes.

No. The bottom four truth table lines show '--' for the sensor input. The manual seems to explain that the relay responds differently for each sensor state. Since we are beating the manual to a pulp it would be good to show those combinations not working if they actually don't. Due to this mode being one of the primary design application features of the ioLinc, I believe the manual could be correct and your table doesn't show the combinations with the changing logic for each input. I only use one to indicate garage door position and do not control mine so I have no experience with the manual shown hookup and alternating logic based on sensor input.

I was using Android 4.4 and the Alexa app was missing many newer features without any mention of being half crippled. Android 5-7 shows many more features despite running the same app. Amazon sucks for this arritude.

That may explain some of it! I think I have experienced that, wondering if I should pull over and wait for them.

There doesn't seem to be logic shown for ISY operating the IOLic under the Momentary B condition. You have a note that ISY cannot operate the relay at all but IIRC some garage door users make it work from ISY. Being that it was designed to be used in that weird alternating lockout logic mode, was something missed in your testing for that mode? The combination isn't shown on the chart from ISY, but only from another linked controller.

Yes but your program will oscillate as you are affecting the same devices that you are sensing. Each time you turn a device on and the sensing sees it your program will restart then.. When it turns it off your program will restart Else.. What are you trying to accomplish? Get your thoughts and logic together and people can help you. At that stage you may have solved your own questions too. Better to detect the MS by using the if Control MS is Switched on. It can only run the Then section state from the logic. Status will trigger Then or Else. If ...Control of MS is Swtched On ...AND ...From X oclock ...To Y oclock (next day) then ...repeat 5 times ......Set scene to On .....set scene Off .....wait 2 seconds ...repeat 1 times ....leave lights where you want them left with v4 else ......blank

Yeah, some of the newer xenon bulbs have height adjustments in the car to compensate for suspension tilt etc. (Mazda is one) and the driver adjust those highly focused beams incorrectly. This shouldn't even be legal. My next door neighbour and I share rides occasionally to the theatre in the next town. He has this newer Mazda and is wondering why everybody is flashing their lights at him. After about a month of this he read the manual and tells me there is an adjustment for height on the dash. Geeesh!! These things are so focused you can see the distinct line of the light and dark on the forest trees, miles ahead.

LOL. I have been writing software since 1973 and python3 is a huge learning curve for me. The documentations is terrible and everybody offers guesses. LOL Try the parenthesis around each logical comparison first. I don't think my python3 behaves correctly and I have never spent the time to investigate but I have had lots of problems with compound logical comparisons not function the way I thought they should.

My son bought a massive house a few years old with illegal wiring in it. Trouble is there is nothing you can do about it. By the time you figure out the washing machine has a defective GFCI receptacle making it erratic, located behind a built in fridge in the kitchen, it's years down the road and no court is going to sit and listen to things, when you had an idiot rated home inspector go through it to your satisfaction, before laying down your Bitcoins. Half the walls would have to be ripped apart to fix all the white hot wires used in the upstairs wiring. Every month or so when I visit I find another gottcha' that should be cause for gun ownership in Canada. What can be done? Sell it to some other unsuspecting non-tech sucker, that may never know some receptacles have no power. Not nice, but either was the purchase. Buyer beware. In my next life I wouldn't touch a house with work that looks like a self-styled contractor. Who knows what evil lurks in the darkness of the walls?

As per KeviNH, I do a similar thing. While writing code, I do a print('XXXX routine:', param1, param2) on the first line of every function. If there is problems you can read the list/log and determine what got sent where. Once things are working reliably then comment out all the first line print(..... lines and leave them there for later debugging, if ever needed. This is not involving ISY or the pi, but rather, only your program code.

I am not familiar with python2 but some loose observations on the layout - no return on functions to separate main from function? I know there are lot of pythonisms that I avoid. - I found with my python3 multiple element boolean logic needed parenthesis to get order of operations correct. I was never sure if this was a bug in my compiler or I needed to study this more. It should work without them but I have had lots of trouble with them working bare.. if (a == b ) or (c != d):

As an afterthought I have had freak-out guests ask me if the MSs in the bedrooms were webcams.

I do this to with a separate program that dims all the SwitchLinc LEDs as well as the bedroom lamp and bathroom levels for "the pee run in the middle of the night". 100W equiv. bulbs ae pretty nasty in the middle of the night. If your proram adjusts the proper level for manual operation it looks fine. You may want a Wait between the scene level sets because they capture the Insteon protocol for a fair chunk of time that coud block other HA Tx items for a second or two. The scene levels are all kept in the Insteon devices.

I don't know how the ioLinc can tell the difference between ISY and any other Insteon module. This makes me wonder if UDI has created some workround to a protocol problem that causes different responses to be encountered.

I sold a house years ago full of X10. The market wasn't good then and it took a few years. I wanted to keep the X10 modules so after the offer was signed I took the wall switches out and repaced them with the smal rocket type mechanicals that matched the rest of the house. I worriedabout this for the next few months until the day of the closing inspection. When the people came to inspect, the first the women did was to go immediately to the switch in the front hallway and demand, "What happened to to the weird switch that was in here?" I told her some BS about being part of the security system that wasn't included, and she retorted, "Good! We thought we were going to have to get an electrician to replace them all." There has been many discussions about this over the years and my take is, it depends on the area and price of the house. Most people do not want HA in their home, or they would already have it. I feel it is like a badly done by the owner basement. I am just going to have to rip it out before I can do it properly. I have three very techie sons and none of them like HA. Every time they come to stay I find all three bedrooms with disconnected lamp modules (no WAF?), as the stupid things kept going off when they got in bed, or the light might have woke the baby up, despite only coming on at 11% after 8 PM. Typically home buyers don't like weird. If that is showing, then what have you done behind the walls? The trouble is, you will get no feedback on it, and the buyer just never comes back. Here the Realestate agents make sure you never meet the buyers. I found RealEstate agents will not even advertise the feature either, and that would be a good starter to attract a certain type that would even appreciate it. But times are a changin' too. I still have all the X10 modules in a junk box in my storage room.