larryllix

Geeez! I posted 4 times in this thread and none ever showed up later. I am trying this with Edge this time. Possibly the forum is developing FF problems as other forums are experiencing. Anyway... Thank you io_guy! I have been reading from the links you provided and have found no actual method to install the update to my SiLab stick yet. Lots of mention about using Win PC or RPi to do this but no actual method. I do not understand what a PC Controller or OTW (from your post) means. Can you elaborate more on a method using either hardware?

With the secure https://xx.yy.zz:8443 you must use the port number extension on the URL With the non-secure http://xx.yy.zz:8080 you must use this port number extension on the URL

The point I was trying to make is why the user has been gifted to use a pulldown menu to turn a Zwave device on and off, and also dozens of pulldown menus (with user friendly labels) to control an LED on the side that nobody will ever use. Then when it comes to setting the basic operational parameters needed to make the device work, the user has to consult an engineering guide specification sheet and find the correct hexadecimal parameter number. The menu driven selection was totally up to the programmer to select decent usable parameters in the ISY that most users will use. I may never turn these receptacles on or off once set but those menus will still clutter up the ISY admin console with useless (to me) menus, status pages, and hundreds of settings. Here are the webpages involved but still avoid the user friendly parameter setting to actually make the pages function. Do we really need a few dozen parameters to control the LED on the side of the receptacle while the basic threshold setting to enable/disable the metering is hidden in an engineering pamphlet, stated in Hexadecimal? I mean I grew up on tech bulletins, but a good majority of users will never make the thing run as the purchased it.

I agree with the user database and made that suggestion a few years ago, also. However, if the same thing was applied to a Zwave thermostat, the parameter selections done in binary would entail hundred, maybe thousands of fields. People wouldn't love to look up parameter field numbers everytime they wanted to set the HVAC setpoint. Meanwhile dozens and dozens of field parameter were assigned to predefined fields with predefined pulldown menu selections for the colour RGBW, including the ramping speed of the LED, the sequencing times for flashing, and effects, for the little LED on the side of the receptacle, which nobody will ever see and only possibly for troubleshooting technical people. This is how to get non-tech users to run away from ISY and surely must be a mistake somehow.

I am not sure this is only Zwave things. I am a newbie to this realm also but the GUI for this device is only half baked. Cripes we don't have to insert hexadecimal field numbers for any Insteon devices and I know they don't talk in English names fields. Why would UDI leave these devices at the low level a hexadecimal programmer level. This will turn users off and get them to go elsewhere. I just figured the time was early but if all Zwave devics are left for the user to research technical manuals to find the necessary hexadecimal field numbers, ISY will be dead in a year or two. I mean really? How many users will use lines like this to turn on the reporting of the basic metering? Set 'WashMach Switch' Set Configuration Parameter 0x1B = 0 ...and then they must know the bit length of the parameter field to communicate properly. How many ISY users will understand what "unsigned binary" or 0x1B means in order to use a Smart Receptacle? Am I missing something here? Was my response from @Michel Kohanim confused somehow? If this is a temporary solution for so many Zwave devices, without studying every engineering manual (a daunting task), will there come a time where knowledgeable users can submit real names for fields on Zwave devices for ISY users that are even afraid of using variables, because they are "too complicated"?

I assumed the basic parameters to make them function would have been incorporated into the GUI and not 2-3 duplicates of everything, including detailed pulldown menus that control a coloured LED on the side of the box, nobody will ever see.

When you turn on a group of lights they show a sequence of them turning on a different times. This can be very annoying. Insteon scenes can make lights synchronized looking whereas many other protocols cannot do this. I use MagicHome protocol bulbs and strips and external software can make them appear more simultaneous.

Yeah, I have a lot of WiFi RGBWW strips and bulbs now. They don't report status back to ISY (using my bridge software) though but I don't see a lot of usage for the confirmation, most of the time and I can do groupings of bulbs, without the ISY popcorn effects.

Most/many use the RGB+++ controllers for LED lighting strips. They dim right down to 1% without any flicker and work on various protocols (WiFi, Zwave, Hue, ZigBee, BlueTooth etc..). Some are dual protocols and compatible with similar RGB+++ bulbs. (Same software drivers and techniques).

Thanks! I thought the Zwave devices GUI would be more polished at this point. This is a PITA sooooo... Looks like the answer is more ISY constants, unless UDI is going to make more detailed parameter descriptions but I assume it is different for every brand and model anyway. We need a admin constant variable pocket with another pulldown menu for variable selection separate from constants please......... (I have over 500 variables now that make ISY living much easier.. ) For those of you not variphobic, here is the ISY variable constant technique I use, to avoid not having to find and review technical docs every time I want to edit a program. Note: The ending "1B" and "2B" specifies the length of the parameter field required. These parameters have not been tested to this point yet. Washer Sensitize - [ID 0122][Parent 0066] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then // Set internal check time Set 'WashMach Switch' Set Configuration Parameter '$cPARM.CHECK.TIME_1B' = 5 // Set Watts & Amps threshold=0, update time=30s Set 'WashMach Switch' Set Configuration Parameter '$cPARM.WATT.THRESHOLD_2B' = 0 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.WATTS.TIME_2B' = 30 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.AMPS.THRESHOLD_1B' = 5 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.AMPS.TIME_2B' = 0 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.VOLTS.TIME_2B' = 0 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.KWH.TIME_2B' = 0 Set 'WashMach Switch' Set Configuration Parameter '$cPARM.KWH.THRESHOLD_2B' = 0 Set 'WashMach Switch' Write Changes // Wait 10 minutes Run Program 'Washer Desensitize' (If) Else - No Actions - (To add one, press 'Action')

Other than the options indicated in my post above screenshot , I can't find any mention of any such option. Is there some particular place to look for this option? The Smart Switch 6 receptacle cannot be recognised by ISY v5.3.0p, at all. I wonder if I have a defective receptacle that cannot introduce itself? I have tried the single click as well as the double click with both ISY's Find and Remove Zwave devices and no response is ever seen in the admin console. ENERGY METERING UPDATE Looks like I have to set parameters by parm numbers. Is this a preliminary setup? This is very user unfriendly. Will parm field names be coming later? It appears I need to set thresholds and update times manually, more sensitive and faster when expected usage is happening, and then slow things down when not (to avoid data storms on ISY). It appears energy monitoring is expected to be a low priority mission in the Smart Switch 7 with lack of intelligent updating. Smart Switch 6 is still ignored by ISY still.

Perhaps the SiLabs Seres 700 dongle is causing me incompatibilities with polISY v5.3.0? Anybody else tried these Aeotec Energy Monitor receptacles with their ISY? Do they ever report the energy status or do they have to be polled?

I have two Zwave devices, both Aeotec Smart Switch 6 and Smart Switch 7, receptacles. The Smart Switch 7 receptacle connects to ISY but I cannot get it to self update the energy monitor. This is the same as the 12 series 3 receptacles I have. No those are not in my system right now, and do not exist in polISY. The only way to update the energy monitor is to poll the device. The Smart Switch 6 receptacle cannot be found with polISY at all. The information on both devices is very sketchy but the user guide tells how to connect with security and without. I have tried both. The active and included Smart Switch 7 device is about 4 feet from the series 6 device. One other thing. WTF are all these nodes and duplicate nodes doing in ISY??? This appears like some device that is not fully developed in ISY yet. Looks like a mess. Any tips to what is going on with these devices? Do any Zwave devices self update ISY or do they all have to be polled for secondary nodes?? If that is true I could have stuck with much cheaper series 3 devices?

Do you have your ISY set to use DHCP for a self assigned IP address from your router? Do you have your router's DHCP reservation table set to permanently assign your ISY's IP address at a fixed address, based on it's MAC address? If No to either, you may have conflicting IP addresses on your LAN and this can cause one, two, many ot all LAN devices to not respond or be intermittent. Hey, as an aside: do you want any Quindar SCADA RTU boards?

AWesome! Glad you got it working. However there are few instructional posts in your thread here, you should read and try to help yourself in the future, including upgrading to a less buggy version of ISY, and how to copy and paste your program in your posts for best readability. It makes it much easier for people to help you with your programs.

No. You wouldn't have to pay twice but it is always possible your ISY dropped the permission to use and UDI could renew it. Sent from my SM-G781W using Tapatalk

NRs can be a subscription paid service. Have yours expired? Maybe contact UDI with your UUID and check to see if the account is enabled correctly.

Change your Themes|Fonts setting to something other than 13. This is a bug in the GUI where some programming selection is based on a screen or box size. Doing some programming myself. this is a very hard thing to line up for some font sizes or styles. The boxes end up being too small for the number of characters needed and show '...'.. You may also try changing your Windows screen magnification back to 100% but that may make things really hard to see for you. You can try changing your Windows mag setting to 100% while the admin console is running, temporarily to prove it for yourself. Oh yeah....if you are running a ISY994 then upgrade to v5.3.4. They fixed a lot of quirky bugs.

Bash script should end with instruction sudo shutdown -r now Without sudo it never complies.

I don't know all the nuances of python2 to python3 but there wasn't that many unless you did some uncommon code things. AFAIK you should be able to just delete the spaces behind the print statement and it should work on polisy. Since print() is a function in python3 it should look like this print("xxxxxx") If you are not familiar with python you should likely stay away from your polisy and use a RPi as your "proving grounds" first. After you are confident the code works and understand some of the basics hen port it over.

polisy is a small CPU box hardware that can replace ISY994i and simultaneously hold polyglot and node servers in the same box. ISY994i could only house ISY software. Polyglot is a piece of software that works as a "sidekick" or extension to ISY software. There are various versions of polyglot. PG1 was the original. PG2 is the current running version. Polyglot cloud (PGc) is an option for some. PG3 is the coming version of polyglot (being developed) that can manage compensations for NS writers. Polyglots are basic software that services the node servers that users write.

I run several python3 scripts on my polisy. I had them running with PG1 but when PG2 was released they began to fail about once per month or so. I switched them back to a RPi for a time and now they are back on my polisy again, running without problems, so far. Time will tell. My ~25 WiFi RGBCW bulbs and strips run off this software on polisy, as a bridge between ISY NR and WiFi signals. You may need to upgrade your script to python3 syntax. I don't know much about python2 code but I doubt the print statements will run without losing the space between print and "(".

I looked at the time/date nodeserver but one thing that seems to be missed is a combination Month and day combination variable. However two conditions would suffice to accomplish any date with a yearless condition. I use a few programs to use the ISY internal system variables that already have that information. When we had to rely on connections, routers and cables to connect with polyglot the one box solution seemed much more reliable, at that time. Now, with a single box polisy that argument becomes somewhat moot. Have a look at this technique. I use it for most holiday lighting scenes and many other functions. It only uses one trigger variable for triggering other programs.

@asbril would be the best source I know for that subject. (note I flagged him)

Basically the same here. However I only have one X10 module left and I only monitor and turn it off with the middle of the night complete shutdown every night. It's connected to a heavy duty contactor that runs my shop dust collector, always run from an X10 remote pushbutton that sits on the chop saw. Michel told me X10 was working so I assumed it was my USB PLM on my polisy that doesn't support X10, anymore.