Bumbershoot

I haven't turned on the system yet, still too many freezes overnight, and I'm still running on my ISY994 and PG2, not IoP and PG3. The Node server is running normally...

Well, I simply checked for status of this single detector (the status on this detector changed when any of my other hardwired detectors saw smoke), and this always worked as intended. I replaced these detectors with wireless Elk detectors quite a while ago, so this solution is no longer in use, but it worked: Smoke Bridge - [ID 004D][Parent 0013][Not Enabled] If 'Devices / dirMasterBedroom / Smoke Bridge-Smoke' Status is On Then Set 'Devices / dirLivingRoom / ZW 007 Siren' On Wait 2 seconds Set 'Scenes / scnAllInteriorLights' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / flcFan-Light' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / sldGuestVanityLight' Fast On Wait 2 seconds Set 'Devices / dirGuestBedroom / sldGuestShowerLight' Fast On Wait 2 seconds Send Notification to '3' content 'Smoke Detector Alert' Wait 5 seconds Set 'Devices / dirLivingRoom / ZW 007 Siren' Off Else - No Actions - (To add one, press 'Action')

@xlurkr, if you need a hard wired detector, it looks like Amazon still has these: https://www.amazon.com/gp/product/B000EVO9D4/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1 I put one of these in, connected it to the Smoke Bridge, and it worked as expected.

@stevehoyt, for the programs that are yellowed and say "Out of Memory" in the status page, the first thing to try is to simply re-save these programs. They may or may not need an edit (I would inspect them), but clicking on the "Save Changes" button might restore the functionality of the programs. This is a problem that was encountered often when folks upgraded from the v4.x.x firmware to 5.x.x firmware in the ISY994. It's a simple thing to try, at least...

My ISY994 has the correct time for sunrise/sunset (v 5.3.4), and my IoP has sunrise/sunset an hour later (v 5.4.1_2). The 'date' command on my Polisy indicates that the time on the machine is correct.

It appears that the Aeotec Multisensor 6 motion sensor does indeed work as a controller in a Z-Wave scene. The motion sensors in my Jasco switches/dimmers to not. I'm not sure what the difference is, as the Multisensors seem to have mostly the same set of commands that the Jasco switches/dimmers have. Lots to learn here... Aeotec Multisensor 6 node details: Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ---------------------------------------------- Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW 008 Motion Sensor 1 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW008_155 uid=8 security=None type=4.33.1 mid=134 tid=258 pid=100 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] Association Group ID 1 Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ZW008_1 - Primary Isy Node Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x20 V1 BASIC Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x86 V2 VERSION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x85 V2 ASSOCIATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x73 V1 POWERLEVEL Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x71 V3 NOTIFICATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x84 V2 WAKE_UP Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x80 V1 BATTERY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x30 V1 SENSOR_BINARY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x31 V5 SENSOR_MULTILEVEL Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - xEF V0 MARK Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Sun 03/13/2022 06:29:02 : [ZW-SHOW ] - Secure Sun 03/13/2022 06:29:02 : [ZW-SHOW ] Sun 03/13/2022 06:29:02 : [ZW-SHOW ] ---------------------------------------------- Jasco motion sensor node details: Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ---------------------------------------------- Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW 025 Motion Sensor 1 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW025_155 uid=25 security=None type=4.16.1 mid=99 tid=18765 pid=12338 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] Association Group ID 1 Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ZW025_1 - Primary Isy Node Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x20 V1 BASIC Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x73 V1 POWERLEVEL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x27 V1 SWITCH_ALL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x2B V1 SCENE_ACTIVATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x2C V1 SCENE_ACTUATOR_CONF Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x70 V1 CONFIGURATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x86 V2 VERSION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x71 V4 NOTIFICATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x60 V4 MULTI_CHANNEL Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x8E V3 MULTI_CHANNEL_ASSOCIATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x85 V2 ASSOCIATION Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - x56 V1 CRC_16_ENCAP Sun 03/13/2022 06:30:44 : [ZW-SHOW ] - Secure Sun 03/13/2022 06:30:44 : [ZW-SHOW ] Sun 03/13/2022 06:30:44 : [ZW-SHOW ] ----------------------------------------------

Is see now. Maybe there's still a bit of fixin' to do on the files?

Maybe I misunderstand, but I'd think that tab separated values in the file might be deliberate as well. https://en.wikipedia.org/wiki/Tab-separated_values

CR + LF is known as DOS format for text files, whereas a single LF is known as UNIX format. DOS format makes the files compatible with Windows text editors. I assume UDI did this deliberately, likely due to the error log formatting complaints that were addressed with ISY version 5.40, though I haven't followed the issue. In many *nix distributions there are included utilities to convert files: 'unix2dos' and 'dos2unix', neither of which are included in the POLISY FreeBSD distribution. https://www.freebsd.org/cgi/man.cgi?query=dos2unix&manpath=CentOS+7.1

I like the sounds of what you're doing. I live in a desert environment with an ongoing and persistent drought and porous, volcanic soil. Proper and effective irrigation requires precision here. Thanks to you, @JimboAutomates and @glarsen for helping me accomplish water savings with these tools (and thanks to @io_guy for starting me down this path). This is the single area where home automation actually pays... Also, @simplextech provided the EcoWitt nodeserver, and the EcoWitt moisture sensors are really useful.

Enhancements : - Added Gallon per hour I'm curious if this was added in support of this nodeserver? I'm considering buying a FlumeWater device to work in conjunction with my Rainmachine, much as @stevehoyt is apparently doing. I see some discussion in the github repository that suggests something like this.

This may be something entirely different that what you're asking for, but I was able to add an additional SKY unit to the hub that also connects to my TEMPEST unit, and the PG3 nodeserver shows data from both the SKY and the TEMPEST. Only one copy of the nodeserver running. Very handy. The SKY unit is measuring indoor data. Thanks for adding this functionality, @bpwwer!

It looks like @xKing has done the most recent commits in github, and somewhere I got the impression that he was working with UDI with Polisy (I could be completely wrong about that). I see he was active on github last month, so my guess is that it's not moribund yet!

I hope so. Over the last couple of years, the LiFX nodeserver has become very useful in this installation, and I'd love to keep it going.

@glarsen has several nodeservers, and has always been responsive.

To upgrade PG3 and everything else from the command line: sudo pkg update && sudo pkg upgrade

I'm not sure you can update past 2.80 on older generation bulbs. About half of my bulbs are new Gen 4 bulbs, running firmware 3.70, and the other half are older generation, running 2.80. I put the older bulbs where there is a strong WiFi signal (and where there's not much chance of them roaming around on my mesh network), and the new bulbs where the WiFi is weaker. It took some tinkering, but it's solved the problem. Gen 4 bulbs, in my experience, handle weaker WiFi quite a bit better.

I switched to LiFX from Hue specifically due to color saturation and brightness. My wife uses them for viewing artwork, and the LiFX bulbs are distinctly brighter with deeper colors than Hue. LiFX bulbs with the latest firmware (v 3.70 currently) behave much better on the network for me than bulbs with older firmware. This problem has been eliminated in my installation.

Actually, you can easily do it from the command line, if you know how to log into your Polisy. Use 'ssh' to log into the Polisy. Once you've logged in, navigate to the appropriate directory: cd /var/polyglot/nodeservers/AugustLock Then, use the 'touch' utility to create the file: sudo touch token.txt Then, you may need to change file ownership as @kzboray indicated above: sudo chown polyglot:polyglot token.txt The file created will be an empty file.

Use SSH and the 'tail' command. This command line string will give you the last 100 lines of the log: [admin@polisy ~]$ sudo tail -100 /var/isy/FILES/LOG/debug.log This command line string will give you a real-time scrolling view of the log: [admin@polisy ~]$ sudo tail -f /var/isy/FILES/LOG/debug.log Evaluating what you see in the log will be another issue... You'll be asked for the admin password for your Polisy when you run these command strings for the first time, and possibly subsequent times, depending on how much time has passed since the last run.

Nicely done, and thank-you!

You can turn off battery writes using a REST call in your browser if your ISY is busy: http://<your ISY IP>/rest/batteryPoweredWrites/off

I've dealt with this on a couple of WiFi mesh networks, and it's a PITA. Two things can work to help solve this: 1) attach one Sonos speaker to your network with an ethernet cable, or if you can't do that, 2) buy a Sonos Boost. Either solution has worked for me.

To me, that sounds like the proper order of precedence. Thanks.

Hi @Jimbo, you can disregard the temperature issue. It has corrected itself!