MrBill

so I think what you're saying is that you want this 40% to be 100%? If so then figure out the correct series of dropdowns for "adjust scene" to change it. For this scene you need two adjust scene, one for the isy or the root level of the scene, then you need one for the RED controller (which you have hi-lited in screenshot I repasted a portion of.

There is an ISY994 section, Z-wave - series 300/500 is a sub-section of that. This post will likely get moved there shortly, since the second part belongs there... The second part it sounds like you need to clear your java cache, includinging installed applets and Icons. is your java up to date? Version 8 Update 361 is current. Where you using the Launcher, or a file named admin.jnlp?

sorry the question doesn't make sense, I guess we need the picture. You should upgrade to v5.3.4 tho...

I'm not following if this is the same device as the adjust scene line. Remember tho, if using adjust scene, you must adjust the scene for each controller in the scene. For example in this scene there are 3 controllers, If I want to adjust the on value for all 3 controllers, I need 3 adjust scene statements. Adjust scene as you have it, i believe is adjusting only when the ISY is the controller. If you want physical buttons or switches that are scene controllers to also change... you need to also "adjust scene" for each controller.

Do you have wireless devices? is one or more associated with a scene controlled by the keypad? When you say green squiggly indicator do you mean the 1011 indicator? If you have wireless devices each of them must be awoken and then written to, if there is a scene that involves a switch or keypad involved it will clear up the keypad or switch when you get the wireless devices taken care of.

I've suggested that. I've also suggested decoupling the label and the button and relabeling the button SET and moving it to the right of the drop-down. This is one of the top 5 most repeated users instructions. The GUI is absolutely not intuitive and I've typed that many times as well. Functionally it works tho, so in UD's eyes there are bigger problems to solve.

yes it likely is on your end, either an error in your programs, or very remotely possible a very bad internet connection at your location. The common denominator is you. Multiple people using the node server, no one else is reporting this issue. Many more people use pushover, doesn't appear at least from the users here that his is a problem either, doubt it's an apple problem either, we would hear about it somewhere else. That leads us back to either the node server is repeating it, or your programs are creating it. BTW, FWIW... if you agree with Javi then your agree the problem is within your programs. Read the last two sentences of his post again.

So your saying all apple push notifications are repeating? yes that would be an apple issue. If that's not what you're saying and its only those that originate in IoX and follow the path Iox -> node server -> Pushover -> apple server, then there's several possible points of failure before reaching apple. If you think it's an apple issue, then why did you open a UD ticket? wouldn't an Apple case be more appropriate? So the same notification randomly repeats itself without being re-triggered? Or when it's retriggered it sometime repeats for awhile? Again here you need to look at the node server log... the node server is designed to RETRY if it doesn't recieve a "200 Ok" response (or certain permanent failure responses). Are the repeats in fact coming because a 200 is not being received? it could even be your internet connection at fault. Your wasting everyones time if your unwilling to check the nodeserver log, and show all related programs. (and if any variables are used in IF statement tell us if they are State Variables or Integer Variables.

To be honest I have no idea what you're doing or trying to do with that program. You set 3 variables, wait one second, and set them again to the exact same values. If all your programming is like that, no wonder you're having issues.... If the problem is the Notification nodesever repeating notifications, we and/or @Jimbo.Automates will need to look at the node server log. In addition to @DennisC's suggestion to paste programs as text and post all related programs, you should also name your variables so that anyone can tell at a glance if the variable is Integer or State (or possibly Constant). The general nomenclature that most use is the just make the first character of the variable name either s, i, or c, and then either add a period or underscore or simply capitalize the 2nd character.... c is a constant or a variable that never changes. Some Examples of constants: cTrue = 1, cFalse = 0, cBlue = 255 etc Using these makes programs more readable especially when you post them for someone else.... If $sAway = $cTrue then When $sDriveway_alert is to 1 it may trigger another program to run, when $iDriveway_alert is set it won't trigger another program, but might filter another program from running.

That should be correct. The initial value of the drop-down will always be 0. The admin console doesn’t know the setting stored in the device. Second, after adjusting the drop-down you must press the LEFT of the drop-down that has the word backlight in it.

this forum has a section titled "Current Release Announcements", inside it you will find a thread labeled "5.3.4 (ISY994) - Last release for ISY994" inside that thread you will find the directions to upgrade, with the file link included.

@Eric I'd migrate to eisy without upgrading your PLM. Then once you get post-migration kinks worked out replace the PLM with a USB PLM (It's not "an IP connection") which will introduce a different set of kinks to work out. The swap PLMs procedure is fairly intense, because when it happens many links in all insteon devices must be updated. Migration is also involved. I'd favor divide and conquer, one upgrade at a time. Yes, it's a little more expensive because you must buy or make the specialized serial to USB cable.

There are built in specific dates, such as: which would be true anytime during December THIS year. So we might combine two schedules using AND to do something useful like turn on the Christmas decorations, but only during December The problem with programs like these, is that they must be revised every year-- there is no method to enter a date WITHOUT the year in the built in date functions. Note for date option to show, you much uncheck daily: There's also a program that you can input once and run everyday to set a series of variables, that i've been using for a number of years... see this thread: with this method it's possible to find thanksgiving.. the 4th Thursday of November, or other combinations. As mentioned previously in this thread, there's also the date/time node server.

no idea, I've never had a yolink device, no idea what sensitivity they have. If you discover tho that quick press and release of the button doesn't work but an extended hold the button does, then consider there might be a time delay relay that will trigger quickly and extend the contact closure. I added doorbell notification before video doorbells were a thing. unfortunately--neither the chinese time delay relay or the 3rd party Insteon product that i used are available anymore. so providing exact details isn't possible however, lots of possible solutions on amazon. Thanks for letting us know. Not sure we can help here. Many people here have the peripherals, however we use a much more powerful ISY/IoX controller manufactured by Universal-devices who provides this forum to support their products. You'll likely get better help in other forums on the internet..... or you could purchase an eisy™, then we can better help you with your projects.

I ended up with a relay with an on-board timer, this allowed me to extend the button press to 1 second. The button press was too quick and the sensor couldn't detect it.

that only applies if you're using an Insteon Hub. Are you using an Insteon hub or an ISY/PLM? I don't have google home, so that half of it I can't help with.

Gosh the topic line of that post has been updated to add the word "Outdated" and then there is the Bold Red text at the top of the post....

Why in the world would you downgrade from 5.3.4? I'm not certain where the mailserver changes were made, but I'll bet that 5.3.0 is too old for the default mailserver to work....

@Harrisrc740 As Dennis points out the climate module went away about 3 years ago. If using the default server, Mail also won't work with older firmware versions. A spam attack changed the way ISY994's connect to the mail server. For the other problems have you tried simply rebooting the ISY? Only two easily available parts fail on an ISY994... the microSD card (hope you have a backup) and the wall-wart power supply... but before we get to far... answer the version questions that Dennis asked....

this morning at 1:14 am the online message arrived..... No offline before that, so i assume it was your correction.

you actually only need a wait in the program. The program re-triggers every time the status of the switch bounces. If OpenClose sensor status is On then wait 30 seconds Turn off pump wait 10 seconds Turn off pump If the pump is controlled by Insteon I'd turn it off twice 10 seconds apart just to make sure it turned off. The above program works for your use case because if the door sensor changes status (to off) during the first Wait the program will stop running, and when it switches back to on, it will start over.

This is the problem. Make certain that you have the PLM online for 30 seconds or so before booting eisy.. It needs to detect that the port exists. ...or the cable or it's built in converter is bad... or it's "wired" wrong and not communicating because of that.

@bmercier Woke up to a notification that my primary ISY was offline: Logged in the the portal and it shows the green "Online" light. Tested a portal connection, it works. checked the ISY error log and found a related entry: Fri 2023/04/07 11:56:58 PM System -5012 0 Sat 2023/04/08 01:22:36 AM System -5012 0 Sat 2023/04/08 01:23:00 AM System -5012 0 Sat 2023/04/08 01:28:28 AM System -5012 0 Sat 2023/04/08 01:39:23 AM System -5012 0 Sat 2023/04/08 01:59:52 AM System -5012 0 Sat 2023/04/08 02:00:16 AM System -5012 0 Sat 2023/04/08 02:00:37 AM System -5012 0 Sat 2023/04/08 02:01:09 AM System -5012 0 Sat 2023/04/08 02:01:21 AM System -5012 0 Sat 2023/04/08 02:01:39 AM System -5012 0 Sat 2023/04/08 02:01:54 AM System -5012 0 Sat 2023/04/08 02:02:00 AM System -5013 0 Sat 2023/04/08 03:01:51 AM System -140003 Portal-Dispatch (Time Zone is CDT, no additional error log entries in the 6 hours since) Included the -5012's and single -5013 before since they appear related. Before what's pasted here nothing appears related. (the Query All program doesn't run until 3:10 am, therefore the portal issue is unrelated to the Query All program running.) Since the portal is working, shouldn't the last message be "...is now online"?

@RGardner01 also, are you using windows or mac? it makes a difference... give us details of exactly where it's not working for you. You're telling us that you updated UI to 5.3.4. but that you can't install the admin console? the first makes you sound like you got into the admin console after upgrade, the second make it sound like you can't. Which makes us wonder if you cleared the java cache including "installed applications and applets"?

Just to update... the email to SMS/MMS gateway at Verizon is definitly NOT configured to accept 11 digit phone numbers. The other day when I was testing, all of the 11dig@vtext.com messages bounced in email, and went to my Junk folder... Bottom line... you can't email 11dig@vtext.com, the email will bounce.