MrBill

@blueman2 is the controller for those devices an Insteon Wireless device? If so, you may need to put the device into programming mode and let instructions that are currently in queue be written, after which new won't accumulate. If not, ignore this.

Wow, I wonder what got in there. or if a capacitor exploded? good you found the problem!

Today was my day for SD card failure. I started to notice odd things over the weekend and wondered again if it was time, but didn't have time to work on that. This morning the admin console failed to open, then opened with a lib-403 error with no programs showing in the program tree. I thought I'd come back and post some more info, while I still can't definitively answer @hart2hart's question about using a win32 imager the answer is probably not, but more importantly I wouldn't bother, It's also not hard or time consuming to do it as UDI suggests in the wiki. 1) replace card, 2) load ISY firmware, 3) restore backup. I will note however that there are many things about the process that are unclear. The Wiki page indicates suggests the maximum size SD card compatible is 16gb. In another recent thread another user stated that 32gb cards are compatible. However, no matter what size the card is the ISY only uses a portion of it. Which is the exact reason I think you might get in trouble using a 3rd party imager. Another BIG problem for those planning ahead, is way back last JUNE, I decided I should have another memory card on hand. I opened the Wiki and placed an amazon order for what the wiki called for a "16gb SD card". The wiki however is missing an important word micro as in microSD card. So in June I ordered an SD card, never opened the package, plopped it down near the ISY only to discover today I needed a microSD card. The funny part is I actually knew that what was in the ISY was a microSD card because I cleaned the contacts when I changed the Z-wave board.... all the while the full size SD card still in it's package was staring me in the face!??? (for those that want the rest of the story, awhile back I bought a second ISY for messing around. testing etc... I stole the microSD card from that unit and ordered a 3-pack of 16gb cards that will be here tomorrow. Main ISY had a factory installed 4gb card, second ISY had an 8gb card that still claims it's size as 3956MB when it's in the ISY.) If preventative changing the microSD card I think the best bet is to just follow the SIMPLE process outlined. 1) Backup, 2) Pop the new card in, 2) load the firmware and 3) restore a backup... the entire process was painless and doesn't introduce incompatibilities possibly created by 3rd party software.

If you have a 500 series board yes, by all means where you should end up is v5.3.2 BUT Don't do that until you get the root cause of your z-wave problem. it should be working in 5.0.16C just fine.... if it's not upgrading again could just add to your problems. Like others have suggested since your post quoted above, I would open a ticket with udi by emailing support@universal-devices.com and/or try a different power supply. The ISY accepts a wide variety of power supplies, from the wiki: You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector.

@jacmathYou must use the two program approach that @oberkc suggests. If the single program that you suggest in the first post is used the lights will also turn on for 30 minutes at sunset if you are home at that time. The two program approach says "if the first then happens, then run a second program and check some more conditions."

Was the ISY recently rebooted? If you open the node in the admin console does it show the status as ON/Off, Open/close or is the status box blank? which indicates the ISY doesn't know the status, if this is the case try to open and close the door and then ask again. If that's not helpful then please tell us what hardware the front door sensor is.... there are lots of choices from Insteon door sensors to z-wave locks to ELK Alarm sensors, etc etc....

the confusing issue is the disabled (grayed out) DST box on the screen before ? that exists because it used to be different before they changed to the current timezone library.

Log into the ISY Portal and click the "My Profile" tab in the upper right hand corner of the screen. Check which is your "preferred" ISY, and how the dialog box below that is set.

Have you tried selecting the device in the device dropdown? Fortunately the mini-remotes are all near the top of the list.

I have a handful of those, they do add. I suspect @lilyoyo nailed your issue. You do have the switch on as well? blinking green LED when you try to link?

1) You may already know this but, close the admin console when your not using it, it's not meant to be a 24/7 system monitor. Anytime something doesn't make sense to me the first thing i do is close the admin console and re-open it. 2) A good exercise to help troubleshoot your counts being off is to click on "my programs" at the top of the program tree, then right click and choose "Find/Replace" use Find to "step-thru" all uses of your variable $S.FH.Zone.Count and just step thru each place it's used to see if you've accidentally done something like used = where you meant += or -= or used += or -= in both then Then and Else of some program. I find it helps to step through each usage of the variable using that method rather than clicking between programs staring at each one. You might also find an entirely unrelated program where you accidentally selected the wrong variable. Another trick you can use to "log" every time a state variable changes for debugging is to create a temporary program using a condition that will always be true and then either email the change or send it to pushover. the program below will run THEN each time the count changes. If $S.FH.Zone.Count > -9999 then Resource send_count If you create a second application token at pushover to use with this program only the app will organize these all together in a separate folder. Of course send the value of the variable. You could also include not only the value of the variable but have separate lines with the state of each node that changes it.

The reason for all those questions is because the Z-wave dongle had a hardware change. V5.0.16C is the final version that works with the original 300 series board. The newer 500 series board is required for ISY firmware versions beyond 5.0.16C. So this puts you in the category of "it seems like you shouldn't be having this problem". Since you stated "I cannot check my Z-wave version because nothing happens when I click on "Z-Wave Dongle not responding" I think you should open a ticket with UDI support, you can do that by emailing support@universal-devices.com For what its worth: had the Z-wave | Z-wave version check worked.... Series 300 board reply version 4.55.00, series 500 boards reply with version 6.81.00. Another way to identify a 300 series board is to look at the back of your ISY, if you see a round circle next to Port A then shine your phones flashlight at that and see if it's really a blue LED (assuming the blue LED not lit up which of course makes it obvious)...If you have a blue LED next to port A then that is a series 300 board.

@jblackst5000 What version of ISY 5.0 firmware are you using? (Help | About) Does the UI version match? What version is reported when you select Z-Wave | Z-wave version? Did you also upgrade the ISY's firmware at any point during the PLM change?

Same here.... I was skipping this sub-forum and only scanning it every few days because i don't own anything android and I wasn't expecting an iOS announcement, by the time I found the post it was already full. I hope new slots open soon, making sure to check the new posts here everyday again.

It's not intuitive, but after changing the setting you must push the button to the left. Are you doing that?

Disclaimer: I've not tried nor tested, just located the option. I'm using V5.x firmware, if you're still using V4 Firmware, YMMV On the configuration tab in the clock box click change location. Choose one of the Brazil Locations, all of which state Daylight Saving Rule is OFF, or use a custom location and set the Daylight Saving Rule dropdown to OFF (located at the TOP of the list.)

@IT Solutions I can only say... I don't have ELK, so I can't comment on how ELK interacts within the IF statement, I do know how ISY works tho and I'd find it unusual that the 3 right click run don't behave as expected unless a folder condition was turning them off.

After I read that sentence a second time, it made me wonder about Folder Conditions... If the folder the program is in or ANY FOLDER ABOVE IT is False, Right click Run, Run Then or Run Else will be prevented. That's about the only way for a right click Run, Run Then or Run Else to not run.

I can't get mine to behave the way you're saying. Specifically i used this Program to Test: AA TEST - [ID 0103][Parent 0001] If Program 'AAA TEST' is True Then $stemp_test += 1 Else $stemp_test += 1000 When I started AAA TEST was false. Clicking this programs Run Then and Run Else from the RIght click context menu changed the color of the left bar on the icon every time. then I changed the value of AAA TEST to true and repeated alternating Run Then and Run Else, every time I did so it worked as expected changing the color of the left bar. Then I disabled the program above and continued to test... still not seeing the observations you are reporting. What is the content of the IF statement of the program that you don't think is changing? Perhaps its being re-evaluated immediately? I also just tried it with a schedule 8:00AM to 5:00PM and then clicked run Else and the band as expected turned red, even tho the schedule is still true. (Because the IF portion of a simple schedule is only evaluated AT 8:00 and AT 5:00PM and NOT constantly between those times.

I should add that you can use that program state, True or False in the IF statement of another program. If you have a program that should always be True or always be False or be True or False at a certain time, or certain time period, or maybe if variable $Test = 1 AND Program XYZ is False.... then..... else and so on...... Caveat: Watch out for Programs with identical names for example i have 8 or 12 programs all with the name "Alexa.on" but in different folder.... the If Program 'Alexa.on" is True phrase won't work. It Finds the first instance, not necessarily the instance you meant.

They show the state of the program, True or False... another way of thinking about it is which ran last Then or Else... very much similar to the full green or red folder, except they have already finished everything they will do until triggered again. Also means "Running" specifically running ELSE, whereas the all green version in your example is Running THEN.

It's been awhile since I was on V4, but it seems like V4.x to V4.y there's a prompt at the top of the admin console window that says firmware update available--And then clicking that or, something on help would download the file and upgrade automatically. I could be wrong it's been awhile and I don't see a page in the wiki showing that. Upgrading 4 to 5 or 5 to 5, you definitely must download the file and use the "manual upgrade" option on the Admin Consoles Help menu.

I initially read the bolded sentence below to mean the PLM wasn't being found, especially with the first sentence. However before I even his post I wondered if this was about finder not finding.... so I added the OR... The leased devices from Comcast are all-in-one Modem/Router/Wifi access points. The only case it could be a modem only is if its Customer owned modem, but if you've reached the point of buying a stand alone modem then you likely know you need a router too.

Oh and I forgot to comment on that statement. It is hard to find electricians that will touch an Insteon system. They don't have a clue, and the learning curve is high. My wife previously owned a high end lighting store. We actually stocked X10 for the DIYer's. X10 was much easier to understand, put this on B1 and this on B1 and they will (maybe) talk to each other, Insteon has to be linked and in simple 1:1 relationships its only difficult to do manually.... it more complex relationships you have to understand the ISY.