TheA2Z

Checked Port with Portchecker. Its open. As for the Host ip config, @MBell that is my IP of my actual rachio device on my network. I thought this was my IP and that the Rachio web will send data via webhooks to it and the port?

Need some help on this one. Installed from PG3 store. In config, I put: Poll short left at 5 Poll Long left at 60 API key from Rachio site. My DDNS address port left as 3001 Left Node additional Interval blank In my Ubiquiti edgerouter: Port Forwarding Page Original Port: 3001 Protocol: Tried all three, UDP, and TCP. Which one? Forward to address: IP of Eisy/ PG3. It is the same for both. Forward to port: Tried 3001. Tried PG3 port. Is it the port number I put in Rachio config or Port number of PG3? With all that, I did not reboot PG3/ Eisy. Wanted to validate config first here.

Eisy is the Universal Devices replacement for the ISY. I moved to it from my ISY.

Why Polisy vs using Eisy device?

I have some battery Zooz devices but not the door sensors. However, they may work the same. Here is what I did to resolve similar problem. Remove device from Eisy Factory reset the device. If you have ability to update the Firmware, do so. I use a home assistant setup that makes it real easy. Here is where it gets fun. Put eisy in add to zwave mode. Take sensor close to eisy and put in inclusion mode. Every 5 to 6 second wake the sensor again Repeat 6 until the sensor is included. See if that works for you.

Agree Timedata is way to go. I was posting a workaround for you in event it is not fixed or fixed quick enough for you.

I sent right when you did. I see now. Impressive. I may be out of my lane in this, but why couldnt you assign minutes to your variable using below screen shot. Then use counters to calculate. Granted it probably could be done programmatically in ISY/eisy, but much easier using Timedata.

Not knowing exactly what the details are. What about something like this where the program would run every second, minute or hour. In your Then you could put the action.

@AGinsburg01Ah. If you dont mind me asking, what is the use case where you are trying to trigger an if on a minute, hour or second value?

Update good. Have not tried Zigbee yet. Need to get a device. Will most likely get a motion. Have not been happy with insteon/ zwave motions that I have used so far.

@AGinsburg01To use ISY or Eisy, just create some variables and run once a night to update them. I dont use time variables but you could. Here is the program to update the variables.

Ah sorry missed that. I dont have Polisy. Hope it gets resolved for you soon as I know that is frustrating.

Sounds like @Michel Kohanim is going to need to get involved in this one. be sure to open ticket. Just spitballing here but try shutdown, then remove zmatter from Eisy, then reinstall zmatter, they restart eisy to validate there isnt a bad connection on zmatter into Eisy.

Thanks. I have programs that calculate many of these as variables that I have used for years. If I was starting fresh, I would of just used this.

Aqara MS-S02 Motion Sensor P1 (aqara.com) Motion Sensor

Does it support Zigbee 3.0 devices? is it just bulbs or all Zigbee devices supported?

What does Timedata give you over just using time and date native in ISY and Eisy?

Beauty is in the eye of the beholder. I agree that I wont be able to sell my house for $ 2K more because I got $2k in home automation. My system is also complex. My plan is to dumb it down when I move to use the most easy controller available at that time and probably integrate it with Alexa. This will make it as simple as possible. It all depends on who the buyer is though. They may be into automation or willing to make it a hobby. Or they wont. Highest bidder gets it regardless. They could bulldoze the whole house for all I care

Worked as advertised. Thanks UD team.

I had same problem. Opened ticket and @Michel Kohanim had me do an upgrade. see my post in other thread:

This is fixed with new version I just installed working in a ticket with @Michel Kohanim Rebooted Eisy Then did an upgrade packages and rebooted. Thanks @Michel Kohanim and team!

This is fixed with new version I just installed working in a ticket with @Michel Kohanim Rebooted Eisy Then did an upgrade packages and rebooted. Dont get RSA error anymore. Thanks @Michel Kohanim and team!

This is fixed with new version I just installed working in a ticket with @Michel Kohanim Rebooted Eisy Then did an upgrade packages and rebooted. Cloud version now works properly and shows right versions. Thanks @Michel Kohanim and team!

On my issue 5 posts above. Opened ticket. @Michel Kohanim instantly responded that it is a cache issue and to just retry in a couple of hours.

@tmorse305 Eisy appears to be working properly despite the error in my log above.