wrj0

@garybixler I added an NVMe SSD to my eisy, per the instructions Michel provided here a few days ago. Setup the new file storage system as /storage. And created a directory to store the MP3 files, /storage/sounds The MP3 files I wanted to push to eisy were on a windows 11 PC, so I used the scp command to push those files to the new storage on eisy. From the windows directory with the desired mp3 files, D:\IoX\Sounds, used scp in a windows command prompt to push the files. Something like this for a single file: scp ./alert.mp3 admin@eisy.local:/storage/sounds Use your own eisy admin username here. Per Michel's info on the plugin, "For custom sounds, for now, you are in charge of creating a directory, uploading your music files, and giving read permission either to the plugin user or everyone." Indeed, I had to play a bit within eisy with chown, chmod, and chgrp to get permissions set for the directory and the files in /storage/sounds. (Lot's of info available on these linux commands with a quick web search). Once the files are in your desired directory in eisy, you'll need to add that directory in the path Custom Configuration parameter in the PG3x AudioPlayer plugin (for me it's /storage/sounds). I then restarted the plugin, and restarted the IoX Admin Console, and was able to select and play the files placed in the new eisy directory. Hope this helps a little. It was a fun challenge for me to get it to work, and did take a bit of time.

Your new plug-in works great! Nice job, Michel. Took me a bit of head scratching to get the mp3 files moved to the right place on the newly installed NVMe SSD - but they are working fine now. Thanks for this very useful addition.

Thanks for the suggestion, @Ross. I'm still looking at options, including Yolink. Still, it seems curious to me that the weather data from my local station (a Marine Corps Auxiliary Field) varies so widely. I've loaded two other weather plug-ins and am looking at weather data from other sources to see what may be the most consistent for my location.

Thanks again for your input. My polling is set to 600, so no temperature changes are provided to my programs in less than 10 minutes, as shown in my sample above. I'd really like to know the reason for the sudden changes in the reported temperature before trying to mask a possible underling problem with the accuracy of the temperature data. I'll spend some time to look more closely at the data from source station. OpenWeatherMap indicates they use a numerical weather prediction (NWP) model to do some manipulation of data from several sources to improve quality and accuracy. Curious if this may be the cause of the variations in temperature data that is reported.

I appreciate the suggestion, but if the reporting station is really reporting this much variation in temperature, how would a delay in my program help? Meanwhile, I'm looking at other weather nodeserver/plug-in options.

Recently, I noticed my freeze warning programs were triggering off and on around the freezing point, even though I have 2 degrees of hysteresis in the programs. So, I created a webpage log to track the temperatures (CLITEMP) reported by OpenWeather (to log each reported temperature change), and was surprised to see how much the values change over a short time period - sample of the log below. 2023/12/24 00:05:27 46.35 2023/12/24 00:55:27 42.53 2023/12/24 01:05:27 45.19 2023/12/24 01:15:27 44.92 2023/12/24 01:25:27 45.19 2023/12/24 01:45:27 44.92 2023/12/24 02:05:27 40.73 2023/12/24 02:35:27 45.23 2023/12/24 02:45:28 40.73 2023/12/24 02:55:27 46.08 2023/12/24 03:05:12 42.48 Should I conclude that the local reporting station has some problems accurately reporting current temperature? And maybe move to another service that pulls data from a different source? Or is there something I can do with OpenWeatherMap?

Bingo! Thanks Javi. The Local Networks field seems to have been auto-populated with the model name of my router. I looked at that several times and still missed it was not the proper SSID entry. After I forced the correct SSID and Saved, the system now Tests Local Connection successfully. Many thanks.

In another post today, @Javi indicated that adding a Local Connection into UD Mobile will allow faster operation when on the same network. I've been using UDM via the Remote Connection Settings successfully for some time, and wanted to get the Local Connection setup. I've followed the wiki instructions here but must be missing something, as I receive the following error when selecting "Test Local Connection": Both the eisy and iPhone running UDM are on the same local network. In UDM, the Add Local Networks under System Network Relations correctly finds my local router's SSID, username/PW are properly set, IOS Location setting for UDM is set to Always, and the eisy ip is reserved in the router. I often use SSH on the iPhone to view the eisy log, so wifi access doesn't seem to be the problem. What am I missing? Thanks.

Installed onto an eisy and a remote Polisy using the two commands provided above. Both systems now show PG3x 3.1.35 and appear to be functioning properly.

Prior to upgrading to 3.5.9 yesterday, after restarting PG3x, Notification NS would report in UDM: polisy (UUID) Notification Node Server Standard Edition Startup But after updating to 3.5.9, UDM now reports: polisy (UUID) Notification Node Server Test Edition Startup Did I do something wrong during the update to revert from Standard to Test Edition? I just ran the Update again from PG3x Purchases, selecting Standard, but UDM continues to show Test Edition.

@Argilos Bob also provided some additional info on the various debug levels in this post:

Polisy accepts 5.5mm x 2.5mm coaxial DC connector.

Ran upgrade packages for PG3x 3.1.22 -> 3.1.23. Left alone for several minutes. Couldn't log into PG3x, IoX showed Reboot required. Rebooted from Admin Console. AC showed reboot required after doing the reboot. Rebooted again, AC still showed reboot required. Front panel 5x and 6x presses didn't respond, so cycled eisy power. IoX 5.5.9 and PG3x 3.1.23 now working OK.

Updated an eisy and a Polisy at another location and rebooted both without issues. Had to restart PG3 to get weather Node Servers to update their online status. Great work by UDI.

Upgrade to IoX 5.5.7 and PG3 3.1.18 went smoothly following release notes procedure, including a Polisy power cycle then a PG3 restart. Well done, developers.

Chris acknowledged the bug report, and offered to investigate.

Thanks @kclenden. Ticket opened to report this possible IoX bug.

So, IoX may be determining 01Jan as day 0. Easy enough to do a simple modification to correct in a program: $iISY.DayOfYear = [Current Day of Year] $iISY.DayOfYear += 1

Yep, clock is set to 24-hour format, and is correct. Good thought, though.

In both my Polisy and eisy, I noticed today that $iISY.DayOfYear = [Current Day of Year] sets that variable to 48. But, today is day 49 for 2023 per epochconverter.com. Both devices correctly show today's date is Sat 02/18/2023. IoX v5.5.6 on both devices. What am I missing?

Yep, same thing with my tstat. Heat/Cool State status on UD Mobile immediately goes from Idle to Heating, but after completion of a heat cycle, it does take a few minutes before showing Idle. But Fan Mode status goes back to Auto immediately. Curious. @hchain Apologies for the delayed response; just saw your message above.

I picked up one of the TZ45R tstats off eBay for $30, and installed it yesterday. Enrolled easily into eisy, and so far basic functions seem to be working fine. UD Mobile controls the basic HVAC functions. Current temperature, Heat/Cool state, Fan Mode, Fan State, and Heat/Cool temperature set points all update immediately in UD Mobile. Initial IoX programs to detect and report temperature settings are working properly. Hard to beat this deal for a low-cost, simple Zwave thermostat.

Thanks for the suggestion. I may eventually go with something like the Kasa smart plug, but was hoping to use an existing eisy feature or service like WOL, if supported by the eisy.

Arbil's answer above offers a good reason.

After issuing a remote "shutdown -p now" and turning off the eisy, can it be restarted, perhaps via a Wake-On-Lan magic packet? If so, how does one enable WOL on the eisy?