gviliunas

My system uses several LIFX Mini (C and W) bulbs. These bulbs are all V3.60 firmware. All of these work properly with the PG3 LIFX NS. I tried to add several new bulbs. These have v3.90 firmware. These new bulbs add properly to the network and can be properly controlled by the LIFX cell phone app. The PG3 LIFX NS discovers the bulbs and adds them to the IOP Admin console device tree. On the Admin Console page for these bulbs, all are listed as offline and cannot be controlled via PG3 Restarting the NS, PG3, IOP, and Polisy does not fix the problem. Added @xKingto this as he is the author of the PG3 NS Has anyone else seen this? Edit: I learned a little more about this issue. After a firmware upgrade, the MAC address of the bulb is changed. (Usually incremented or decremented by 1). I tried manually deleting the old node on the NS Nodes page and modified my devlist.yaml to reflect the new MAC and IP. IOP shows the node as found but still lists it as being offline. Lifx_Bulb_debug.log

Hi @asbril. I went here: https://www.silabs.com/developers/simplicity-studio , created an account, and then downloaded Simplicity Studio. It takes awhile for the full package to install. Once you start Simplicity Studio, you will see a Tools button. Click on that for the Tools Menu. Click on Z-Wave PC controller from the Tools Menu. Once the tool is open, click on the "gear" icon and select the port that your PC has found for your plugged-in dongle. Click okay and then click Network Management on the tool's main page and you will see data related to your system. From there, you can fine a Backup / Restore button as well as a Reset Button (Be careful, this clears everything). You can also send basic on/off commands to your devices from here.

@asbrilYou may or may not have a problem similar to mine but......You still may want to ensure that your 700 dongle is backed-up via the Silicon Labs tool. My system was having trouble starting. The NS would all work but programs wouldn't work. Restarting and playing with the NS would somehow result in things working. Mitchel had correctly suspected that some NS or device was not responding. Eventually, the 700 stopped responding. I finally needed to do a factory reset on the dongle via the Silicon Labs tool. Now I need to carefully include-back all of my Z-wave devices being very careful to include them in the exact order that IOP originally had them. I am now about 50% done with this. With over 40 devices, I am kicking myself for not having a good backup of the dongle. Good Luck!!

Thanks @tazman and @tlightne for your feedback! I missed the fact that only part of tlightne's z-wave devices weren't working. Yes, definitely a different problem. Maybe time for me to try re-imaging to rule out the hardware.

@tlightneI think I am having the same root problem. I initially didn't recognize this as a Z-wave not working problem as I have only one Z-wave switch but many Z-Wave sensors (that I didn't notice as not working). For me, I noticed that none of my programs would run after a reboot. Initially this was intermittent and "playing" with PG3 NS start-stop would fix the issue and IOP would take-off and run. In an initial ticket to UD, Michel wrote that my programs were hung because IOP could not communicate with a device(s). Now, I noticed that when programs hang after a reboot, if I unplug the 700 dongle, IOP immediately queries the Insteon devices, runs programs and and all NS data seems to be displayed properly. All PG3 NS are enabled and seem to always disconnect / connect properly with each reboot. Hmmm seems to be related to the Z-Wave to IOP interface and not so much to PG3 (but I don't know for sure). Unfortunately IOP does not support hot-plugging the 700 dongle so I didn't expect Z-wave to begin working after plugging the dongle back in. I tried replacing the 700 dongle (with power off) with another good 700 dongle and restoring a previous backup with no change in symptoms. I am able to control my one light switch via the original dongle connected to my PC using the Silicon Labs tool so I don't think that the 700 dongles are the problem. The Polisy FreeBSD usbconfig command shows a "Silicon Labs Zooz ZST10700 Z-Wave Stick) connect so I don't think it's a usb problem. I have updated my original ticket and am awaiting UD's analysis. One way to possibly confirm if we are seeing the same problem is to ask if your programs will run when you have problems with your Z-wave? I created a simple Turn on light, Wait 5 sec, Turn off light program. In my case, when I do a Run Then, The icon turns green (forever) but no light on or off.

Early on I also tried disabling all NS (in 3 polyglots) but this didn't seem to do anything. I only made progress when I went to the top node of the Wireless Tag NS in the admin console and toggled Monitor Tag off and on then Reboot Tag Manager, then Discover. I am not sure if one of these or the combination caused the Please Wait pop-up to appear from the admin console and everything began to work.

@tazmanJust to close the loop. My programs were still not working after 24Hr so I submitted a ticket. Michel responded in his usual amazingly short time: "Programs will start running only after the initial query. So, I suspect that you have node servers (or devices) that could not be queried after the reboot." This led me to look at my PG3 Wireless Tag NS log where I found a string of interface errors. From the Admin console top node of the Wireless Tag NS, I toggled monitor tags off and on, clicked "Discover", and then clicked Reboot Tag Manager. ISY then popped-up a progress bar and began its query. After this, my programs, and system, were all running normally. Can't beat UDI Support!!!

Thanks @tazman I thought that I had the same problem last week and yes, it did clear on its own. I will wait and be patient. Maybe there is some queue that the system needs to work through???

Something strange is going on with my IOP 5.4.4 Yesterday I rebooted Polisy. After this, I noticed that no programs were running. Manual control of lights and scenes from the Main page of the Admin Console works normally. Today I began investigating further. Here is what I am seeing: 1. I verified that There are no Folder Permissions blocking. I added and removed a permission criteria just to be sure. I also tried re-saving many programs. 2. After ISY reboot, the summary page is showing that "Run at Startup" programs were never run. 3. I created a simple Turn on light, Wait 10 seconds, Turn off light program. If I Run Then, the Last Run Time is logged on the summary page, The activity shows "Running Then", The light never lights, and, 23 minutes later, the program is still shown as running. 4. Strange observation. After rebooting ISY, all of my programs were in Idle state. I created the test program above and did the Run Then of this program at 5:58:30. While I was watching, another program that I have set to trigger every hour (0. Announce the hour trigger) automatically changed state to "Running Then" at 06:01:10. This simple program now shows running, did NOT perform its task, and it is also not showing as completing. It appears that the scheduling part of ISY programs appears to be working but the actual engine that executes the code is stopped. Is anyone else seeing this type of behavior? I looked for some type of error log in Polisy but didn't find any that seemed to log program execution.

“ISY made me do it…” I have been a long-time user (>10yr) of ISY. Along the way I added Z-Wave, 10 Node Servers, 800 hundred programs, (8) Alexa, and Polisy to the fold. I have had my Polisy since the beta-group release and during that time, it has hosted my 10 node servers without issue. I installed IoP when it became available but was holding off migrating due to the need to manually migrate Z-Wave devices. Up until last Monday, ISY (> 10-year-old) was running the main show. Sometime in the dark rainy night, ISY died with a flashing red error LED. I thought this was just a simple sd-card change time but after 3 sd-cards and a continued persistent flashing red LED I took it as a “sign” to move to ISY on Polisy. Thanks to @dbwarner5 and many other members here for posting their tips, tricks, procedures, and advice. With these, my migration was absolutely uneventful. Insteon nodes, scenes, and programs all migrated without any issues. My only cost was the hour or two excluding and including all of the Z-wave nodes and fixing Z-wave scenes and program entries. This was also a good time to review some old programs. I don’t have any objective evidence but can say that with IoP, my system seems much faster and response to events seems crisper. I especially like the speedy opening of the Admin Console. ? I am very happy that I took the plunge and upgraded to IoP. Many of us have come to rely on our ISY home automation as an essential piece of modern life. Thanks to UD technical team and the contributors to this forum for making such an easy and painless upgrade solution possible.

@briansAt this point I have just be dabbling with IoP. The previous z-wave settings didn't matter to me so I just started over with the new stick. I am waiting for the migration to be able to move Z-Wave devices and for some node servers (Lifx) to migrate to PG3 before beginning a full-blown move from ISY. I also purchased my stick from Amazon.ca. I think that Zooz's Canadian distributor is Home Tech Solution on ON. Thanks for the link to 7.17.2. I just followed the link and was successfully able to upgrade to 7.17.2

@mmb, FYI: I experienced the same firmware upgrade issue as you. Finally, I contacted ZOOZ tech support. They had a few ideas to try but could not resolve the issue. Finally offered to replace the stick under warranty. I just received the replacement stick yesterday and was now able to successfully upgrade the firmware to v7.17. In the process, Silicon Labs tech support suggested that the problem might be that encryption keys might not have been written to the device during initial factory programming. I was not able to verify this an opted for the RMA instead.

@RPerrault, My devices were all added long ago, well before 5.4.3

I was curious and so gave it a try. I think it works. I have a Homeseer (I think the model is HS-200 - Older model with the multi-color lights). I added to scene as responder . The controller is an Aeontec Multisensor 6. I added the motion sensor node to the scene. The, I selected the MS6 (Not the scene itself) and see responder table. From here I selected the Homeseer switch in the table. At the bottom of the page, the link-type drop-down now includes "Z-Wave Basic" The MS6 now seems to control the switch in a "snappy fashion"

@Techman, My experience was slightly different After the upgrade, I noticed that the center LED was flashing rapidly. After a Polisy power cycle, now the left LED is blinking rapidly. Also, after the power cycle and a trial reboot polisy, the musical tunes are now gone. Policy is silent.....BUT EVERYTHING seems to work normally.

Previously, I had tried changing the Poilsy SSH password to something other than "admin" but this seemed to change back. Was this due to updates? I don't know. So far I've just be leaving it as "admin"

Thanks guys for keeping me honest! Don't know what I was thinking about the PLM communication speed. Got to stop mixing up teletype with fiber optics...... Yes, 19.2k seems much more reasonable for your long runs. Sorry for the confusion. Very Glad we have forum members here keeping projects successfully moving forward!!!

Although this connection uses standard Cat5 cable and connectors, the communication protocol is RS232. I think I remember the max recommended length was 4M when running at 38k baud. ISY communicates at 115k baud so I would expect that the recommended maximum distance should be fairly short, 2M ???

SUCCESS with Aeontech Multisensor 6 Motion Detection with S0 mode inclusion @Michel KohanimI was going to dive back into my Aeontech M6 this morning to see if any settings changes could make motion detection work. The sensor was included under S0 secure mode yesterday. I discovered that MOTION DETECTION IS in fact WORKING along with the environment reporting. To test this, all parameters are default except I set the PIR timeout (parameter 3) to 10 seconds. I apologize for the incorrect report that motion sensing was not working. I think I did not wait long enough for the PIR to stabilize.

And with this product....UDI has raised eyebrows in my office as I now sometimes issue "Company Polisy Updates" instead of "Company Policy Updates." Be careful out there - or they will look strangely at you too! ?

@bpwwerI spent some time trying to duplicate your results with the MS6 and made some discoveries: - If I include the MS6 in "Secure Mode" (Press the MS6 button 2x when including), I get the Temperature, Humidity, Luminance, UV and Battery Level values displayed immediately after inclusion. Also, the values seem to update according to the interval time set in parameter 111. (I did not need to change the wakeup interval time for this to work) - If I include the MS6 in "Regular Mode" (Press the MS6 button 1x when including), I only see the Battery Level value displayed. Waiting here doesn't matter. The default MS6 reporting should be every 5 minutes. I waited ~15 minutes and still the other values failed to be displayed.....but can be coaxed-out.... - To see the other sensor values when the MS6 was included in "Regular Mode," I needed to click the "Wakeup" button on the Multi-level sensor node and then click to write updates to device. Once I did this, the sensor values were displayed. Notes: 1. Clicking the "Query" button at the bottom of the Multi-level sensor node page appeared to do nothing. 2. I did not set any particular wakeup interval - just left the default 0-seconds when I clicked wakeup. - Okay - Now I have initial values for the sensors when included in Regular Mode BUT, the values do not update. I changed the update interval parameter (111) to 10 sec and varied the light striking the sensor. The only way to see the displayed value change was to click the "Wakeup" button on the Multi-level sensor node and then click to write updates to device. BUT it only updates this one time. I need to change to a different wakeup interval time (greater than parameter 111 value) and click Wakeup to see an updated sensor value. So, it appears that when the MS6 is included in Secure Mode, sensors and sensor reporting appears to work normally while if included in "Regular Mode," the wakeup interval needs to be set and constantly changed to see or have updated sensor values. - In all attempts I could not get motion-sensing to work.

I tried including an Aeontech Multisensor 6. The device included without any trouble but it doesn't work. - It does not respond to motion - The only parameter reported is battery level (100% - But my sensor is USB powered. Note: I did a factory reset on the MS6 before including.

Ah Ha. Early adopters... It seems we have all ordered a Zooz (mine arrives Friday) in anticipation of Isy on Polisy with Z-wave.... Almost like Christmas anticipation when we were little.... Isy, Polisy, and UDI - Entertaining in so many ways!

Same issue here. It's good to know through this forum that we all have the same problem ..... and that it's probably NOT with our systems. Funny that the outage times are different. Mine has been off since 7:30:57 on 9/25

Be sure to verify the voltage of the lighting. Some commercial lighting runs at 277V.