Teken

That makes perfect sense to me. I have like you been running each Beta since launch so gather when UDI makes a release official. There is no flag being declared on the Admin Console since we are all on the latest release. In the last several years I can honesty say I have never been using a older version of firmware. This is the first time I have not jumped into the next cycle because of long term Alpha testing for the Energy Module. I will see what UDI has to say about this 4.2.30 release and if it includes the Energy Monitoring patch I have been testing.

Really?? This has never appeared on my console in any release I have used, ever. Not sure why its working now but happy to see this in place. Its always the small things like this that impress me about the ISY and what UDI brings to the product.

Today I logged into the Admin Console like I do everyday. Upon launching the Admin Console I was presented with a new version 4.2.30 is now available? I think its quite awesome this small feature has been implemented but would like to know when this started? Also, I would like to know if 4.2.30 has the energy patch which I am Alpha testing at the moment?

Randy, Very sad to read you didn't make the cut. Having someone on the inside who knows what the ISY membership wants in terms of integration was really key for me. [emoji22][emoji35] Let's see how others fair and help shape the development of this product. I really wish UDI would have been tapped directly by Amazon to participate in this process. Oh well let's see where this goes. Ideals are peaceful - History is violent

Hello Simon, It's been awhile and am very happy you were able to make this work, finally! [emoji1] My first guess is the fact the SL is not dual band. Next are you sure your Insteon network is properly coupled / bridged as confirmed by the 4 tap (beacon) test outlined by the 2413S PLM user guide. Next, more than likely the gear your controlling is a noise maker / signal sucker. So some of this gear may be impacting the SL and the COM's. A filter linc may be in order here. You could simply write a program that query the SL at set intervals so you know it's current state as a work around. Those are my thoughts for today. [emoji5]️ Ideals are peaceful - History is violent

Hello Jerry, Is the PLM near the two year mark? If so its more than likely its internal capacitors have failed. There is a link where some great folks have provided the specified parts and values needed to bring your unit back to life. If the unit is within the two year mark engage Smarthome as they will assist you in the RMA process for a replacement unit. If the unit is out of warranty you can definitely follow the capacitor replacement procedure. Original thread is listed here: http://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/

Mattc, You Sir, are a beautiful human being! I thank you from the bottom of my heart for taking the time to share this quick fix and work around. Thank You

In the Insteon world when a device is programmed to be a controller it by default makes it also a responder.

As always I thank you! [emoji1] Ideals are peaceful - History is violent

Glad you got all sorted out.

It would be best if you created a service request to UDI to facilitate a solution in this regard.

Hello Davonavo, The first link does not download a file to your computer system? If it does all you need to do is click on the down load and the application will launch. Once it finds your ISY Series Controller it will than automatically launch the Admin Console.

This thread has lots of useful information pertaining to the topic at hand: http://forum.universal-devices.com/topic/15043-wiring-a-load-to-be-permanently-on/

I would have to gather this will be like the heart beat node appearing in the Open / Close sensor as it never had it before. More than likely UDI will once again have to reach out to someone at Smartlabs and determine what *Magic* needs to be added into the next firmware release to take advantage of this new firmware feature. As I have stated many times here and abroad in other forums. Smartlabs inability to take just a small amount of time and communicate to their internal staff never mind to the general public. Is truly astounding and continue to show the piss poor consideration for the consumer! This is 2015 and they have half a dozen methods to inform and update the consumer and their tech support. Yet at every turn they fall miserably on their face and let the general public beta test yet another new *feature* You know the phrase STUPID is not lightly used when addressing someone. But, in this case after 10 freaking years Smarthome / Smartlabs truly embodies STUPID on all levels of communication and deployment.

[emoji5]️[emoji4] Ideals are peaceful - History is violent

OK, something here simply does not track. I have been following this thread with great interest and just moments ago everything was accessible perfectly fine via the HAD interface. Meaning when I was in the HAD interface when selecting the Admin tab like I normally do. Upon selecting the *Admin Console* tab it then showed the broken link and that the plugin was no longer supported WTF??? This issue was seen after selecting the link provided by Michel in the docked thread located here: http://forum.universal-devices.com/topic/15885-chrome-and-isys-admin-console/ Selecting option one which down loads the link from the UDI server and places it on your desktop is directly related to the web browser showing this plugin is not supported??? Can someone explain to me what can be done to restore the previous access?? I like Shannong would prefer not to have the finder floating around even though I have three ISY Series Controllers in production.

I was thinking about something else when you initially replied. Assuming we are talking about the same thing lets be clear. 1. In the device tree on the left if a device has multi nodes. To have them all under one level simply right click and select group. 2. If we are talking about a folder where there are many individual folders. To place it (with in the folder) simply drag & drop it to the top level (parent / child) folder.

Are you sure you didn't group them? Ideals are peaceful - History is violent

Does it still have the two screw terminals for external sensor use?

The 6 VDC will be fine as I recall the ISY has a huge voltage range of approx 30 VDC.

If you use another (older) link for a previous Beta firmware this too can cause untold issues. The UI / Firmware in the *About* in all cases should match and be identical. This single conflict has in the past resolved many random issues not explainable. If you're in doubt and the *About* still indicates a conflict with what you actually have. I would humbly suggest you perform the upgrade again and than clear the java cache including all check box's. At that time you will use the most current link that is associated to that firmware release to access the Admin Console.

Hello Don, This may not resolve the slow loading times but I did notice your firmware and UI levels were not the same. Please clear the Java cache and select all check box's while doing so. Often times strange behavior is attributed to this one conflict. Ideals are peaceful - History is violent

If the device is set for night only mode there should be very little traffic coming from the MS. If you didn't set it to night only mode this is expected. Its also very dependant upon the location, install, and FOV. Keep in mind IR sensors are prone to false readings due to extreme temperature changes, wind, and reflected light. You will need to determine the above first and follow up with a solution that meets your needs. There are settings to reduce the level of sensitivity the MS will detect. If that is not enough you can always use a old school trick and place a piece of card board of various thickness to reduce the FOV. Keep in mind the Insteon sensor is by no stretch of the imagination a true motion sensor. You wan't high reliability and less false alerts than you need to purchase the real thing.

I took Don's reply that he upgraded the Java application six months ago. But, I can see how it could be taken as he is running Java v6.

Just in case no one has said: Thank You for sharing this work!