apostolakisl

I had this same problem a few years ago. When you link two accounts to Google Home it does not try to stop you. And it still works kind of sort of making it even more unclear what is going on. So if you want to share your link to ISY with your wife or whomever, you need to log them into your google account, not link their google account. Also, I just finished unlinking and relinking my home account. For reasons unkown it gave me permissions errors.

While you can't turn a scene on directly to a level, you can brighten or dim a scene. Not 100% sure if Alexa accepts that command (ie "dim scene xyz") but you certainly can do it from a scene controller such as a switchlinc or ISY. The problem of course is that all the devices in a scene get their own custom brightness level when the scene is turned on. I suppose if you had 2 devices in a scene with 1 device set to be 50% on and the other set to be 60% when you turn the scene "on", then you might think that turning the scene "on" to 50% would mean on light at 25% and the other at 30%. But, this gets a bit ambiguous. You might consider creating 2 or more scenes at various dimmed levels. Then name the scenes something like "bedroom lamps 50 percent" and "bedroom lamps". While it would seem as though saying "Bedroom lamps 50 percent" is telling the scene "Bedroom lamps" to only ramp up to 50%, it is actually a completely different scene.

So when you set up a temp node, the number you assign it is meaningless.

Correct me if i am wrong. But it would seem that the temp virtual node has no affiliation with any particular variable. Set the temp at the node, the variable stays the same. Set the variable value, the node stays the same. It appears the only connection between a variable and temp node is if you use a program to transfer the value from one to the other (either direction). But this is not restricted to the "assigned" variable you use when configuring the node in polyglot.

While hours works for me on this one application, unless there is a way to let the user configure the label in polyglot, I think you would be better off with no label at all. Then people can make it whatever they want and label the node itself to clue in the user. I would leave the temp one as is, just add another one that is pretty much the same as the temp one but with no label (or user defined label).

Thanks for the update. The 1 decimal place works great. Any chance you can make a generic one? Or is it possible to be able to create your own label as part of the configuration? In my case, I'm looking for the label to be "hours". I could use it as is, but it would just be confusing when people go to set how many hours for something to run and the label says "Fahrenheit". It would be better for there to be no label at all rather than a label that incorrectly describes the value.

What nodes do you have that have free form? I'm pretty sure every node I have is a drop down selection.

I was also wondering if this is possible. But every node that currently exists in ISY has only a set array of values, nothing is "fill in the blank". I suspect that "fill in the blank" is not possible for a node value.

I would just call it "numeric value" or something totally generic. Certainly you could just use the "dimmer" node and just know that despite the label, you are not dimming a light. It would be there as a generic node that can track or set anything that can be controlled or tracked with a number. Humidity, RPM's, minutes, days, seconds, hours to set something to stay on, or off, or track how long it has been on/off, etc. The first thing I would use it for is to control the hvac at my church. Currently I have a variable that I set for the number of hours I want it to turn on the system. Before an event in the church that you know will last, for example, 2.5 hours, you set the variable to 2.5 and it counts down to off and shuts down the system. It would be much easier to train the ISY novices at the church to use a node rather than digging into variables and setting it there. Perhaps doing decimals doesn't work, but I could use minutes instead. Trouble is currently limited to 100 minutes using the dim level node or using hours I would be stuck with whole numbers. Below is the program I use currently, but like I said I have to set it in the variable section. It allows for setting down to 2 decimal places. The idea is to set it in 15 minute increments, like 3.25 for 3 hours 15 minutes. Manual Time to Unit Shut Down - [ID 003E][Parent 0049] If $s.Manual.Hours.To.Shutdown > 0 Then $s.Units.Running = 3 Wait 3 minutes $s.Manual.Hours.To.Shutdown -= 0.05 Else $s.Units.Running = 6 $s.Units.Running = 0 $s.Manual.Hours.To.Shutdown = 0

OK, got it. Thanks for creating it. Just my luck I decided to test it using temp. You might have one that is allows you to put in a wider range of numbers and transfer that over to a variable. Also, not have it labeled "dimmer". Maybe include negative numbers. I assume you are limited to the number of choices that can fill in the field by ISY?

Do I have something set wrong here or do I just not understand what this is supposed to do? I assumed that setting the value from the main node page of ISY would then propagate through and set the variable. But the variable does not change. Do I need to write programs both directions? If the variable changes then it changes the node, and vice-versa? If so, I don't understand why the node server needs my ISY ip/user/pass. I've tried 192.168.1.9 192.168.1.9:80 192.168.1.9:443 192.168.001.009:80

@Brian_A Windows 7 is no longer supported by my understanding. I believe that as of 1/2020 they discontinued even critical security patches. So I would suggest moving to Win10. Perhaps if this PC never touches the internet, you will be OK. And I think you already figured out to use the ISY launcher app. This is totally independent of any browser. Also, the launcher gets messed up with java updates. So, when updating Java, you need to delete the shortcut, clear the java cache, and run the start.jnlp installer again to create a new and working launcher along with a new shortcut. If you don't delete the shortcut, you will get a working version of the launcher, but it won't install the correct shortcut on your desktop. It is said that you should clear the java cache with updates to ISY firmware, however, I have never done so and have never had a problem. Only Java updates, which seem to crash it every time. Although, if you are running Win7, it is likely that you will never be prompted to update Java as Java updates seem to directly follow windows updates, which there will be none of for Win7.

seems like you could set up some mirrors at various angles and reflect the beam back and forth up the track. Challenge would be keeping them from getting out of whack.

we do have a tahoe and on occasion it isn't parked in far enough, but when parked as it is normally, the door opens without hitting the garage door. But yeah, that is a risk. Though I would expect damage from the GD to be quite a bit shy of destroying the back door. Paint scratches, maybe break the windshield wiper, but not structural damage. It should just push the door into a more shut position.

I close mine remotely if I am going to bed and forgot it open. Not a lot of toddlers in my driveway at midnight. Actually, not a lot of toddlers in my driveway ever. At least not since my son stopped being a toddler 5 years ago. I live on 7 acres and there just aren't any kids wondering around anywhere at any time on my street. I see more bobcats on my property than toddlers. And if you know anything about bobcats, you'll understand what I mean. I have trapped birds in the garage, however.

no problem. And regarding cameras, the problem with portals is the data has to go through the portal server. So there aren't really any low costs way to do this since the server needs tons of bandwidth for video. Consider getting yourself a ubiquiti usg (router) which has a very simple VPN configuration. Then you can vpn into your home network to view your cameras. VPN doesn't work for ISY since many of the devices you want to connect will not be able to establish a vpn connection first (like Amazon). Though if the only thing you wanted to do was connect a phone app to ISY, you could set your phone up with VPN, then connect your phone to vpn first followed by opening your phone app. But this is just kind of cumbersome.

OK, so it is listed on ISY as "beep", but the sound the switch actually makes is much more closely described as "chirp". It is just one of the many options for a switch, such as on/off/fast on/fast off/beep/etc. available in a program. In other words, just write a program and instead of commanding a light to turn on, you command it to beep. And if you want "chirp chirp chirp", you put three lines of code back to back. Not sure about new users and the portal on the forum. But if you just go to my.isy.io and sign up for a new account, I think it walks you through.

regarding the portal, I don't really think anything has changed as far as setting it up since its inception. The portal is just a pathway to your ISY from the internet that doesn't require opening ports on your firewall. You don't need the portal at all if you are willing to open ports. Most folks would rather not do that. The portal also facilitates using google home and amazon alexa. These two things do keep changing in the sense that more functionality gets added. Regarding using Amazon to say "shed open" or whatever. That is fine and all. But unless you have one in every room, you are likely to not hear it. The "chirp chirp chirp" is heard everywhere (assuming you have switches all over the house) and is relatively innocuous. You can do both of course.

I don't understand. Momentary means the contact closure holds for whatever you set, say 1 second. That is still a toggle. It is ISY "pushing the gdo button". Just like if I push and hold the button with my finger for 1 second. If it is currently closed, it opens, if open, it closes. Unless you have some different kind of gdo than I am aware of. I suspect that the latest and greatest that have wifi and apps probably have an api that allows for separate open/close network commands, but I don't think many of those are out in the wild, plus, I'm don't even know that they actually do that.

Most garage door openers (all as far as I know) simply issue a toggle command. So you can't do that. I have my garage doors connected to Elk zones, so the status is never wrong.

The PLM, I believe, has a queue (either that or ISY does). But either way, there is about a 1/2 second delay between multiple Insteon commands issued at the same time via ISY.

You can make your Insteon light switches inside the house "chirp". I have the blue iris node server and programmed blue iris to trigger when an object travels up my driveway. So now I hear "chirp, chirp, chirp" every time someone comes up the driveway. Then I can meet the Amazon guy at the door. Anyway, you can have an Insteon door sensor trigger ISY to make your light switches inside go chirp chirp chirp if you like. Unless you are in a dead sleep, it should wake you up. And it isn't as jarring as an actual siren would be. Also, it would not be heard by someone breaking into your shed. So you can catch them red-handed, if indeed that is what you want. If you would rather scare them away, program a bunch of lights that are visible from the shed to turn on or blink. If you are more of the shotgun kind of guy, do the chirp chirp chirp and have some fun.

I had to click through the SSL warning message.

If you run conduit all over the place you won't ever have to worry about what wire will be needed down the road. Conduit is as cheap or cheaper than a lot of wire types and allows you to future proof things like crazy. Conduit runs all over the place!! Most of them will be empty at first, maybe forever. But it is worth it. You can dead-end conduit into various wall spaces so that later on you can just pop a little hole into the sheetrock if you want to add something weird in an area. Also, I highly recommend not going with a textured wall. They charge more for the "slick" finish but it just looks so much better and if you ever patch it, you can make it perfect. Matching texture is just never quite right. Put boxes in the wall in all of your closets that you run the conduits to and use larger conduit to connect the boxes to each other. A hub and spoke arrangement. Take tons and tons and tons of pictures, and video before the sheetrock goes up so you know where everything is. 1/2 inch pvc conduit is very cheap and easy to install. A propane torch and a nice smooth fanning technique turns it into flex conduit as well. Or you can run smurf tube, but the corrugation makes it harder to pull wires down the road. Personally, I would stick with Insteon for your switches. The switches they have been making in the last couple years are very good in my opinion. They look good, feel good, sound good, and work great. Plus you can pick them up at Christmas time for half price. Security in a 2 bedroom condo probably doesn't really need an Elk. I would just go with a DSC system and use the ISY node server for it. It is way cheaper and once integrated with ISY will have most of the features an Elk would offer.

ISY is definitely different than how most other languages structure things. Someday AI will be so intuitive that we'll just be able to tell it what we want to happen and it will ask us a bunch of questions to make sure it gets it right and then it will just happen. When that day comes, we will all become very stupid, but our HA will work.