Check for string param when doing range checking

[jmthomas]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.21%. Comparing base (c552eca) to head (9549c30).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1337   +/-   ##
=======================================
  Coverage   75.21%   75.21%           
=======================================
  Files         600      600           
  Lines       44676    44676           
  Branches      777      777           
=======================================
+ Hits        33603    33605    +2     
+ Misses      10986    10985    -1     
+ Partials       87       86    -1     

Flag	Coverage Δ
frontend	55.59% <ø> (+0.05%)	⬆️
python	83.64% <ø> (-0.01%)	⬇️
ruby-api	48.59% <ø> (ø)
ruby-backend	80.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ryanmelt]

Good fix for the bug. We still need to figure out how strings were ending up there though before closing this PR.

[ryanmelt]

I think the original issue was caused by sending a command with a manually entered state value which sends a blank string by default. Fix works.