MrBill

It was first announced on Feb 13th.... I read about it in the forum and didn't get an email either... https://www.universal-devices.com/byebyeclimatemodule/

i was just writing a response pointing to that exact example in the wiki

Disclaimer: I don't have the ELK add on, so I could be wrong. my guess is that you want OR for your If conditions: If Elk Area 'Home' 'Arm Up State' is Armed Fully Or Elk Area 'Home' 'Armed State' is Armed Away Or Elk Area 'Home' 'Arm Up State' is not Armed with Exit Timer When using AND it means all 3 conditions must be true, OR means at least one must be true.

Might be brand specific too.... as in some brands may be specific, others may use a simple voltage. Two reasons I can see for a manufacturer to do this. 1) more specific error codes. 2) ball and chain: you can't replace it with a 3rd party product, you're stuck with OEM.

@Michel Kohanim is this not the same battery devices write bug many of us are patiently waiting for to be addressed?

How silly, now they have to stock an additional SKU for paddle color change kits, and brown and black don't appear to be available in the new items color change.

not in browser, however these instructions allow you to run the admin console and connect via the portal.

It's a quick fix... we have to wait for the west coast to wake up tho.

You do have mismatched firmware and UI versions according to your screenshot, to fix that follow the instructions here: That probably doesn't account for the problem you describe however. As for what's wrong with your programs being intermittent I would have to wonder first if you've introduced a noise maker or signal sucker. Meaning the ISY is working just fine like it always has, but the signals aren't getting from the PLM to the device. I think this because if you say they used to work, it's the most logical reason they would become intermittent. Have you changed where they PLM is plugged in? Any new not necessarily home automation related devices. my wife once bought an air ionizer at a thrift store.... that thing made so much powerline noise that nothing worked at all when it was plugged in. We also used to have a deep fryer that when plugged in would kill Insteaon signals.

there is an expired certificate this morning, hold tight, it will be a quick fix once the west coast wakes up... it's still 7:30 in that part of the world.

In my system, I use a program that turns on the barn lights inside and out when the door opens after sunset, however after a certain time they won't turn off when the door closes, they stay on until manually reset. If it's after the specific time, it also rings the back doorbell 3 times, 5 seconds apart. The gates coming into the yard will also ring the back doorbell once if opened between sunset to sunrise.

Same here.... Paging @bmercier?

Have you tried this: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console

Mismatched. Follow the instructions here:

Do you have any idea what firmware version your ISY is currently running? Have you not updated firmware in 7 or 8 years? or am I reading too much into your wording? The best method is the Launcher, It will automatically match the UI version to the firmware version. Instructions are here:

$Fireplace.down.cycle = State Variable '#1704 / Downstairs Fireplace' Temperature = Wireless tag Temperature Node '$Fireplace.down.setpoint Fahrenheit'Is = State Variable If you don't want to have an override switch, you could skip $Fireplace.down.cycle There is actually 3 more programs that work with these 2 for a group of 5. Essentially there are 2 buttons on a 8 button controller that are controllers for the scene. 'DN Fireplace#' is also a responder to the scene. The extra "status" line in the IF of the cycle-on and cycle-off programs takes are of updating when the scene is turned on / off via alexa, or an iphone APP. the single Status is perhaps all that's needed, except this forum taught me to use Control in If's early on.... then when Alexa came along I added the 'status' lines also. I actually have another set of 5 programs for another fireplace.... these have worked very. Haven't needed delays, the temps only update once per minute. All 5: =================================================================================== Fireplace-Downstairs - [ID 007C][Parent 0001] Folder Conditions for 'Fireplace-Downstairs' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Allow the programs in this folder to run. ----------------------------------------------------------------------------------- Fireplace-cycle off - [ID 0078][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature >= '$Fireplace.down.setpoint Fahrenheit' And 'DN Fireplace#' Status is On Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-cycle on - [ID 0079][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature < '$Fireplace.down.setpoint.hysteresis Fahrenheit' And 'DN Fireplace#' Status is Off Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-off - [ID 007B][Parent 007C] If 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched Off Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched Fast Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched Fast Off Or '{hide}OUT Lower Fans - High / {hide}DN Fireplace' Status is Off Or 'DN Back Door Recessed+# / DN All Off' is switched Off Or 'DN Back Door Recessed+# / DN All Off' is switched Fast Off Then $Fireplace.down.cycle = 0 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Fireplace-Downstairs-on - [ID 007A][Parent 007C] If '{hide}OUT Lower Fans - High / {hide}DN Fireplace' is switched On Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' is switched On Or 'DN Back Door Recessed+# / {hide}Fireplace Downstairs' Status is not Off Then $Fireplace.down.cycle = 1 Else - No Actions - (To add one, press 'Action') ----------------------------------------------------------------------------------- Setpoint hysteresis - [ID 00E4][Parent 007C] If $Fireplace.down.setpoint < 80 And $Fireplace.down.setpoint >= 60 Then $Fireplace.down.setpoint.hysteresis = $Fireplace.down.setpoint $Fireplace.down.setpoint.hysteresis -= 1 Else $Fireplace.down.setpoint = 73 $Fireplace.down.setpoint.hysteresis = 72 When the setpoint value changes, and the new value is sane, then set hysteresis value. When the new value is NOT sane, set default values.

I'd separate this into two programs so that it can turn on at >= 90 and off at <88 or somethings. With only a single program two things come to mind the fan would go on/off frequently. Also I'd use and AND in If's to prevent excess traffic because each time the temp changes on or off is sent regardless of whether it's already on / off. Here's examples I use with my fireplace: Fireplace-cycle off - [ID 0078][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature >= '$Fireplace.down.setpoint Fahrenheit' And 'DN Fireplace#' Status is On Then Set 'DN Fireplace#' Off Else - No Actions - (To add one, press 'Action') Fireplace-cycle on - [ID 0079][Parent 007C] If $Fireplace.down.cycle is 1 And '#1704 / Downstairs Fireplace' Temperature < '$Fireplace.down.setpoint.hysteresis Fahrenheit' And 'DN Fireplace#' Status is Off Then Set 'DN Fireplace#' On Else - No Actions - (To add one, press 'Action')

on the Help > About menu of the admin console, does the Firmware and UI version match? and what version are shown?

It's my understanding (and I just tried again) that only the Admin User, located at File > Set Userid/Password works. If you attempt to set one in Userid 1 -9 it appears to set, but is unusable for logging in to the admin console. The wiki page, doesn't contain instructions for using those entries either. I think in the past I've answered several queries about those here in the forum with essentially "they don't work, they might be for future use, but haven't yet been implemented yet" and I believe @Michel Kohanim has "liked" at least one of those past post, perhaps indicating he agrees. But on the other hand maybe it's one of those bugs that some people think is getting fixed but no one in development actually realizes exists. Or perhaps @bambamf16 is referring to the "User" tab of the portal, where sub-accounts are created. That doesn't seem likely tho because the list of Currently assigned users, shows on the Users tab, the same place they are added.

WOW, I thought this was a known bug for a long time. It's kinda like scene re-writes to battery controllers, I thought we were just waiting for it to be fixed. These are the two biggest I know of that effect my usage, but I wonder of there are others? Is there a public list of known open issues anywhere?

You build your own customized content for the texts the same way you do for emails from ISY. https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables If your carrier is AT&T using 10digitnumber@txt.att.net means that the messages arrive from 1 (410) 000-XXX and are broken into max 160 character messages, often arriving out of order. If your carrier is AT&T using 10digitnumber@mms.att.net the messages will arrive from the email address that sent the message and has max length of 1000 char (I think). If your carrier is a different provider they all have their own similar email to sms/mms gateways. Many are listed in the table in this wikipedia article.

I believe you! I also believe my observations. Unfortunately those two things are mutually exclusive, hence my statement. That bug and the GUI bug's around Backlight, On Level, and ramp rate also never seem to get love.

@apostolakisl this has been an interesting exercise. But it just proves once again that I don't understand what's happening in the error log. I ran the THEN branch of the Factory query twice, it finishes quickly, 2.5 minutes with zero devices error-ing out. I wish I could watch it during boot. I'll have to start watching the error log again at the 3AM mark.

I literally leave the Christmas Insteon devices plugged in all year round, lol. 3 stay in place and the other, 2 I move to a plug strip under my desk. My wife bought a new fountain, so one of the "Christmas" devices became a Summer fountain controller this year. Today, I've actually been wondering if open/close sensors and recessed open/close sensors are getting hammered in the Query all. (they shouldn't be, but since V5 tries to write to them for scene changes it's made me wonder if ISY is trying to query them). I'll try running a 'query all' soon with the event viewer open to level 3 to see if anything gets queried repeatedly and/or errors.

@Michel Kohanim has told me that my assertion that the unwritten data builds up is not correct. However I'm not sure what to believe because when I remove the scene updates involving a battery device my queue full problem goes away. For me the real solution is to fix the bug so that the scene updates only write to the non-battery devices, the way it worked in v4.x.