Bumbershoot

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!

This is PG3 with ISY on the Polisy, v 5.30. On polyglot v2 on the ISY994 the value is correct.

Hi @Jimbo, I'm seeing an issue with temperature with tag type 13. Reporting actual Celsius when it should be in Fahrenheit. See screenshots...

@Jimbo, a reboot of the Polisy has corrected the problem. I got the appropriate dialogue this time, and now have a token.

Okay, I restarted PG3 and reinstalled the nodeserver, but something's goofy here. The log says it's 3.0.31 2022-01-10 14:20:09,409 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.31 Starting... and the UI says it 3.0.36. I'm going to reboot my Polisy.

Hmmm.... Already on 3.0.36. [admin@polisy ~]$ sudo pkg info pg3 pg3-3.0.36 Name : pg3 Version : 3.0.36 Installed on : Fri Dec 31 18:26:57 2021 PST Origin : misc/pg3 Architecture : FreeBSD:13:* Prefix : /usr/local Categories : misc Licenses : MIT Maintainer : andrey@xkinghome.net WWW : https://github.com/UniversalDevicesInc/polyglot-v2 Comment : Polyglot v3 for UDI Polisy Annotations : repo_type : binary repository : udi Flat size : 59.6MiB Description : Polyglot v2 server for Universal Devices ISY994 version 5.x.x WWW: https://github.com/UniversalDevicesInc/polyglot-v2

Will do, thanks!

PM sent. I wanna support the developers, and I don't mind a few cuts and bruises.

Hi @Jimbo. Upon installing and starting the PG3 version of this nodeserver, there was nothing to prompt me to get an authorization token as there was in the PG2 version. Unfortunately, the token I got for the PG2 version doesn't appear to be valid for the PG3 version. Maybe I'm missing something, but it's not entirely apparent what that would be. Thanks!

I see that the Wireless Tag nodeserver has been released for PG3. I've been waiting for it... ?