Bug: PowershellSensor as Satellite Service - error_during_execution

[Skons]

Describe the bug
Powershell sensor does not work as satellite service. It works when Test Command/Script is executed, and it works as a hass.agent sensor.

To Reproduce
Steps to reproduce the behavior:

1. Go to Satellite Service
2. Click on Sensors
3. Click on Add New
4. Select PowerShellSensor
5. Add this as command $(get-date).ToUniversalTime().ToString('yyyy-MM-ddTHH:mm:ss')
6. Click Store Sensor
7. Click Send & Active Sensors

Expected behavior
The date as state in Home Assistant

Screenshots

Misc info (please complete the following information):

• Windows build (ideally screenshot/info of winver.exe output): Win10 22H2
• Windows' UI language: EN
• HASS.Agent version: 2022.14.0

Please check what's applicable (multiple answers possible):

• Installed via installer
• Installed manually
• Problem occurs in HASS.Agent
• Problem occurs in Satellite Service

[amadeo-alex]

Hello,
I cannot reproduce this:

Snippet from satellite sensor config:

  {
    "Type": "PowershellSensor",
    "Id": "67ce197d-bcb0-4a61-a604-a6f276aacd32",
    "FriendlyName": "",
    "UpdateInterval": 30,
    "Query": "$(get-date).ToUniversalTime().ToString('yyyy-MM-ddTHH:mm:ss')",
    "Scope": null,
    "WindowName": "",
    "Category": "",
    "Counter": "",
    "Instance": "",
    "Name": "AMADEO-PC-satellite_powershellsensor",
    "ApplyRounding": false,
    "Round": null
  },

[Skons]

this is mine:

[
  {
    "Type": "PowershellSensor",
    "Id": "3a0ef5bd-22bb-475d-9df2-d7ae48bb5430",
    "UpdateInterval": 30,
    "Query": "$(get-date).ToUniversalTime().ToString('yyyy-MM-ddTHH:mm:ss')",
    "Scope": null,
    "WindowName": "",
    "Category": "",
    "Counter": "",
    "Instance": "",
    "Name": "[snip]-satellite_powershellsensor"
  }
]

I noticed i missed ApplyRounding and Round. Stopped the service, edited the json, started the service again. No success. After send and activate the custom config was gone.

The satelite service is 2022.20.0.0. I am running the client from another disk (D:) then the satelite service (C:).

I also tried to change the command to $env:computername, that dit not work either

[Zarox666]

I get the same Error Code executing a Powershell Script that gets the the GPU Power Consumption via some String-Extraction out of nvidia-smi.exe.
This works perfectly fine from the Agent or when testing from the Config, but HomeAssistant shows the value as "error_during_execution".
0

Other Sensors, such as ProcessActive work without any problem.

[Zarox666]

Any ETA on this?
Running the PowerShell Sensor as User instead of Service works, but relogging everytime as User is not the idea behind a Server/Service.

[amadeo-alex]

@Zarox666
Hard to give ETA for a fix PR as I'm not able to reproduce this issue.
You may try to help with the investigation by posing the script that is not working for you.

@Skons
Strange that it removes the round config options, are you using newest available version of HASS.Agent?

[Skons]

Yes, it is stated in the first post: 2022.14.0.

if you want me to run a debug version, or enable debug logging (if possible), then i am happy to help

[Zarox666]

OK now its gettinig wiered.....

For me the service based sensor on my Server startet to work this morning (without any interaction from my end)
At that time the expected value changed from 0 to 5 and later back to 0.
The Service Sensor changed from unknown to 5 and later correctly to 0.

However the Service based sensor on my PC still reports unknown instead of the correct value of 0

Here is the Script that is used by both Sensors:
(in essence it reads lines out of a .ini file and fills a path variable with that. Then it counts how many running process exist that have their .exe file somewhere under that path and returns that number.)
`
#$DebugPreference = "Continue"

#Include

#Variables
$MinerInstances = 0
Get-Content $PSScriptRoot\mining.ini | Foreach-Object{
$var = $_.Split('=')
New-Variable -Name $var[0] -Value $var[1] -ErrorAction SilentlyContinue
}

Write-Debug "#####################################"
Write-Debug "MineManagerPath= $MineManagerPath"
Write-Debug "#####################################"

Get-ChildItem -Path $MineManagerPath -Filter .exe -Recurse -File -Name| ForEach-Object {
$ProcessName = [System.IO.Path]::GetFileNameWithoutExtension($_)
if (Get-Process -Name $ProcessName -ErrorAction SilentlyContinue)
{
$Process = Get-Process -Name $ProcessName
$ProcessPath = $Process.Path
$ProcessID = $Process.Id
Write-Debug "Found running Process $ProcessName out of $ProcessPath with ProcessID $ProcessID"
if ($ProcessPath -like $MineManagerPath+"" )
{
Write-Debug "Mining-Process found!"
$MinerInstances++
}
}
}

return $MinerInstances
`
The other Script that has the same issue retrieves GPU Power consumption via String extraction from an NVIDIA .exe file.
Its a lot more complex.

Let me set up a Test-Sensor with a power-shell Script that just returns 0 and see how that fares.

EDIT:
And yes, I am fully aware that it now shows "unknown" instead of the original "error_in_execution". I have no explanation for this.
I can even pinpoint when this happend:

[Zarox666]

OK,

succesfull Repro, but only on my PC not on my Server (more on that later).

The Names appended with _service are Service Sensors in HASS, the others are normal Sensors.
all 4 sensor are powershell sensors executing a powershell script containing just one line:
return 0

So this makes it clear, that its not due to the logic inside the Powershell script, but other factors must be at play here.
my Server is a Windows Server 2022 Version 21H2.
my PC is a Windows 10 Versiojn 22H2.
HASS Agent Version on both 2022.14.0

However we need to depart from the notion, that it never works:
(any number including 0 is a valid value)
(times where ZaroxOmega goes black is due to my PC beeing switched off)
(the problem are the yellow "error_during_execution" and grey "unknown" blocks)
last week:

[Zarox666]

I might have made some progress.

My Service Log File on my PC is full with these messages:
2023-09-11 14:32:12.851 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:12.851 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:13.613 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:13.613 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:13.613 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:14.364 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:14.364 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors) 2023-09-11 14:32:14.364 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage') System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage') at System.Text.Encoding.GetEncoding(Int32 codepage) at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors)
I do not see these Messages in the Services Log on my Server, where the Powershell sensor works.

Digging into the Error Message searching for System.Text.Encoding.GetEncoding I found that "1" is indeed not a valid codepage.
See:
https://learn.microsoft.com/en-us/dotnet/api/system.text.encoding.getencoding?view=net-7.0
https://learn.microsoft.com/en-us/dotnet/api/system.text.encoding?view=net-7.0
However its not clear to me, why this would behave different between the two Systems.
1 is not a valid code page for either of them, so I can only assume, that
HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput
might be behaving differently between the two otherwise "identical?" scenarios.

[Skons]

It could be that the .Net version makes a difference. Mine is 4.8.09032. Nice find!

Edit: Same here

2023-09-11 17:13:22.842 +02:00 [FTL] 1 is not a supported code page. (Parameter 'codepage')
System.ArgumentException: 1 is not a supported code page. (Parameter 'codepage')
   at System.Text.Encoding.GetEncoding(Int32 codepage)
   at HASS.Agent.Shared.Managers.PowershellManager.ExecuteWithOutput(String command, TimeSpan timeout, String& output, String& errors)

[amadeo-alex]

Good find, thank you both!
I'll take a look at what may be causing this.

[amadeo-alex]

From what I've been able to research, it looks like this might be some kind of incompatibility between the .net/.netframework and the keyboard/system languages which are installed on a given system.
@Zarox666 could you please check the keyboard/system languages on both of your systems and look for discrepancies?
In the meantime I'll create a fallback logic to UTF-16 and put it as part of LAB02-Research/HASS.Agent.Staging#14 which should remediate the issue.

[Skons]

These are mine

But, as a user i do not have any problem running this. As SYSTEM it is a problem. Maybe there is something else in regards to the SYSTEM "user"?

[amadeo-alex]

Fix added to the PR and merged to the bulk PR LAB02-Research/HASS.Agent.Staging#24.
Unfortunately for now the only reliable way to get it is to build the project yourself :\ (I don't recommend accepting exe files/binaries from me or any other random internet user)