hart2hart

That confirmed my thought process. Reinstalled from production store and devices all remained the same. The polling intervals did revert to defaults. At least shortpoll did as I had lowered it a bit below default. Thanks!

I purchased and installed the Node server when it was only in the non-prodcution store and it is labeled as Beta. Works great for my very limited use of LED strips. I now see it in the production store with same version number. Simply for future support purposes, should I install again from the production store?

I’d use current serial PLM to control number of things changing at same time.

Glad to hear it!

Maybe SD card was damaged when power supply failed. Replace it and restore a backup might be a possibility. Also, just saw post where a rj45 cable went bad and caused issues.

Thanks. Do you have this lock? If so, what conditions can you trigger automation based on? You mentioned lock/unlock … are there others?

Thanks. In essence, that’s my question is there a way to engineer a connection between ISY and HomeKit? That’s assuming HomeKit even has needed nodes and or actions to trigger what I want. I had looked a Node server store and did not see home assistant node? Did I miss it?

Revision 8.2. Have not install so FW unknown.

I want to integrate this Schlage Encode Plus into ISY. It integrates with Homekit. For example, if someone opens the lock, could I get the usercode / lock status to ISY? I do this now with Zwave Schalge so I can open door and disarm security in one step.

I just received my order of 2 six button Keypadlincs — Manufacturing date is 3922!

The issues from your original post are when the state of the switch/device is reported at 3;00 am s as no it’s different than what the ISY had thus causing some program or potentially a scene to be executed. The typical issue is bad communications and status change has been missed. Look for any program or scene that the device coming on in the night and see what triggers it. Then check those device’s actual status against what the ISY / plm sees to determine if they are out of sync.

There is usually a query all device program that runs at 3:00 am by default.

That is much more concise. I missed the adding node server device (fan) to scene with a command. Thanks.

EDIT — I created programs for fan off, low, medium, and high instead of creating mixed device type scenes (they are in essence the same thing but programs give more control it appears in this case) on ISY. Used scenes same as defined for a fanlinc to keep right button light on. Created a program to turn off all buttons including the off button when turning fan off. Works great! Not the source of screen name but oh the memories. Lol I saw it on admin console and tried putting the device into 3 scenes linked to keypadlinc buttons. I though I’d set the speed as desired and then pull the Media fan into corresponding scene with associated button. It appears that I’m only getting last speed I declared so feel I’m obviously doing something wrong. To the point, How would/could I put same fan device into 3 scenes and each would be at a different speed?

Does running Then record a value? The every 15 seconds is a battery saver feature. Its under settings stations stations "your station name" Manage Devices Sky Advanced Power Save Mode turn it on. You may have temptest where sky and air are in one device together so it may be a little different In iOs app...

Is your weather flow set to measure the wind every 3 or 15 seconds? Try removing the else clause and see if the value is going back to 0 between actual samples.

I've added 3 ceiling fans to my Bond bride. Each of them have 3 speeds on the Bond App where they can distinctly set the fan to Low, medium or High. On Bond, they are called Speed1. 2. 3. I can even tell alexa to Turn Media fan Speed3 and it goes to high -- for example. When you discover you only get the Fan but not the speed "Devices" feels like they should be there. I'd like to request they be added. Also, all three of my fan lights can be dimmed but they are discovered as NoDimm -- why?

Something went wrong with you original PLM restore PLM. It only takes that one step and then a lot of device updating occurs. My only guess is you had device writes turned off but that’s just a guess. I’d open a ticket wit UDI. .

Steve Lee was one of three panelist and he mentioned it a couple times even in last 20 minutes cast in a good light. They don’t necessarily want hub users. That was not the business model. I missed first part for a work meeting but they were referring to Insteon line and the strength of the true dusk mesh network snd navigation of the supply chain. I’m sure the first half had great information. It was recorded so I hope it will get posted soon. EDIT. LINK. Sound sucks. It’s third party capture

Thanks for your excellent efforts moving PG3 forward.

I’m in!

Add the button to a scene (create scene if needed) and turn the scene on and off.

I’ve had load button on keypad stop working. Did a factory reset and restored device fixed it. I think of the keypads as fly by wire so commands and button pushes are suggestions. I don’t think it’s hardwired do it was reasonable that it fixed it.

Another way of saying... You can upgrade isy994 to 5.0.16C if you have a zwave 300 series board and can upgrade to 5.4.4 if you have a zwave 500 series board or no zwave. I compiled a list of steps to get from 4.x fw to 5.x fw and it’s posted here somewhere. Find it to prepare for what’s ahead. Complexity and time required depend on type and numbers of devices and programs.

I was looking for data logger and another member pointed me to this https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic.2FCustom_Page_Creation It works well on 994 but not sure if it carried forward to IoP.