MrBill

update to 5.3.4, one of the updates after 5.3.0 deals with mail server issues. Also if it still fails after the update check the error log and it might get more specific

@CPrince If you don't get it up and running easily just open a ticket support@universal-devices.com Michel will get you online quicker and without a lot of guessing.

In a programmers world, 0 typically means the negative... i.e. off, closed, false; on the other hand 1 means on, open, true. The program will only remember the last state. If it was 1 when the ISY restarted it will still be 1 when restart is complete-- even if someone closed the door while the ISY was off. The variable values give you the ability to know the last known state, but if that changed while the ISY wasn't paying attention the ISY won't know it changed. The good news is you eventually reach a point that you don't have to reboot too often, for example mine currently hasn't been rebooted in 184 days, which is about 6 months. Did you find the door sensor under "Control"? it would be there.

the UD website has a long term bug, that it looks like they've been working on, but haven't quite gotten correct yet. Click purchase modules and when you get the the page with the 404 click the My account button: then click: and follow the prompts to login. you should then end up in a page that has this in the middle of the left side: click My products, and then the Modules button next to the correct ISY. You can also email support@universal-devices.com and ask them to transfer your purchase from one ISY to the other, include both the old and new UUID's.

this is exactly what happens and yes an incandescent bulb on the side of the line that float higher will flicker brighter. been there, done that. seen it first in my parents house when I was a teen. Seen it in customers houses repeatedly...

What happens when service neutral drops completely? I don't know how it works in Canada, but in the US Neutral is center tapped, one side of the line goes high and the other side goes low with respect to ground based on the amount of 240 volt loads present. When in the connection is intermittent (flickering) and flickering brighter it means the voltage has increased.

it should.... try restarting the admin console. and/or just realize those lists sometimes alphabetize weirdly.

Read it again Larry.... The incandescent bulb is a 120V load, it it flickers BRIGHTER when a 240V load is turned on then the problem is the service neutral.

@landolfi One idea is presented by@kclenden just above, another is to use "Control" rather than "Status" in your program. Control doesn't look at the status as known by the ISY, but instead fires the program based on Events. If 'test door.1 - Door Open' is switched On Then ---- do whatever------------ Else - No Actions - (To add one, press 'Action') In this case Else will never run. A second program could be used for "switched Off" actions. --or-- This construct will make the "switched on" and "switched off" behave similar to "Status", but without the unknown problems you're experiencing: If 'test door.1 - Door Open' is switched On And 'test door.1 - Door Open' is not switched Off Then Set 'LR Lamp 1' On Else Set 'LR Lamp 1' Off In this case Then will run when the door open signal is received and Else will run when the door closed signal is received.

Just call them and tell them you have flickering lights. It's a routine call for them. They will check the connection at the pole and meter, and likely come to do that within a few hours of your call. Its common that a loose connection will cause an unsteady high resistance arcing connection that causes lights to flicker. If an incandescent bulb is flickering brighter when a 240v load such as an electric oven or air conditioning compressor kicks on it's an indication that the above described issue is occurring on the service neutral which is more problematic and needs to be dealt with before it ultimately burns open.

Some LEDs.. mostly cheap LEDs show the problem better. I diagnosed a power company issue at someone else's house and the only bulb flickering was the incandescent bulb in the furnace closet. I looked at a couple of their LED bulbs and the stamped input voltage was 100-240v.

The notification Node server is no slower. Technically it probably is since there's another process involved, but it's not measurable in human reaction time, it only milliseconds. Did you configure the notification Node server then restart it, then restart the admin console? I suppose it is a little bit trickier to get going from ground zero.

This doesn't make sense. If you push this button: in the IoP admin console there is no feedback provided about the number of packages installed. When this button is pressed, the admin console immediately closes. The only feedback mechanism is a series of beeps that means it was successful or complete. Bottom line, if you can make a detailed statement such as "all went well and the 14 packages that pkg noted as needing to be updated were install successfully this time;" thhen you are not updating by pressing the 'admin console-upgrade-packages-button'. Clarification needed.

It works great!

as pointed out by @larryllix I typo'd the numeric operator, but to add to what he said let's take a second look, I've empathized where the motion count goes up and down. So the first program counts motion the second program handles the actually switching, and the third program expires the motion. Program MotionSense If Motion is switched on And $iMotionCount < 5 then $iMotionCount += 1 Run Program MotionLightExpireMotion (if) Run Program MotionLightOn else (none) Program MotionLightON If $iMotionCount = 5 then turn light on else (none) Program MotionLightExpireMotion If $iMotionCount > 0 then wait 10 seconds $iMotionCount -= 1 Run Program MotionLightExpireMotion else Turn Light Off

As @hart2hart mentions there is a factory program that runs at 3:00am that does a system query. The bigger question tho is why does the query program cause things to happen that shouldn't. The first experiment that I would try is to disable the switch that makes the noise you can hear, it may be creating noise on the electrical line also. Most switches can be disabled by pulling the set button at the bottom of the paddle out. If you want to test this during the daytime, find the program in your program tree, most likely named "Query All". The IF statement will be "Time is 3:00am" and the THEN will be "Set ISY Query". You can manually make the query occur by Right Clicking the program name and choosing "Run Then" from the context menu. So try disabling the switch, and then manually running the Query All, and let us know what happens.

yes. technically it requires polyglot 2 or 3. If you don't have yet you can used Network Resources without too much issue, I only lost 1 out of every 500 messages, and that attributable to the crappy cable connection my house has. If you have a better internet connection you don't need to worry.

There are numerous methods to get a message from ISY to Pushover. As you've discovered one method is email. I don't recommend it because there's a middleman or two. Second as @Geddy mentions direct from Network Resources. Probably the fastest, but with a catch-- Network resources is a simple interface that only tries to post the message once. Either the message gets through to Pushover, or it fails and there's an error log entry instead. No retries. Personally my house sits at the end of a long rural lateral with internet provided by giant-philadelphia-cable company and sometime the packets just get lost. It doesn't happen often but it occurs often enough that I knew messages were missing. (at one time I sent every message via 3 methods figuring at least one would arrive.) If a user was using the internet they would just reload the page and never give it another thought, with a critical message that doesn't get sent, it's a whole nuther matter. @Jimbo.Automates created the Notification node server which will also push messages to Pushover. The notification node server has so many message send options it's difficult to document. The key thing tho is that the Notification node server will retry! Certain http errors or failure to return "200 Ok" when the message is sent will cause the Notification node server to keep trying. Just be sure to have an ISY program the monitors the node servers heartbeat and sends notification via other methods if/when the node server dies. This is the program I used to monitor the node server itself, the notification is via a Network Resource directly from ISY to Pushover with the node server in the middle: hb.controller - [ID 0028][Parent 016D] If 'Node Servers / Notification Controller' is switched On Or 'Node Servers / Notification Controller' is switched Off Then Wait 11 minutes Repeat Every 30 minutes Resource 'ISYnotification.NotificationNS.Missed Heartbeat' Else - No Actions - (To add one, press 'Action') the "repeat" loop will end when the node server again sends it heartbeat.

Its very hard to get an accurate link count on a large system with multiple battery powered AND/OR motion sensors. Yet continually the instruction is given to check link count with no regard to that.

i think you're too late he already solved his problem. Also not that he is using an ISY99 and correctly found the link for the ISY99 admin console..

Also it should be noted that ANY Insteon traffic during a link count will throw the link count off. People seems to give the command "DO A LINK COUNT" without mentioning this. This means No switch flips, no motion and no battery device heartbeats can occur during the link count. If any traffic occurs the pointer will move to whatever that address is in the order and the link count can be very high or very low as a result. If any battery devices exist in the system, you almost need to do multiple link counts until the same number occurs twice or you determine there is a hardware fault. The advice to "Do a link count" is not valid without understanding how link counts work and why they might be invalid.

That depends. There are two versions of the leak sensor (I'm lucky enough to have some of each) One version clears itself as soon as it's dry or picked up. The other version stays "wet" until the contacts are out of water AND you have pressed the button once.

You should be able to uncheck the box "Migrate ISY Portal License" and everything else should migrate fine. I haven't done it yet tho.....

Create a integer variable and use several programs, such as: Program MotionSense If Motion is switched on And $iMotionCount < 5 then $iMotionCount += 1 Run Program MotionLightExpireMotion (if) Run Program MotionLightOn else (none) Program MotionLightON If $iMotionCount = 5 then turn light on else (none) Program MotionLightExpireMotion If $iMotionCount > 0 then wait 10 seconds $iMotionCount -= 1 Run Program MotionLightExpireMotion else Turn Light Off Disclaimer: I don't have an ELK M1 and don't know how often motions can retrigger. The wait and motion count above also may need adjustment based on that answer and personal preference. When I started writing this example I assumed it would use a State variable rather than an integer variable, but the solution is much more complicated using a state variable. Since the 2nd and 3rd programs only have an integer variable in the If statement they will never run unless called by another program. The first program is triggered on motion and only continues to accumulate the value if the motion value is less that 5. Since the second and third program won't run on their own, it runs them. The second program has one job only when the motion count gets to 5 it turns the light on. the third program expires motion and anytime the value reaches 0 turns the light off (it may not be on but this minor inefficiency shouldn't cause problems, a fourth program could be used to turn off the light when the variable returns to 0 but it would need to be run from the else that currently turns the light off.)

there are users that are paying twice. I'll be in the same boat if I choose to migrate. I'm paying both ISY and Polisy portal licenses. The second sentence of OP's original post establishes that he is also paying for both: