Failed to Setup

[SteveHoyt]

Just tried starting this version and got Failed to setup.

I have attached log and version info below.

home-assistant_2023-06-05T17-58-26.519Z.log

[SteveHoyt]

here you go. pg3-backup-6-6-2023_71919_AM.zip

[shbatm]

Received, looks like exactly what I need. Thanks!

[shbatm]

https://github.com/shbatm/pyisyox/releases/tag/1.0.0a7 should address this issue, but needs further testing. See request:

https://forum.universal-devices.com/topic/41342-how-to-use-solaredge-info-in-ha/?do=findComment&comment=367821

[SteveHoyt]

Good morning. I am back and will try to do what you need today. Before I start, a couple questions to make sure I do what you need. Bear with me as I have limited experience with ssh commands. So a couple questions. 1) you mention I need..(assuming you have Python >= 3.10 and pip installed). Do I need to verify this before I proceed. If so, please give me the commands do the verify. I assume I must login to my PG3 via ssh to do them? Is that right? 2) Assuming I do have the right versions then.....again I should be in the PG3 via ssh right.? After executing the commands, please give me the commands to do.. "dump all of the config files to a "./.output/" directory and output the events to the log. Ctrl+C to disconnect.

Thanks. Many moons ago I worked with unix but that is long gone and need hand holding to make sure I get it right for you.

FYI I will be doing all this on a IMAC connecting to the PG3. I do have a PC too if that makes a difference.

[SteveHoyt]

I think my brain must be working at 1/2 speed after thinking about this some more. That is what a 9 hour drive home does to one. In any case, it looks like what you need, I should be doing in the HA terminal interface not PG3 as I thought. I just updated HA. Here are the versions I am running. HA 2023.6.2, OS 10.3, Frontend 20230608.0 if thats the case question 1) still applies I believe, do I have the correct Pyton and PIP. Question 2. nudge me in the direction of how to get the files you need.

Thanks Steve

[shbatm]

Anything that can run python and is connected to your network will work. The easiest to do this is probably the "Studio Code Server" addon in Home Assistant--assuming you're running Home Assistant in a way that has addons (Supervised or OS). (I checked the current version of my Polisy via SSH and it is only 3.9, so that won't work, you can check with python3 --version).

Pressing Ctrl + ` in the Studio Code Server editor screen will open a terminal at the bottom which has access to Python 3.11 and PIP.

After that just run the two commands in the terminal:

pip install pyisyox==1.0.0a7
python3 -m pyisyox http://polisy.local:8080 admin "yourpassword" -o -v

This installs the latest alpha version of the module, and then connects and dumps everything. You'll be looking for any errors in the log on the terminal, and then the .output folder will show up in the current folder on the left of the browser.

[SteveHoyt]

A quick update. I am really flying blind, but after a bit of reading, I think I understand conceptually what I am trying to do.

So: 1) got Studio code server installed. Checked Python version to be 3.11 2) ran the pip install and it seemed to work. 3) ran the python3 command. Seemed ok. Got tons of messages in the terminal window. All were colored blue or green. Searched the terminal output and no obvious error messages seen. Was hoping maybe they would be red if there were any, but only guessing. I am not able to copy or get the entire text to send to you, only a snippet using ctrl V. 4) Checked .outfolder…it is empty. I continue to see updated messages every few seconds. So something is working. See the sample below.

5) One thing to note. After the custom install failed, awhile back, I went to a previously working backup that does NOT have the custom install directory. So when I look at the integrations running it shows the standard version. I also did NOT restart HA after the pip install, if that matters. I tried to look a bit at the HA directories, to see if I could tell if it was installed, but now for sure I am out of my league

I am not sure if this is of any value, but am happy to try anything else if it would be of value.

Snippet below from terminal output.

2023-06-20 15:56:44 INFO [main] Node status updated: {"address": "n016_686428", "status": 7178354, "detail": {"parent": {}, "status": null, "family": {"instance": "16", "address": "10"}, "flag": 128, "node_def_id": "SESITE", "address": "n016_686428", "name": "Hoyt, Steve", "pnode": "n016_686428", "elkid": "", "type": "0.0.0.0", "enabled": true, "device_class": "0", "wattage": "0", "dc_period": "0", "start_delay": "0", "end_delay": "0", "property": {}, "rpnode": "", "sgid": "", "custom": {}, "devtype": {}, "zwave_props": null, "protocol": "node_server", "node_server": "16", "qry": null, "ctl": null, "rsp": null, "tx": "", "rx": ""}, "last_changed": "2023-06-20 15:56:44.779802", "last_update": "2023-06-20 15:56:44.779798"} 2023-06-20 15:56:44 VERBOSE [pyisyox.events.router] <?xml version="1.0"?>ST6595184n016_6864286595.184 WattsProduction 2023-06-20 15:56:44 INFO [main] Node status updated: {"address": "n016_686428", "status": 6595184, "detail": {"parent": {}, "status": null, "family": {"instance": "16", "address": "10"}, "flag": 128, "node_def_id": "SESITE", "address": "n016_686428", "name": "Hoyt, Steve", "pnode": "n016_686428", "elkid": "", "type": "0.0.0.0", "enabled": true, "device_class": "0", "wattage": "0", "dc_period": "0", "start_delay": "0", "end_delay": "0", "property": {}, "rpnode": "", "sgid": "", "custom": {}, "devtype": {}, "zwave_props": null, "protocol": "node_server", "node_server": "16", "qry": null, "ctl": null, "rsp": null, "tx": "", "rx": ""}, "last_changed": "2023-06-20 15:56:44.818573", "last_update": "2023-06-20 15:56:44.818572"} 2023-06-20 15:56:44 DEBUG [pyisyox] Updated node state: Hoyt, Steve (n016_686428), changed=state 2023-06-20 15:56:44 VERBOSE [pyisyox.events.router] <?xml version="1.0"?>GV40n016_6864280 minuteSince Last Update 2023-06-20 15:56:44 INFO [main] Node status updated: {"address": "n016_686428", "status": 6595184, "detail": {"parent": {}, "status": null, "family": {"instance": "16", "address": "10"}, "flag": 128, "node_def_id": "SESITE", "address": "n016_686428", "name": "Hoyt, Steve", "pnode": "n016_686428", "elkid": "", "type": "0.0.0.0", "enabled": true, "device_class": "0", "wattage": "0", "dc_period": "0", "start_delay": "0", "end_delay": "0", "property": {}, "rpnode": "", "sgid": "", "custom": {}, "devtype": {}, "zwave_props": null, "protocol": "node_server", "node_server": "16", "qry": null, "ctl": null, "rsp": null, "tx": "", "rx": ""}, "last_changed": "2023-06-20 15:56:44.917178", "last_update": "2023-06-20 15:56:44.917170”}

Steve

On Jun 20, 2023, at 10:49 AM, shbatm @.***> wrote:

Anything that can run python and is connected to your network will work. The easiest to do this is probably the "Studio Code Server" addon in Home Assistant--assuming you're running Home Assistant in a way that has addons (Supervised or OS).

Pressing Ctrl + ` in the Studio Code Server editor screen will open a terminal at the bottom which has access to Python 3.11 and PIP (the current version of my Polisy via SSH is only 3.9, you can check with python3 --version.

After that just run the two commands:

pip install pyisyox==1.0.0a7 python3 -m pyisyox http://polisy.local:8080 admin "yourpassword" -o -v This installs the latest alpha version of the module, and then connects and dumps everything. You'll be looking for any errors in the log on the terminal, and then the .output folder will show up in the current folder on the left of the browser.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1599248628, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWPPDR7HS466H5LIWDDXMHPCTANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[shbatm]

As long as you didn't get any literal red flags (yes, errors are red), then it sounds like everything loaded ok. This was just to test the connection, loading, and event stream (the messages you were seeing every few sec). Nothing in Home Assistant had been updated yet.

If that's all good, then I'll push a new version of the HACS integration later today/tomorrow and you can test in Home Assistant.

[SteveHoyt]

As far as I can tell everything seems ok. The event stream is still running this morning.

I will keep an eye out for the new integration. I assume HA will alert me.

Also, do I need to do anything to stop the stream ( I believe you mentioned ctrl C in a post awhile back ) or will it all stop with the update and restart.

Thanks

On Jun 21, 2023, at 7:49 AM, shbatm @.***> wrote:

As long as you didn't get any literal red flags (yes, errors are red), then it sounds like everything loaded ok. This was just to test the connection, loading, and event stream (the messages you were seeing every few sec). Nothing in Home Assistant had bred updated yet.

If that's all good, then I'll push a new version of the HACS integration later today/tomorrow and you can test in Home Assistant.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1600981708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWNEXGXTNV6U67WCJXTXMMCV5ANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[shbatm]

Updated with https://github.com/shbatm/hacs-isy994/releases/tag/v4.0.12

Update in HACS and restart Home Assistant. Let me know what issues you have.

[SteveHoyt]

Looks like progress, but still got "failed to setup". Log files and NS Files attached home-assistant_2023-06-22T14-58-36.703Z.log Archive.zip

[SteveHoyt]

Got another “failed to start” files uploaded to github thread

On Jun 21, 2023, at 5:57 PM, shbatm @.***> wrote:

Updated with https://github.com/shbatm/hacs-isy994/releases/tag/v4.0.12

Update in HACS and restart Home Assistant. Let me know what issues you have.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1601870567, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWMZNLC7VCDBR62CI2TXMOJ7JANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[SteveHoyt]

Good News

Please ignore my earlier “failed to start” posts.

With all the testing we did, and the fact that I had not rebooted the machine in a kong time. I thought it might be a good idea to try a reboot. Also there was a new Solar edge node server release.

So I installed the new node server and rebooted my machine running HA and lo and behold it started fine.

I’ll let you know if I see any other issues.

Steve

On Jun 21, 2023, at 5:57 PM, shbatm @.***> wrote:

Updated with https://github.com/shbatm/hacs-isy994/releases/tag/v4.0.12

Update in HACS and restart Home Assistant. Let me know what issues you have.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1601870567, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWMZNLC7VCDBR62CI2TXMOJ7JANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[shbatm]

Took care of a few of the errors in your log anyways. V4.0.13 should be available now.

[SteveHoyt]

Good Morning. I did a restart today I noticed a number of messages in the log file, that indicate I should send them to developer for you to look at.

See the attached file.

Edit. Take a look at the web socket error.. I am getting hundreds per second Also I updated HA this morning to version 2023.6.3 so maybe that is the cause Update 2 Just backed off to HA version 2023.6.2 and issue is still there.

Everything is working fine so far. I am dealing with the new 200+ entities, that I was asking you to provide, which you did. The old saying be careful what you ask for.

Thanks Steve home-assistant_2023-06-24T18-07-47.555Z.log.zip

[SteveHoyt]

Good morning.

I left a new log file on Github, over the weekend with some errors I think you need to see.

Also the web socket errors appear to have crippled the ISY admin console. It now won’t start and I am getting the error already subscribed.

Per Ravi ( the UD mobile guy ) in another thread, he suggests the following cause for the error. I have rebooted the PG3 part, but not my polisy as the ISY part is still OK and I need it.

Thanks

"This error is usually related to clients (i.e. Admin Console, UD Mobile, HA integration, PyISY) not calling unsubscribe from the ISY event stream (subscription) when it stops viewing or perceives there was an error. This causes all available subscriptions to be used so new clients (i.e. Admin Console) can not start properly. Usually a reboot corrects the issue, or waiting some time. Waiting some time assumes the client causing the error is acting properly or it may continue using available subscriptions (event streams) which will continue lockout. PyISY, used by the HA integration, was a usual suspect in the past but I thought it was fixed. So if the issue persists after reboot try disabling the HA integration or any Node Server using PyISY.”

On Jun 22, 2023, at 6:33 PM, shbatm @.***> wrote:

Took care of a few of the errors in your log anyways. V4.0.13 should be available now.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1603511586, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWJY4KKSMNXPBOXZEHTXMTW43ANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[SteveHoyt]

Good Morning

Just updated to the latest version and still seeing some errors. Log file attached. Let me know if you need anything else.

Thanks home-assistant_2023-06-28T13-40-44.164Z.zip

[SteveHoyt]

Hi

Still seeing some errors with the new version.

I have uploaded the latest log file to github.

Steve

On Jun 22, 2023, at 6:33 PM, shbatm @.***> wrote:

Took care of a few of the errors in your log anyways. V4.0.13 should be available now.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1603511586, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWJY4KKSMNXPBOXZEHTXMTW43ANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[SteveHoyt]

UPDATE

I thought it might be time for a fresh start, so I updated my PG3 along with the ISY running on polisy. I then did a power restart on the Polisy. I followed that with a restart of HA. The amount of errors has been significantly reduced and the already subscribed error seem to be gone now. So looking much better all in all.I have attached the latest log file output and a screen shot of the versions I am currently running on Polisy. It looks like we are on the home stretch.

home-assistant_2023-06-28T16-49-28.457Z.log.zip

[shbatm]

Making progress, I'm not sure what the websocket hangup issue was, but it looks like it got cleared up with a reboot.

2023-06-28 09:48:37.142 ERROR (MainThread) [pyisyox] Error parsing language file for node server slot 15, invalid format

There's 1 issue I'm still not able to run down and its with the language file for your WeatherLink node server--I can't reproduce with the backup file you sent me, that seems to load fine. Can you please download the following and attach it here?

http://your-device-ip:8080/rest/profiles/ns/15/download/nls/en_us.txt

2023-06-28 09:48:32.411 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:32.443 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:32.969 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:33.973 ERROR (MainThread) [pyisyox] Reported an Invalid Command received /networking/resources 2023-06-28 09:48:33.974 ERROR (MainThread) [pyisyox] Could not load response

These are because it is trying to load your network resources, but you don't have any defined. You can stop it from trying to load them by unchecking the "Enable adding network resource entities" box under Devices & Settings > ISY/IoX > Configure. I've marked this as default OFF for future versions.

2023-06-28 09:48:38.598 ERROR (MainThread) [custom_components.isy994] Node 4F 96 C4 10 has a parent node Pantry Motion.1 Motion (4F 96 C4 1), but no device was created for the parent. Skipping

This is most likely because you have the primary Motion node disabled either via an ignore string, or disabled in Home Assistant already. If not, let me know.

2023-06-28 09:48:39.876 ERROR (MainThread) [pyisyox] Could not communicate with device: 14 B7 52 1

This is a general comms error reported by the ISY. If you have a missing device(s) the ISY dumps them to the log every time you connect.

2023-06-28 09:48:38.736 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.inverter_1_apparent_power (<class 'custom_components.isy994.sensor.ISYSensorEntity'>) is using native unit of measurement 'VA' which is not a valid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

I will have to add a check for this and classify it as an "Apparent Power" device class in Home Assistant. This module uses the ISY's control names to determine device classes, and that node server uses "CPW" (Power) for the apparent power. It doesn't look like the ISY actually has a control for Apparent or Reactive Power (e.g. "APW"/"RPW"), just power and total_power_used (TPW). May be something to suggest to them to add.

2023-06-28 09:48:38.853 WARNING (MainThread) [pyisyox.events.websocket] Web socket server response error: Invalid response status 2023-06-28 09:48:38.865 WARNING (MainThread) [pyisyox.events.websocket] Web socket server response error: Invalid challenge response

These look like a generic websocket hiccup. As long as it reconnects immediately, I wouldn't worry too much about them. If you're connecting to the ISY over HTTPS and don't need to (e.g. same LAN), I highly recommend sticking with HTTP--it will be much faster.

[SteveHoyt]

See comments below in CAPS

On Jun 28, 2023, at 3:04 PM, shbatm @.***> wrote:

Making progress, I'm not sure what the websocket hangup issue was, but it looks like it got cleared up with a reboot.

YES APPEARS TO BE GONE FOR NOW 2023-06-28 09:48:37.142 ERROR (MainThread) [pyisyox] Error parsing language file for node server slot 15, invalid format

There's 1 issue I'm still not able to run down and its with the language file for your WeatherLink node server--I can't reproduce with the backup file you sent me, that seems to load fine. Can you please download the following and attach it here?

http://your-device-ip:8080/rest/profiles/ns/15/download/nls/en_us.txt

INFO ATTACHED

2023-06-28 09:48:32.411 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:32.443 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:32.969 ERROR (MainThread) [pyisyox] Client Response 400 Error Expected HTTP/ /networking/resources 2023-06-28 09:48:33.973 ERROR (MainThread) [pyisyox] Reported an Invalid Command received /networking/resources 2023-06-28 09:48:33.974 ERROR (MainThread) [pyisyox] Could not load response

These are because it is trying to load your network resources, but you don't have any defined. You can stop it from trying to load them by unchecking the "Enable adding network resource entities" box under Devices & Settings > ISY/IoX > Configure. I've marked this as default OFF for future versions.

SET IT TO OFF ERROR GONE 2023-06-28 09:48:38.598 ERROR (MainThread) [custom_components.isy994] Node 4F 96 C4 10 has a parent node Pantry Motion.1 Motion (4F 96 C4 1), but no device was created for the parent. Skipping

This is most likely because you have the primary Motion node disabled either via an ignore string, or disabled in Home Assistant already. If not, let me know.

2023-06-28 09:48:39.876 ERROR (MainThread) [pyisyox] Could not communicate with device: 14 B7 52 1

IT WAS AN OLD ISY MOTION DETECTOR THAT I GOT RID OF. I HAD IT DISABLED IN ISY. HAVE DELETED IT NOW ALL OK

This is a general comms error reported by the ISY. If you have a missing device(s) the ISY dumps them to the log every time you connect.

2023-06-28 09:48:38.736 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.inverter_1_apparent_power (<class 'custom_components.isy994.sensor.ISYSensorEntity'>) is using native unit of measurement 'VA' which is not a valid unit for the device class ('power') it is using; expected one of ['W', 'kW']; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

I will have to add a check for this and classify it as an "Apparent Power" device class in Home Assistant. This module uses the ISY's control names to determine device classes, and that node server uses "CPW" (Power) for the apparent power. It doesn't look like the ISY actually has a control for Apparent or Reactive Power (e.g. "APW"/"RPW"), just power and total_power_used (TPW). May be something to suggest to them to add.

SHOULD I OPEN A CASE WITH ISY OR DO YOU WANT ME TO, AS YOU UNDERSTAND THE SPECIFICS BETTER THAN I. LET ME KNOW

2023-06-28 09:48:38.853 WARNING (MainThread) [pyisyox.events.websocket] Web socket server response error: Invalid response status 2023-06-28 09:48:38.865 WARNING (MainThread) [pyisyox.events.websocket] Web socket server response error: Invalid challenge response

These look like a generic websocket hiccup. As long as it reconnects immediately, I wouldn't worry too much about them. If you're connecting to the ISY over HTTPS and don't need to (e.g. same LAN), I highly recommend sticking with HTTP--it will be much faster.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1612168467, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWKSY5YKQCV375WC2O3XNSS6BANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[shbatm]

Looks like the attachment didn't come through with the email reply.

As for the bug report to ISY, you could just take the paragraph above and open an issue on that Node Server's page for them to take it back to UDI. It's not really a big deal, more of a feature suggestion that would best come from the node server that would use it.

[SteveHoyt]

will do. I'll send something to node server developer.

Here is the file in 2 different formats text and pdf. Let me know if they don’t make it.



On Jun 29, 2023, at 11:48 AM, shbatm @.***> wrote:

Looks like the attachment didn't come through with the email reply.

As for the bug report to ISY, you could just take the paragraph above and open an issue on that Node Server's page for them to take it back to UDI. It's not really a big deal, more of a feature suggestion that would best come from the node server that would use it.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1613630708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWL7R5XILDXQ5U5DO7LXNXEXDANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[shbatm]

Nope. Github doesn't accept attachments from email.

[SteveHoyt]

requested files infoshbatm.pdf

[SteveHoyt]

just added it directly to the thread on github

let me know if that worked

On Jun 29, 2023, at 11:48 AM, shbatm @.***> wrote:

Looks like the attachment didn't come through with the email reply.

As for the bug report to ISY, you could just take the paragraph above and open an issue on that Node Server's page for them to take it back to UDI. It's not really a big deal, more of a feature suggestion that would best come from the node server that would use it.

— Reply to this email directly, view it on GitHub https://github.com/shbatm/hacs-isy994/issues/101#issuecomment-1613630708, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXIJHWL7R5XILDXQ5U5DO7LXNXEXDANCNFSM6AAAAAAY4RIEFY. You are receiving this because you modified the open/close state.

Steve



[SteveHoyt]

resending text in case the file did not get sent.

controller

ND-weather-NAME = WeatherLink ND-weather-ICON = Weather CMD-ctl-DISCOVER-NAME = Re-Discover CMD-ctl-UPDATE_PROFILE-NAME = Update Profile CMD-ctl-REMOVE_NOTICES_ALL-NAME = Remove Notices ST-ctl-ST-NAME = NodeServer Online ST-ctl-CLITEMP-NAME = Temperature ST-ctl-CLIHUM-NAME = Humidity ST-ctl-BARPRES-NAME = Pressure ST-ctl-DEWPT-NAME = Dew Point ST-ctl-WINDDIR-NAME = Wind Direction ST-ctl-SPEED-NAME = Wind Speed ST-ctl-SOLRAD-NAME = Solar Radiation ST-ctl-RAINRT-NAME = Rain Rate ST-ctl-GV0-NAME = Wet Bulb ST-ctl-GV1-NAME = Heat Index ST-ctl-GV2-NAME = Wind Chill ST-ctl-GV5-NAME = Yearly Rain ST-ctl-GV6-NAME = Solar Radiation ST-ctl-GV7-NAME = UV Index ST-ctl-GV8-NAME = Pressure Trend ST-ctl-GV9-NAME = Wind Gust ST-ctl-GV10-NAME = Daily Rain

ND-indoor-NAME = Indoor Conditions ND-indoor-ICON = Weather ST-in-CLITEMP-NAME = Temperature ST-in-CLIHUM-NAME = Humidity ST-in-DEWPT-NAME = Dew Point ST-in-GV0-NAME = Heat Index

ND-soil-NAME = Soil Conditions ND-soil-ICON = Weather ST-soil-GV0-NAME = Soil Temperature 1 ST-soil-GV1-NAME = Soil Temperature 2 ST-soil-GV2-NAME = Soil Temperature 3 ST-soil-GV3-NAME = Soil Temperature 4 ST-soil-GV4-NAME = Soil Moisture 1 ST-soil-GV5-NAME = Soil Moisture 2 ST-soil-GV6-NAME = Soil Moisture 3 ST-soil-GV7-NAME = Soil Moisture 4 ST-soil-GV8-NAME = Leaf Wetness 1 ST-soil-GV9-NAME = Leaf Wetness 2

EN_RAINTYPE-0 = None EN_RAINTYPE-1 = Rain EN_RAINTYPE-2 = Hail EN_RAINTYPE-3 = Rain & Hail

EN_DAY-0 = Sunday EN_DAY-1 = Monday EN_DAY-2 = Tuesday EN_DAY-3 = Wednesday EN_DAY-4 = Thursday EN_DAY-5 = Friday EN_DAY-6 = Saturday

EN_TREND-0 = Falling EN_TREND-1 = Steady EN_TREND-2 = Rising

EN_CARDINAL-0 = N EN_CARDINAL-1 = NNE EN_CARDINAL-2 = NE EN_CARDINAL-3 = ENE EN_CARDINAL-4 = E EN_CARDINAL-5 = ESE EN_CARDINAL-6 = SE EN_CARDINAL-7 = SSE EN_CARDINAL-8 = S EN_CARDINAL-9 = SSW EN_CARDINAL-10 = SW EN_CARDINAL-11 = WSW EN_CARDINAL-12 = W EN_CARDINAL-13 = WNW EN_CARDINAL-14 = NW EN_CARDINAL-15 = NNW

EN_WIND_DIRECTION-0 = N EN_WIND_DIRECTION-1 = NNE EN_WIND_DIRECTION-2 = NE EN_WIND_DIRECTION-3 = ENE EN_WIND_DIRECTION-4 = E EN_WIND_DIRECTION-5 = ESE EN_WIND_DIRECTION-6 = SE EN_WIND_DIRECTION-7 = SSE EN_WIND_DIRECTION-8 = S EN_WIND_DIRECTION-9 = SSW EN_WIND_DIRECTION-10 = SW EN_WIND_DIRECTION-11 = WSW EN_WIND_DIRECTION-12 = W EN_WIND_DIRECTION-13 = WNW EN_WIND_DIRECTION-14 = NW EN_WIND_DIRECTION-15 = NNW

[shbatm]

Received. I still cannot figure out what it's choking on. I will push an update later that uses a different method to process these files and see if that fixes (or at least pinpoints) the issue.

For reference, all it needs to do is filter out blank lines and comments, then split the " = " ... So I'm not seeing anything that jumps out that would break that.

[shbatm]

Finally found the issue with Node Server 15--the line endings in the original file are Windows (CR+LF) instead of Linux (LF). Most of my text editors that I use automatically correct the line endings, that's why I couldn't find the issue. Was able to update fake-isy-994 to serve the node server files you sent so I could find the issue.