oskrypuch

The latter has been announced for the Polisy unit, when equpped with the soon to be released (new) inboard Z-Wave dongle. * Orest

I LIKE the present tense use there! * Orest

Use the Window Alarm node instead. Works for me correctly. * Orest

A pair of appliance lincs were running two sets of curtains. Both units about 12 years old, the one was getting a little flakey and not energizing to command, on occasion. Figured the other might start to go as well. Decided to replace both, and got the SS7 for that. I ordered them from the Aeotec store online (couldn't find the 7 anywhere else), didn't realize that they would ship from Hong Kong! After a couple of weeks, still no units, emailed support, they said they were stuck in Customs and I had to contact DHL. Seems they needed some $ for customs, got that sorted out. Units are very nice and compact, added them with no issues. The usual gazzilion nodes popped up, stored all but one in my unused node folder. Disabled the power reporting data, as I don't need it. Set the auto-off for 17 seconds so I only need to send an ON command, that toggles the curtains open/close state. Tweaked the programming, and they are working great. Also, given their location, will be great repeaters, especially since they are external units. Well, I guess a boring story, usually is when you meet with success! * Orest

@Prana electric Doesn't do anything much useful, but this is what you're asking for. timer initialize could be triggered by something. And presumably, you'd want something to happen when the counter reached zero. $_counter would need to be a state variable. (I( use the underscore to label variables as state variables) * Orest ----------- timer initialize - [ID 01A4][Parent 0054] If [some conditions or action for a trigger] Then Stop program 'timer run' $_counter = 60 Else - No Actions - (To add one, press 'Action') ----------- timer run - [ID 0094][Parent 0054] If 'family rm / FAM - pots' is switched On Then Repeat Every 1 second $_counter -= 1 Else - No Actions - (To add one, press 'Action') ----------- timer stop - [ID 01B6][Parent 0054] If $_counter <= 0 Then Run Program 'timer initialize' (Then Path) Run [do something here] Else - No Actions - (To add one, press 'Action') Could also use a while loop for the counter, which is a little more efficient performance. timer run - [ID 0094][Parent 0054] If 'family rm / FAM - pots' is switched On Then Repeat While $counter > 0 $_counter -= 1 Else - No Actions - (To add one, press 'Action')

Wouldn't the presence of the 300 series device, downgrade the capabilities of the rest of the mesh as well? * Orest (not that there may be any other choice given hardware availability)

@Michel KohanimIt may already be too late in the process, but if not, please ensure that the antennas have a common (standard) connector, so they can be remoted from the Polisy. Many (myself included) have the Polisy in a nice rack, that is not very antenna friendly, with a lot of metal close by, and perhaps impossible to allow for a more optimal vertical antenna orientation. But, in any case, thanks much for the effort. * Orest

@johnnytReport back. * Orest

I have the early T1700/T1800 units with the v2.2 insteon dongle. Also have the remote sensors. They have been working flawlessly, hope they continue, else... *Orest

@johnnyt Did you do the whole exclude, link to a dongle on a computer, update OTW, etc. thing, then link back in, to update the firmware? *Orest

As I relate upthread my setup experience was a bit flaky as well. But now " In production", it has been working 100%. * Orest

Yes, it is an RF device, but a power spike could possibly affect it. I'm reaching here, but not sure why it shouldn't be working. Taking it to first principles, I would take the Zen17, put it on a regular outlet, and then short and open the sensor input with a pair of alligator clips or a bit of copper wire. If it doesn't work then, something is not set up correctly, or the unit is sick, the former more likely. If it does work, then there is something about the in-use setup that is causing an issue. Can also try excluding the Zen17, factory resetting the Zen17, readding it, and then positively setting the only parameters you want changed (again). * Orest

Take the Zen17 OFF the UPS power. Yes, it is an RF device, but a power spike could possibly affect it. As you have it set up, mine works 100%. * Orest

Are you by any chance powering the Zen17 on the circuit supplied by the UPS? It is of course an RF device, but the surge might be doing something. Did you try to run a program, to see if it would notice the change, even though it isn't shown in the admin console? * Orest

If you have to manually remove all your devices from the stick/ISY, and then add them in with the stick plugged into a laptop, [do the update], and then remove them and then add them back to the ISY -- that is completely impractical. Besides being rather time consuming, it would scramble all of your ISY programming. I would have to need that update, really badly! * Orest

@johnnytInteresting. How did you perform the firmware update? * Orest

Well, you could try a backup, factory reset on the Z-Wave stick, and then restore. Worth a shot. * Orest

@asbril STOP! There is a procedure for backing up your entire Z-Wave setup, but you can't do it with the Polisy. Check out the ZOOZ stick firmware upgrade procedure. That directs you to install some free software from the ZOOZ site. That same software has a backup/restore function. If you do need to swap in a new dongle, then you can import your entire setup and save yourself a lot of time. And, you could try, updating the firmware, slow operation is one symptom of (shipping) v7.15 firmware problems. * Orest

Do you have the model numbers? And you use a PG3 node? * Orest

Yes, that was a serious irritant. I found my own solution, just noticed yours (I believe it is yours) in the cookbook. * Orest

I remember when ISY first introduced variables, of course most rejoiced. But, there was one comment, I think from someone not familiar with such things, "What are variables used for (in programming)?". I had to chuckle. This is an interesting discussion. I thought for a bit that I was on stackoverflow. ? * Orest

Thanks! * Orest

A bit of historical reflection. Before there were variables AT ALL in ISY (not that long ago), we had to use Program TRUE/FALSE state as boolean variables, and even creatively using several together to keep track of binary number values. Now we have the luxury of using either method, as it best fits our programming style and priorities. All good! * Orest

@bpwwerI have the PG3 nodes for WB, OW & WF. Running the PG3 .55 BETA. I presume that on the free weather service accounts, Weather Bit and other public weather servers, they will restrict polling intervals for IP identified requests. I have a Tempest for most of my weather data, but still pull in WB and OW for the winds (sheltered location) and forecasts. I'm not concerned with Weatherflow of course, but for WB & OW Is the polling interval that the weather service sees, determined by what happens in an IoP program, or is the polling interval determined and set in the PG3 node? I don't need the forecast at any rapid intervals, every 6hrs is fine, just want to be sure I'm not locking myself out to up-to-date data at random if for example the punitive lock outs are for 24 or 48 hrs. * Orest

I'm using the zen17 for monitoring the garage door states. Seems solid, although there were some small hiccups in the setup for me. I posted about it here: Although you are harnessing the other side of this IOLinc equivalent, have a peek, it may make your setup easier, especially if you are yet a Z-Wave newbie (like me) * Orest