larryllix

What doesn't work about it? Give more details (what does it do and doesn't do) as the logic looks good here.

@Michel Kohanim @bpwwer Battery device MS 1 device Option button, hangs IoP while Battery Write option is disabled. Trying to set an option on a newly -reinstalled Insteon MS I. Trying to use the deferred writes feature to write to the MS using the triggered write program technique. However every time I click the MS device "Options" it hangs IoP and it has to be rebooted. Restarting it on the admin console configuration page doesn't seem to do it. After I get a TCP error message box or the one below, the ISY admin console goes into a perpetual busy indication and most functions lock up. I can see some programs updating variables from the ISY internal clocks but not much else works. After 10-15 minutes the busy boxes still keep coming up. I have only installed about 20 program so far on this new environment. The only way I can get any control of my IoP v5.4.4 is to reboot the whole polisy or SSH use sudo service ISY restart Note that "sudo sevice udx restart" did not reset the problem, although when reloading ISY Launcher, the UUID address only ever shows 00:00:00:00:00:00 until ISY is restarted or power cycled. This has been repeated with the same result at least 10 times now.

I am not sure what you have to set up to enable WiFi and make a connection on a polisy but usually WiFi uses a different MAC address than a hardwired connection. You may need to set up another IP assignment on your router for the WiFi and then inject that same IP address into your finder. Sent from my SM-G781W using Tapatalk

Yeah, I guess i purchased my NR module outright and had it transferred to my polisy. Mine is not included with my ISY Portal subscription. No module information shows up in my polisy as it did in my ISY994s. I only get a response of "Modules are all up to date" now.

You may have to contact UDI. Most of my polisy lighting depends on this module. It must be an oversight when they ported ISY over to polisy and facilities to install it were forgotten. @kzborayISY portal has a different function than the NR module and cannot replace it. IIRC, the Network module is now being included with a subscription to ISY Portal though, and the lone NR Module may not be available separately anymore.

Polisy runs about 1200% times the CPU power of ISY994 and that would require a fan to make noise and wear out. This way the large metal case avoid all that, acting as a heat sink. Don't try to wash your hands of polisy now. "heat sink" is not a warm water wash station.

Do the door sensors not have an On only option like the Insteon MSes do?

ISY994 and IoP, as a copy of it, represents the longitudes backwards to any standards I have seen. Always has.

Either your comm noise that was causing the congestion went away, or your offending program stopped.

Sent from my SM-G781W using Tapatalk

I don't remember the details now but IIRC PG3 depends on some database module that is being eliminated and then new updates will remove common Linux db modules. Sent from my SM-G781W using Tapatalk

If you have been using the admin console to access your ISY994 then you have been using the java applet and your browser was never involved. However it does take a browser to download and install the java applet. You should keep your java version updated for the best results. After loaded you should clear your java cache and reinstall the ISY Finder for better access to your admin console.

I think I was inspired by this fellow's code hacks to write my NRbridge.py that I use for my MagicHome bulbs and strips. Then it disappeared from the flux websites.

This sounds like the same thing happened to me when installing the ecobee app. I installed the code into ecobee. It registered OK. I rebooted polisy and the admin console but no go. Then I deleted the app code in the ecobee app and reinstalled it and then the ecobee NS installed all the nodes into my IoP. The first time would not perform no matter what I tried to jog. @bpwwer @JimboAutomatesPerhaps something is being stubborn inside PG3 when you first install a NS. Pin code early time out on initialisation, maybe?

Years back I had a new device, right out of the box, that actually reported on and off interchanged until I factory reset it. I don't know how it could happen but it stunned me to see and retest it as such. Remember, SmartHome had n quality control at all. They practiced Quality Assurance, which means, you test it and we will replace it if it is messed up. I also had an iRLinc with a reversed wired sensor for SmartHome, right out of the box. The cost of returning the device under warranty was higher than the device was worth, so it got garbaged. It would never function properly with my ISY anyway. I also have a 2441WTH Insteon thermostat that reports changes back (confirms commands to alter parameters) to ISY but never actually changes anything inside. However I have an older firmware version that works correctly. I can't remember the third defective device but all three came directly from SmartHome on one of their sales. Then they delayed shipping for two or three weeks until they shipped the "in-stock" items via USPS to CanPost. I was so impressed I never bought from SmartHome directly again. ...always, always, always, factory reset every new device.

Did you know there are two ANDs and two ORs. Individual lines can each have their own AD/OR logic and there are also two distinct and separate AND and OR buttons that are used with parenthesis. Then you can move each bracket up and down to where you like.

That may be, but I believe it would violate the rest of the style of operation of ISY trigger logic. IMHO Consistency of trigger logic would be most important. It can get complex enough for users already. Perhaps the status vs switched logic could be applied giving users a choice. I try to avoid using the status of other programs. I find it obscure and a gotcha down the road. Sent from my SM-G781W using Tapatalk

hmmmm.. that could be LAN switch problem. IIRC Switches determine which device (IP) requests a response and only passes the packets through to the device that wants it. This would be opposed to a LAN hub that just broadcasts everything to everybody and it is up the the receiving card to only listen to it's own packets. Maybe some LAN guru knows more about whether WoL can even function through a switch. OTOH my isy was on the other side of a switch from my TVs and other devices I was turning on using WoL, just fine.

@Michel KohanimThis needs to be reported as a bug. The same thing happened during one of the version upgrades where the variables would trigger programs when the same value was written to them. (from REST commands anyway IIRC) It was corrected immediately after reporting. ISY processing logic is based on triggers of changes only for most logic.

WoL needs to be on the same subnetwork as the ip address is xx.yy.zz.255 for any device. The MAC address us what is particular. With or eithout a bridge between subnets I doubt it will ever work. Sent from my SM-G781W using Tapatalk

The nomenclature must match the positive logic and then anything is possible and good.. Many times people label things with generic labels...like "BattStat" which does not indicate either state as logic True.

I don;t know why any device that supports echoing it's own protocol cannot monitor that same protocol signal for a group device code that it belongs to. Scenes and instant group responses, without any popcorn effect, should be a natural built-in feature of any device used in a esh protocol. I can;t help but wonder this is planned as Zwave Ultra that will cause all the Zwave followers to (again) buy all new devices and dump their old devices in 2023. Marketing plan?

Nobody said it won't be free...yet. But I would have thought WoL would have been just transferred to polisy as a native piece of internal code. However, I have learned to trust UDI to do the "better thing" for ISY in the end. Having some sidetrack piece of code for the data stream, may be of some detriment to IoP's internal logic engine and better placed into a sideline stream monitor like a PG3 NS. My guess is that the majority of user never use it or even know what it does. Now we need a SoL (sleep on LAN) function to turn things off. I read in a few blogs now, about reversing the MAC address and sending it. Yeah right.

Almost all smart TVs, receivers, BlueRay Players and Ethernet smart A/V devices accept WoL without authentication. The Packet is secure enough I guess. ISY994 had a place to insert security. I never had to use authentication on my 6 devices I used WoL/ISY with. I have never needed WoL for a thermostat, mobile cell phone, or iPad yet but I would bet they accept it when needed also.

What protocol are you using? HTTPS:// or HTTP:// What port address are you using?