gviliunas

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 ???

Mine is still going strong after 4+ years

@kzborayHi Kaz, I was going to suggest the .yaml file but see that you've already tried that. I'm using a router with dd-wrt and punish myself with semi-regular updates. Over the months I have noticed up and down changes to LifX connectivity following some of the dd-wrt firmware upgrades and settings changes that I made. Lifx seems to need a very generic/vanilla WIFI connection (20Mhz BW, no airtime fairness, etc.) I have 10 polys and 29 bulbs in my system and use a devlist.yaml file. Presently, I can reboot Polisy and almost immediately upon hearing the UDI "I'm back" tune, I can successfully command my lights. There is a sign in the bathroom advising guests "If the lights fail to work, unscrew the bulb, wait 3 seconds, and then screw it back in." I almost never need to do this emergency procedure anymore. ? Sorry, I don't have a specific setting for you to check but you may want to experiment with your router's WIFI settings - especially if using dd-wrt. Greg

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.

Soon Alexa Canada will want to see your vax passport before responding...."Papers Papers".......

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.

I tried configuring my ISY on Polisy with the same settings that are currently working on my ISY. I am using smtpout.secureserver.net (godaddy server) on port 80 and see the same problem as @whyworkwhen I try to send a test e-mail.

@mbkingThanks for your help! It worked and the finder now finds ISY on Polisy.

I had previously upgraded to version 5.04 and was able to connect to ISY on http://<ip address>:8080/desc via the finder. I have not used ISY on Polisy for a few days and several update packages were installed via the Polisy web page. Now the finder cannot find ISY on Polisy. - The Polisy service is running on Polisy. Tried rebooting Polisy. - If I try to update via ssh session, I get: [admin@polisy ~]$ sudo pkg update Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. - If I check https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/ There is no file "packagesite.pkg" only packagesite.txz

I was able to upgrade my polisy isy with problem but after this could not communicate with the PLM or any connected Insteon devices. Restarting ISY or disconnecting / reconnecting the PLM did not help. Rebooting Polisy solved the issue. Confirmed that LAN access to ISY now works properly.

PLMs shipped with DB9 to RJ45 cables. I was expecting to use this to connect the PLM to Polisy when the time came.

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

Upgrade SUCCESS but expect a whole lot of beeping. I followed Michel's steps above. My system was already at the prerequisite versions. Step 3 required several minutes to complete then needed to enter: "sudo shutdown -r now" for the reboot. Over ~ 2min there were 14 beeps in this pattern then I could login and all was good. beepbeepbeep beepbeepbeep beepbeepbeep beepbeepbeep beep beep Thanks to the UDI Team for all of their excellent work!

As an alternative, you may want to look at using Pushover and the Pushover node server for notifications. I have noticed that the timeliness of e-mail notifications varies. This hasn't pushed me to act ...yet but it is nice to know there are alternatives.

A few days ago, I remember Michel warning not to upgrade until further notice. They were having a problem moving to OS ver. 13 You may want to submit a ticket.

Michel's Home Automation in "G" ?????

@whywork, I just tried the manual update and am seeing the same problem as you...

I just had occasion to restart Polisy via the System / "Reboot Polisy" drop-down link in the web page. In the past, when doing this, I would hear 2 beeps followed by a long pause while Polisy reboots then 2 more beeps telling me that Polisy is again running. Now, after selecting the reboot, I hear 4 beeps followed by the long pause then 3 lower-tone beeps followed by 3 higher tone beeps, a short pause and then 1 beep followed by a longer pause and a final single beep. Old sound pattern: (shutting down): beep beep (Polisy back up): beep beep New sound pattern: (shutting down): beep beep beep beep (Polisy back up): Lowbeep Lowbeep Lowbeep Highbeep Highbeep Highbeep beep ....... beep Everything appears to be working properly. Is this a new feature? Polisy version: 2.2.13 Frontend: 2.2.9-5 Isy 5.3.3