larryllix

For one way control you can install Network Resources to control variables, programs, scenes and devices on the other ISY box via it's REST interface. You require the IP address and the port number, and use the GET protocol style. Variable substitution can also be used inside NRs inside any part of the URL sent, so one NR can be used for many devices, if desired. You will need the NR package which can be subscribed for a very low cost per month/year. I purchased mine outright years ago and it has been the most useful tool to interface to non-Insteon devices and to my RPi software as a bridge to more WFi devices.

I just ported my NRbridge.py (MH lighting bridge software) over to polisy again (I had some infrequent problems when PG2 first came out transferred it back to my RPi again). and used "localhost:8080" for all my ISY servicing apps and they all work fine, so far. IIRC I also used "localhost:8080" on my Polyglot. I don;t know if there is any advantage to localhost. I would hope the drivers see it and circumvent some caching or other overhead.

I only have about 10-12 Aeon Energy monitoring receptacles, which are series 300 technology. I tried them a few times, forcing them to mesh (repeat anyway) and I saw no delay when operated manually from polisy manually. They actually seemed faster response than my Insteon OnOff modules, going by the sound of the clicks. I haven't actually used them as the energy reports need to be polled (washer and dryer shut-off detection) , and they would become the closest repeater point in my Zwave system. Just experimenting so far. I want to build a cleaner system and don;t want to overly pollute my polisy with poling routines.

ditto for me. The substitution of variables at send time has been a real PITA for popcorn effects on lighting items using WiFi, and probably other end devices. Imagine the appearance of a room full of blinds with individual blinds 1-2 seconds behind each other while opening. Not as impressive as simultaneous operation. I do hope this can be changed also. The polisy is much faster and should be able to do more homogeneous "scenes" using that speed. Right now the speed between successive usages of NR is very poor due to overlapping variable writes between repeated NR usages. Keep on truckin'

I f you have the PLM box still, it hides under the cardboard and most people never even knew it was there. The linked cable looks right but I couldn't say for sure and it a very expensive version from what I have seen elsewhere. Wait for others to chime in here.

The cable came with your PLM. Zwave dongles can be purchased from amazon.ca or .com. Zooz is the brand name. I bought a SiLab 7 (cheaper and reported as upgraded routinely) dongle and it works just fine.

The stop program (self) was only for trouble shooting purposes but, I found the output variables containing a -1, instead of the original 0 value. However, the same problem would apply to stopping other programs. I don't believe ISY994 Stop Program waited for an open timeslice, this way. IIRC the Stop Program was always immediate. That may be incorrect, as I never monitored or needed to test it before. Thanks.

@Michel Kohanim Found another bug in V5.3.0 Program stop does not function immediately and waits until a Wait line. GathRm.automatic.select - [ID 01D7][Parent 0004] If 'Gathering Room / PotLights over Chairs' is switched Fade Down // vocal control also Then $sGathRm.colours = $cMODE.RESET $sGathRm.colours = $cMODE.AUTOMATIC $sGathRm.whites = $cMODE.RESET $sGathRm.whites = $cMODE.AUTOMATIC // shouldn't be needed Stop program 'GathRm.automatic.select' <----- doesn't process immediately $sAutoLighting.night -= 1 $sAutoLighting.day -= 1 Wait 1 second <-------- processes STOP here. $sAutoLighting.day += 1 $sAutoLighting.night += 1 Else - No Actions - (To add one, press 'Action')

@Michel Kohanim Found another bug in polisy v5.3.0 System variable "Minutes since start of day" produces the wrong resultant. Mine seems to increment with time but appears to be based on 7:00 PM EST (EST here). eg: At 11:50 PM it produced 250. This would be 4 hr 10 minutes after 7:00 PM.

I have never had problems with bulbs if they are dimmer capable. It was always the non-dimmable types that caused me problems. I always figured the power supplies are not capable of filtering as well in a non-dimmable type. I had some problems with early Cree bulbs and Canadian Home Depot went from almost all Cree, at the beginning, to dumping them. When I return a few under warranty, the sales clerk told me they had a lot of returns on Cree bulbs until they dumped the brand. Then the sales clerk, told me to just pick one and leave the store without paperwork. Turned out the dimming curve doesn't match the other four bulbs in the chandelier. Good enough for now and I don;t notice it any more. Those four + one bulbs have worked well for the last 5-6 years now. I have a very similiar story about BR-40 bulbs from Feit, I bought at Costco years ago. When I had to buy four at a time, I had to return all four to get just one new one...but I got money back as they were now cheaper for four bulbs. Those bulbs operate at skin burning temperatures, as I found out when I returned the blinking one. Placed in a ceiling full of insulation the heat has no place to go. Burning the crap out of my hand and having to throw it onto a couch, and then run to save the leather couch from burns, surprised the heck out of me.

There are hardware buttons on the top or bottom of the MSII. I can't remember the exact functions of them but one was an enable. I have my "send off" option disabled, and program ISY to turn my lamps off. Then the On duration is set to a very short duration as it also controls the Off duration which makes the MSII non-functional until it times out. Bad design.

@Michel Kohanim Found a small bug in V5.3.0. Variable "Last Changed" time registered is incorrect from program changes but correct with manual changes. $sAutoLighting.day was edited manually to -1, then 0 and shows the correct time of the change. $sAutoLighting.night was modified by a program within the same minute and shows incorrect time. It appears to be 5 hour earlier, or still PST time? instead of EST. Refresh does not correct.

As you quoted, yes. Just click on them and save them. This can also be done placing the cursor anywhere on the parameters and hit <enter> I use about 35 WiFi bulbs that all live on 4 NRs, total. I make usage of the variable substitution to control them individually and in groups / scenes.

For my NRs, I just loaded each one, individually, and then saved them again, as if I have done an edit. It seems they were not hooked into the main engine somehow and re-saving them did so.

I find mine in various places. One of the most obscure spots is I think Windows grabs it and installs it under ISY in your Win 10 start menu. I hate "we did you a favour" stuff.

I was hoping there would be some movement on caching variable substitution values simultaneously so that old values do not get used for following NR invoked with new variable values. My quick testing showed multiple sends with old values when quick sends are done without 2-3 seconds between each. This feature would be nice to eliminate some popcorn effects with shared NRs between multiple devices. eg: send NR MagicHome.setLevels set NRb.rgb = $cHUE.RED <----- values all changed using variable substitutions set NRb.RGBlevel = 100 set NRb.WWlevel = 0 send NR MagicHome.setLevels <-------- same NR used for dozens of devices sends the old values twice instead of the new values. RED, 100%, 0% Caching the variable substitutions at the same time as the NR invocation would resolve this, eliminating many NRs for each device, and eliminate many popcorn lighting effects. Any progress with this? Thanks!

Thanks. I never need to shut the dryer off (finished monitoring only) but I need both for the washing machine (finish notification, and water leak detection shutoff). I see this unit is a 500 series. Is there much difference between a 500 and 700 series? These would be the first repeater points out of my polisy SiLab 700 dongle so I want a decent repeater function also.

I found the same version mismatch after clearing cache etc. Despite java cache clearing the version mismatch wouldn't go away. It would automatically close each time giving no ISY access. I found my polyglot not connecting and needing new credentials. Maybe I didn't wait long enough for ISY to reboot properly yet, but I still after a few minutes I received all my rebooted notifications via SMS and email, so ISY was running. after many retries and java cache clearing I tried SSH into polisy and... sudo reboot then after about 6-8 minutes, all was well again and all connected again. How do I load the ISY Launcher? All I can ever get is the ISY Finder and the polisy Administrative Console (Which is also the ISY Finder??) after the java cache clear deletes the ISY Launcher app.

Thanx Asbril! I don't think I want a "smart receptacle" depending on how you define the "smart". I want a load monitoring receptacle to monitor when the washer or dryer has stopped that automatically updates ISY with the load amount, or detected load (on/Off status, only like a SynchroLinc does. When you posted "smart like X10" I think of a receptacle or plug-in that can detect the lamp switch and turn on the receptacle or X10 device automatically. The automatic turn on is not wanted, in my case.

Lack of devices (connectors, cables, routers, switches, power supplies) between your NSs and ISY programs.

aartech.ca = No ETA

This sounds like, and logically makes sense, that using a 300 series devices would be typically OK as the 700 series devices would repeat it at higher speeds. (IOW: at the far outreaches of the mesh might be OK) Is there any docs that can confirm and explain this further? On a side topic: I am looking for a 700 series receptacle that can repeat signals well (would be closest to my SiLabs Zwave dongle) and also send load information back to polisy for washer and dryer finish detection. Any suggestions? I am not sure where to start.

@brians BTW: To ping another person you need to use the @ and their name, but also select their name from the falldown menu, or it is just plain text with no ping. The result should be a reverse video font, as shown above.

To put it another way: Program timers are retriggerable and each heartbeat received retriggers the Wait 25 hours timer so the notification line never executes. I add a loop on my heartbeat watchdog programs at the bottom, so they test again in 25 hours. My notification states that it may be a low battery or just a missed signal so as not to cause any panic. My LD under my dishwasher has missed heartbeats about once per year. If I never get the second one, I just ignore it. BTW: Most use two lines to trigger If heartbeat is switched ON OR heartbeat is switched OFF Some LDs (maybe all?) send alternating signals every 24 hours.

Awesome! I am sitting about the same spot as you are Zwave wise. Although, I have a dozen Zwave inline power plugs that I inherited in another deal but I believe they are all series 300 devices. I am not sure how I would tell except they require polling to access load information. May become useless for me as I don;t want to develop so many ISY programs to keep the protocol traffic limited to critical times abased on who knows what for triggers. When did a daughter board ever become a "dongle"? I always thought part of that portmanteau word was "dangle" meaning it hung off the back of a USB port, or cable., outside of the main device.