apostolakisl

Looking back at the original post, he says it changes every 20 minutes or so. That is hard to explain. The device (eisy) asks for a lease via a network wide request (the first time), the router hands out an ip with a lease length. Check the router to see what that time is set to, 24 hours is common. The device keeps track of its lease time and it requests an extension at the half way point. At this time, the router could give out a new address (but wouldn't unless you changed settings on the router). Devices usually don't put out a broadcast request for lease renewal, it usually goes directly to the dhcp server IP that gave its current lease, so a second dhcp server shouldn't even know about it. If it asks for a renewal and gets back crickets, it will just keep the current IP address and keep trying. At least this is how I understand it all works. Anyway, for the ip address to change in 15 minutes, that would imply the lease time was only 30 minutes and that the request for renewal came with a change of IP. I expect that FreeBSD is handling all of this. I don't know how that could get corrupted in such a way to do this weird behavior. I'm assuming all of the IP addresses that eisy is using are on the correct subnet. Assuming that FreeBSD was going bananas and just giving itself random numbers, they would not all be in the same subnet. IF you telnet into eisy, there are commands to see the status of the dhcp client, you would have to look them up, I don't know them off the top of my head. You can also assign a static IP address via telnet. Again, need to look up the commands.

Is it possible you have two dhcp servers on your network? If the mac address is always the same, but the ip address is changing, this has to be a problem with whatever is assigning the ip address. When you see the non-correct ip address getting assigned, is it always the same "other" address, or is it always seemingly something random? If it was an issue with it switching back and forth between wifi and ethernet, you would get a different mac address for wifi and ethernet, but I would expect it to keep getting the same ip address when on wifi and the same for every time it is on ethernet, even if you don't have static dhcp assigned to both. DHCP servers generally give the same IP address to something over and over unless it has been offline for an extended period of time. I doubt ISY firmware plays a role in IP address at all. The Eisy/Polisy firmware runs on top of FreeBSD which I am sure is handling all of that.

It appears that the https://trigger.esp8266-server.de/ server is now a gonner. Other options included voice monkey and ifttt. But both of those have very limited free options and I have no intention on getting into one of those recurring charge things that I forget about and a decade later you gave them $1000 for something you forgot you even had. Anyway, I decided to go with virtualsmarthome.xyz which is free, but you can (and should) make a donation. It works the same going through network resources so all I had to do was update the network resource and update the routine in Alexa to switch from the esp8266 setup. chat monkey works the same as well. virtualsmarthome.xyz nodes in Alexa default to being doorbells, so you have to also shut that off, assuming you don't want alexa to make a doorbell announcement every time you trigger the url. The process is 1) enable the virtualsmarthome.xyz skill in Alexa 2) login to the virtualsmarthome.xyz website using your primary alexa account 3) Where it says "create . .. " fill in a name for your trigger. I include the words "virtualhome.xyz" in the name so I don't get confused about it later on when I can't remember what the heck I was doing way back when. 4) A few seconds later, Alexa discovers it and you will see it under the devices tab. Open it up and uncheck the doorbell function. 5) In Alexa, create a routine and put the virtualsmarthome.xyz device you just made as a trigger for the routine. 6) Return to the virtualhome.xyz website and open up the trigger you just created. You will see the following info. Copy everything starting with to the end </url_. . . > I used the json response. 7) Create a network resource in ISY and format as below. Paste into path what you copied from above. Set the it to "get", fill in the host and delete from the header section all the stuff not listed below. 8) Create a program in ISY that triggers the network resource as you desire. Note: I decided not to use ISY portal connection to Alexa that can directly trigger routines because of the 30 second time out after each trigger. This just doesn't work for me. You may ask, why do this? For me, the whole reason is that I have several items in my home that do not have ISY polyglot nodes but do have Alexa integration. Specifically, Levalor motorized blinds and some ceiling fans that use the Tuya control system. Both of these have Alexa skills, but not ISY polyglot nodes. This allows ISY to control those devices using Alexa as an intermediary. In short, anything that has an Alexa skill can be controlled by ISY in this fashion.

Google voice allows email to text, but it is slightly tricky to set it up, but once set up it works perfectly every time. You need to enable google voice to send a copy of all your texts to your email. First thing is to receive a text from the phone number you want to send texts to. This could be you sending a text to yourself. Then copy the from address in that email copy of the text and put that as the to address in ISY. That address defines for google voice where to send it, both the phone number and the text thread. Of note, the email account that ISY sends emails must be the same one you have google voice copy texts to. It follows this format <yourphonenumber>.<thetophonenumber>.<stringofnumber/lettersthatidentifythethread>@txt.voice.google.com I sent myself a text to get the thread going so the two phone numbers in my case are the same. I set this up this many many years ago and the thread still keeps going. If you want to send the text to someone else, you would need them to send you a text or reply to a text from you to get that email address format I showed above..

Yes, IF the variable is a "state" variable. Integer variables are not triggers. Integer variable are used to affect the true/false status of a program when something else triggers it. No, if it is a state variable, it only triggers on a change of the value. Again, it is integer, it never triggers. Yes, when it changes at all it will be a trigger, if it is a state variable. It is the change of the variable that is the trigger. For example, If $s.test is 1 Then do something Else do something else In this case, if $s.test is currently 2 and it changes to 3, the program will trigger and go false. In the case it is 1 and some other programs sets it to 1 (so it doesn't change) nothing will happen. If it starts as 2 and changes to 1, it will trigger and run true. Status in an if clause triggers the clause on any change in status. For example, if status is 25% will trigger on any change in the status of the switch. Say it was off and it turned on, that would trigger the program to run false. Status responds to any change in the switch no matter how it happened. It could be responding to a scene command, responding to a program, or responding to local control. Control in an if clause ONLY triggers on that exact thing happening on that device. For example, control switched on, means someone clicked the on button on a switch. Nothing else done to the switch triggers the program. Turning on because it responded to a scene or program does not trigger the program.

I agree. The java admin console has all kinds of bugs in it that cause it to lock-up, have hidden windows, and generally just stop working when you leave it open. But never have I seen it do bad things to eisy/polisy/isy. In the very very old days of windows, ctrl-alt-delete /end program was just a thing you had to do for lots of stuff. But for the last 15 years or so, only with java.

Control statement important considerations 1) Only an action originating at that device is a trigger. Typically that means you physically acted on the switch. However, things likes motion sensors would also trigger a control statement if it picked up motion because that device is the origin, it isn't responding to another device. 2) The status of a device is not relevant to a control statement of a program. (though you can still have separate status lines in the same program, see point 5) 3) Use "is" logic to trigger true, use "is not" to trigger false and you can have both in the same program. For example: if device a is control switched on and device a is not control switched off. In this case, the program runs true when you click the on paddle, and runs false if you click the off paddle. What it does is make the program mirror an action at the switch. 4) A control statement using "is" logic will only ever be true if it is the trigger of the program. So if you mix status items into a program with control, then that program will never be true when triggered by the status line. Using "is not" logic is the same but opposite. Also along these lines, you would never have two "control is" statements in the same program if you ever wanted it to run true because you can never have two devices simultaneously hit the program at once. No matter how hard you try to hit two light switch on paddles at the same time, one will always come before the other. 5) You can combine status and control for certain logic. For example: If device a status if off and device a is control switched off, then . . . . In that case, if the light is off already, and you push the off paddle the program runs true. In my home I use this as a night light feature where I can get up in the middle of the night, hit the off paddle and the program turns the light on to 10% instead of the usual on level.

OK, I just tapped favorites, didn't hold it. I think that does it. Thx.

I tried again. Rebooted the phone and it is reverted to home page again. I tried deleting the icon (it was in quick launch bar), going back to original icon in my full list of apps, press/hold/add to home screen. That put it in the regular home screen. I pressed and held and hit favorites. Now it opened to favorites. I dragged that into quick launch bar. Still opens to favorites. Rebooted phone and it reverted to opening to home page. I tried then only having it on the home screen, not quick launch bar, still reboots revert it to opening in home screen. Not sure what else to try.

This seems to be only a sort-of fix. I rebooted my phone and it reverted back to opening on the home page.

Thanks. Not sure how you figured that out but good job.

My Android skips from lock edits to favorites span. I don't have the launch preference. Is it somewhere else in Android? EDIT: Don't know if this matters, but I have two ISY's on my UD mobile acct. Doesn't matter which I look under, it is the same, it skips that field.

That is a good idea too. I was just trying to teach someone how to use UD mobile and it is just way too much for a user only person to look at. A version that only opens to favorites and requires an admin password to edit the favorites.

I would like to make a suggestion that there is an option to set UD mobile to, by default, open to the favorites screen instead of the home screen. 99% of the time, I just have to click "favorites" after opening, and I'm guessing that is the same for a lot of others.

Yes, that is correct. The java console is still plagued with quirks and is supposedly soon to be replaced by a fully functional browser interface.

You need two programs, the first program contains all the if conditions. Then clause does a run then on second program and disables itself. If clause on second program is blank. Then clause contains your actions and concludes by re-enablung the first program.

From this screen. I have the edit enabled, I change the name (just deleted the AHU3 part). I hit "save" in the upper right corner that shows up after I start editing, it does the little swirly thing for a couple seconds and takes me back to the previous page. But nothing changed. Same name (which is apparently too long and it is cutting off the word "lobby"). And if I hit device dashboard again, it returns me to the page shown above with the name still un-edited. This ISY is running 6.0.4

Right after I upgraded, I went out of town. There was a big wind storm and it blew over an outdoor potted plant that had led lights in it controlled by a lamplinc. The wire to the lights tore and it was making the lamplinc sense go bananas. 6.0.5 could not function with that going on. Via VPN, Michel downgraded me to 6.0.4 which got ISY to run, but the java programs page wouldn't open. The programs were all working, you just couldn't get to them in java. But you could in UD mobile. Michel said there was a program set to run at start that was in a loop doing this. I was skeptical, because I have had all those programs for years without issue. Anyway, I shut down all the run at startup programs from ud mobile, but the programs page was still blank (no panes or grids or anything, just a blue screen). I tried upgrading to 6.0.5 again and now all is fine. I re-activated all the run at startup programs and all is still fine. My theory is that the downgrade wasn't complete and there were some mis-matched files preventing the java programs page to load. The main thing here, as I see it, is that 6.0.5 crashes if an Insteon device is misbehaving whereas previous versions could deal with it.

had some issues with .05 and went back to .04. The node is still populating correctly. ???

@Javi I am still having issues with the names of thermostats I added. For Example, Venstar AHU1 Conf (this is fine, displays as expected) Venstar AHU3 Lobby (this displays as Venstar AHU3 it cut off the Lobby part) I open the full device dashboard page and the full name is there, I try to edit the name, hit save, but it doesn't save it.

I'm still on 6.0.4 and did legacy sync and at first glance it seemed to have worked.

I restored a backup from a few months ago, and all is normal for how it was at that time. But when I do a synchronize, it breaks again. I got no errors, but my nodes are either missing, not configured correctly, and nothing populates. This isy is running 6.0.4. I haven't made any changes to the ISY firmware since I upgraded to 6.0.4 however long ago that was (not long after it was first introduced). The changes I made that needed sync'ing was I added a new PG node and moved a PG2 node to PG3 and deleted a few devices and changed a few programs. EDIT I tried uninstalling ud mobile and clearing all data. Again, the sync results in the same non-functional ud mobile. Restoring the backup gets it back to a working ud mobile as it was at that time.

I have two ISY's connected to UD mobile. I made a bunch of changes to one of them and re-synced it. I got some error about a node definitions file if I recall and now none of the nodes on that 1 ISY work. My favorites folder had bunches of stuff from that ISY disappear. Further syncs show no error but don't fix it. @Javi The other isy seems to be normal.

@paulbates Seems that you are correct. I factory reset again, setup wifi, turned on api, and they are both working with nodelink and pg3x. I will let it go for a few days and then see what happens if I try connecting to skyport.

Possible. I factory reset the two that aren't working, connected to wifi and turned on the local api, and I got a connection on nodelink (didn't try pg3x at that point). I thought I had it fixed, I then rejoined skyport thinking I was good. When I went back later to check on it, it was no longer working. So maybe I need to leave skyport off.