MrBill

The only thing that could be a serious issue is if your programs make extensive use of adjust scene where the scene controller is a wireless device such as a motion detector, Open/Close Sensor, Hidden door sensor, or wireless Insteon remote. Specifically: Where the Action in a program is Adjust Scene and the Controller is a battery device. This isn't always used by everyone, but it might be used to provide, for example, a different level of dimming at night. The function does work correctly when the controller is NOT a battery device, however the action will not convert when upgrading 4x -> 5x, and the program will need to be manually adjusted and then re-saved. Other than this issue, I agree 5.0.16C is rock solid.

I use that value from the wireless tags nodeserver like this: (run at startup) If '#1704 / Freezer' Last Update Time > '$freezer.tag.hb Raw' Then $freezer.tag.hb = '#1704 / Freezer' Last Update Time Wait 11 minutes Send Notification to 'Bill' content 'Freezer HB' Else - No Actions - (To add one, press 'Action') Normally the wait is interrupted because of an update, so the then body only finishes when an update is missed. I've considered adding one more statement to the end of IF: Run Program 'Freezer HB' (else body) and then making Else Wait 24 hours Run Program 'Freezer HB' (if) to make sure it gets restarted... and to nag with another notification in case I forgot to deal with it... but I haven't tested that but I don't see a problem where it wouldn't work... except if maybe the nodeserver wasn't running with the ISY restarted.

Ideally you would use seconds from the epoch which is easy to obtain in python, thus it stops when the node server stops, but never resets. the Wireless (CAO) tags node server is a shining example:

the always increasing time in seconds value is a simple method that never fails.

it was.... when you right click an Insteon device in the tree the "replace with" context menu does not appear if the device located in a folder. It must be moved to the root level to use the function.

if you're having this kind of trouble you should open a ticket. support@universal-devices.com include the new and old email address as well as your UUID to expedite.

I just created this program: AAA TEST - [ID 00E8][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $temp_test = 1 Else $temp_test = 0 Added it to the portal as: "Alexa, Turn on the toaster" sets the variable to 1 "Alexa, Turn off the toaster" sets the variable to 0.

do you have an else body in the program? in my experience on is then, off is else. or paste the program and show us how you have this set in the portal, maybe I'm not understanding what you've set up.

The magic happens in the portal. Instead of mapping Alexa to a device she's instead mapped to update the state variable.

it can be done... here's almost what you asked for: the change you'll need is in the alexa.on program you'll need to repeat each of the devices dim levels. The problem is scene's can't be dimmed, they can contain members preset to a certain level for that scene but they weren't designed for setting the scene itself to a certain level. I actually have a group for 3 lamps that I did with individual controls like in the linked post (1 variable and 3 programs for each lamp). And then made a "group" program to control the individual lamps: Alexa.on - [ID 00A1][Parent 00A4] If $Dim.Lamp1_2_3.group > 0 And $Dim.Lamp1_2_3.group <= 100 Then $Dim.Lamp1 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp2 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp3 = $Dim.Lamp1_2_3.group $Dim.Lamp1_2_3.group = -1 Else - No Actions - (To add one, press 'Action') Alexa.off - [ID 00A3][Parent 00A4] If $Dim.Lamp1_2_3.group is 0 Then $Dim.Lamp3 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp2 = $Dim.Lamp1_2_3.group Wait 1 second $Dim.Lamp1 = $Dim.Lamp1_2_3.group $Dim.Lamp1_2_3.group = -1 Else - No Actions - (To add one, press 'Action') Basically if you use the group spoken to set a level for the group, these two programs set the variable for each lamp with a wait between each. The group variable always gets returned to -1 as soon as it's used so that anything you tell alexa registers as a change. You could also just do one scene for the group and in the alexa.on program, set each fixture to the level.

@bmercier probably needs to assist you.

After ssh to Polisy, become the polyglot user... sudo -u polyglot -s supply the admin user password when prompted. then cd /var/polyglot/nodeservers then ls -la will show you the directories for your existing node servers... your node server should also reside here, in its own directory.

I have this problem at my house too, and I have a workaround that's almost perfect. At my house Insteon came first, and the system was designed with lots of 6 and 8 button controllers. I very quickly grew tired and irritated with Insteon's hub and upgraded that to an ISY. It wasn't until years later that Alexa came to live here, at the same we'd been using our phones as a remote control and that was for unrelated reasons becoming something that wasn't reliable. Like you I discovered Alexa did a lot of good but at the same time my switches were always out of sync with each other. and most of the switching is built on scenes. To implement you'll need one state variable for each pair of switches and 3 programs, to summarize each: The state variable with have possible values of 0=Off, 1-100=known dim level, 101=On, dim level is unknown. Alexa.on is the first program, and allows Alexa to control the scene and dim the device as needed. (I'll cover how to setup Alexa in the portal later.) Essentially if the value of the vaiable changes and is greater then 0 or less than or equal to 100 then the program first turns on the Scene, waits one second then sets the dim level of the DEVICE that actually controls the load. (Since I have a lot of second switches or KPL buttons a naming convention that I use in my system is to append a # to the end of the name of any device that actually controls the load... it makes telling them apart easier.) Manual.on is the second program, and sets the variable to keep track of when the light was manually controlled via a switch. Basically you need an OR condition for each of the devices that can control the scene and 3 conditions each, ON, FAST ON, or FADE STOP. So in this example the light can be controlled by 3 manual switches. If we detect that the scene has been turned on manually with a switch, then we set the variable to the special value of 101, which signifies that the scene is on, but we don't know the dim level (and we really don't need to either, we just know it's NOT off). Off is the 3rd and final program in the group. It works for both control from Alexa and control from a wall switch. Again using Control, you need to catch Off and Fast Off coming from each switch OR if Alexa changed the state of the variable to 0, then we set the variable to turn the scene off and set the variable to zero. Actually one or the other condition is redundant, but the way the ISY works allows us to use one program for off instead of having both Alexa.off and Manual.off... in this case we can combine both of those programs into one and just call it off. =================================================================================== Lamp 1 - [ID 0098][Parent 00B7] Folder Conditions for 'Lamp 1' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Alexa.on - [ID 000C][Parent 0098] If $Dim.Lamp1 > 0 And $Dim.Lamp1 <= 100 Then Set 'LR Lamp 1' On '$Dim.Lamp1 %' Wait 1 second Set 'LR Lamp 1#' On '$Dim.Lamp1 %' Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Manual.on - [ID 0099][Parent 0098] If '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fast On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fade Stop Or 'Kitchen Table Light# / {hide}Lamp 1' is switched On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fast On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fade Stop Or 'LR Remote -Deb - A-B' is switched On Or 'LR Remote -Deb - A-B' is switched Fast On Or 'LR Remote -Deb - A-B' is switched Fade Stop Then $Dim.Lamp1 = 101 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Off - [ID 0095][Parent 0098] If '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Off Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fast Off Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Off Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fast Off Or 'LR Remote -Deb - A-B' is switched Off Or 'LR Remote -Deb - A-B' is switched Fast Off Or $Dim.Lamp1 is 0 Then $Dim.Lamp1 = 0 Set 'LR Lamp 1' Off Else - No Actions - (To add one, press 'Action') To configure the portal for Alexa you will want to ADD Variable: Then on the next screen, select the state variable you created, select Scene for Alexa Category, put 0 for the "Off" value and 100 the on value. (In my example, "ON" actually means set to 60% dim... any number from 1 to 100 is works for the turn ON value.) Now first say "Alexa, Discover devices" once shes done try: "Alexa, Turn on whatever light" "Alexa, Turn off whatever light" "Alexa, set whatever light to XX" (you can say the word Percent or drop it and just say XX. You can also mix in controlling from the wall and you'll see everything stays in synch. The only annoying issue (which also has a workaround) is that if you're using Alexa and starting out from OFF and setting a DIM level of say 20%, the light comes on bright first then dims to 20%. That's because in the Alexa.on program we must turn the scene on first, which actually turns the light on, then wait 1 second, then set the actual dim level that we want. The workaround is to have a longer ramp rate. (I uses 2 seconds) which will begin to fade on the light, then 1 second later comes the dim command. As I type this it occurs to me that if the only manual devices are two 2477D dimmers like in your kitchen, then you'll want to set the DIM level for both switches so that the left LED's on the switch will display correctly. I actually don't have that situation. It's a little bit tedious to set this up for each scene you want to control via Alexa, but once it's set up it does work and doesn't require maintenance.

Wrong log. Look in the error log for clues.

Does the ISY error log provide any clues?

Use this site to get your latitude/longitude: https://www.latlong.net/convert-address-to-lat-long.html My guess is that your numbers are correct but you need to enter longitude as a negative number. Entering that longitude as a negative number will put you in Pennsylvania The pair you are using is on the other side of the world.

You can also run local nodeservers on a Raspberry Pi.

I do have a polisy for local nodeservers, however I'm not actually running that one myself, the cloud version would be better. The problem with the local version of the rachio node server is that it requires and open inbound port from the outside (specifically from the rachio cloud server). I will add that you might be able to get your motion detector to rachio need configured with IFTTT as a middleman. I have a similar need to yours that I run to turn on one particular zone, the hose connections around the pool are actually on a sprinkler zone, so to make it easy I have hidden an Insteon Hidden Door Sensor in a dry outdoor spot. Press the button in and release and it triggers an ISY program , that flashes a light outside (visual feedback), and then calls a network resource, that connects to a webhook which is part of an IFTTT applet that then turns on the sprinkler zone for a 30 minute manual run. It works great... this solution pre-dates node servers, I was going to convert it over to take IFTTT out of the loop if there is ever a cloud version of the Rachio nodeserver.

not sure about using alexa as a middle controller for this, but there is a Rachio node server for ISY, if you're running the nodeserver then yes....

I've had trouble reading those labels lately D and 0 are hard to tell apart, can't think what other letters and numbers but watch the possibilities...

Browser developers have stopped making it easy to click a link to start a Java app. It's too dangerous and most users would probably click a malicious link that installed malware etc. that is disguised as a link for something else. Not gonna name names but if the browser link says "here is your favorite type of cutey kittens, click here" could get you a cute kitten pic AND malware if java is allowed, thats why browser don't launch java anymore. That's why ISY migrated to the launcher, which is not in anyway launched via a browser.

Insteon address look like AA.BB.CC... do you see a product label with address and firmware revision? I don't have any of 2844-222 so I can't say where they stick the label, on the back or possible inside.

You can go to https://my.isy.io/index.htm then click create a new account. this will allow you to create a portal account. You can't connect your ISY to it however, without subscribing to the portal service. The portal account is however UDI's new single sign on service.

At this point in time you keep the existing ISY994, we've heard that someday the ISY functions will likely move over to Polisy. Not sure where the Z-wave controller will be when that day arrives.

It's been noted before but I'll repeat it here. Only a few nodeservers (and most of those are weather) make sense to exist as both local options and polyglot cloud versions. Most seem to be better suited to run local because the other devices exist on the local network, or on PGC because the it's making a cloud to cloud connection somewhere. It also really wasn't hard for me from a time perspective to choose Polisy over Pi. While I have a few pi's around the house doing this or that, none of them are mission critical and none are allowed outside internet access (network rules). The biggest benefit of Polisy to me is that updates are pushed out, and I don't have to do much in terms of systems administration and staying up to date on OS exploits.