I set my router to give the EVL4 a static IP lease and kept the EVL4 itself configured for DHCP. I actually reserved an IP address for it on my router before plugging it in so that I’ll know what IP it was going to get. I heard about this particular issue on their forums.
By the way, using a web CoRE piston and 3 virtual switches, 1 routine (along with my already existing ones), and an additional trigger for my away/night/home routine I was able to accomplish what I wanted. My Ademco/Honeywell keyfob’s “away” button puts the alarm into away mode, which puts SHM into away mode. The CoRE piston monitors changes in the shm status variable and turns on the appropriate virtual switch (which would be triggered by relay in the other project). The away/night/home routines are activated when their appropriate virtual switches are turned on. The home routine is linked to the disarm function on the keyfob as well. The keyfob’s stay button arms the system in stay mode which just turns on the alarm in “instant stay” and nothing else, SHM status of course reflecting this mode as well.
I went a step further and used the SHM stay mode with a conditional so that if my house is in “night” mode (which is simply after the sun goes down) it goes into my “bedtime” mode which is the mode the turns off my lights and HVAC on my main floor (all bedrooms are upstairs) as well as locking doors. This bedtime routine runs on a schedule a bit past our bedtime in case we forget to run it manually.
The way I did this works for my particular needs although I probably could do it more elegantly. I didn’t want to buy any additional hardware. I am just happy to make this integration work. These forums are full of smart people so thank you all!
It’s nice that simply setting the alarm like we did before all this home automation, using our old school alarm keypad and keyfobs, now actually kicks off a lot of automation that I have complete control of. This helped with the WAF (wife approval factor).