Danny de Vries
Danny de Vries
I've had the same issue. In my case I forgot to save and publish the change: File -> Save -> Save -> Publish
Good one! Let me investigate if we can prevent this issue from happing later.
I've seen this happening because of the increased logging of the client. Have you picked or noticed the increased amount of lines that is being gathered by the script?
This is the code in the script: `$TeamsStatus = Get-Content -Path "C:\Users\$UserName\AppData\Roaming\Microsoft\Teams\logs.txt" -Tail 1000 | Select-String -Pattern ` 'Setting the taskbar overlay icon -',` 'StatusIndicatorStateService: Added' | Select-Object -Last 1`...
If you are already using the separated Settings.ps1 file, then it's just replacing the Get-TeamsStatus.ps1 script. Otherwise you'll need to copy/past the information from your old Get-TeamsStatus.ps1 version to Settings.ps1,...
Nice find :) What is your use case to distinguish between camera on or off?
If there's interest from others, I'm happy to add it to the master branch.
I've borrowed some code and updated the original script which is working with the new (or current 😅) Teams client. Thanks for your help!
Probably because the initial creation used input_text template sensors. Will investigate further at a later moment.