Steps to reproduce:

**Hi zabbix team,

since i updated our zabbix servers to the last 5.0 minor patch 5.0.16, i noticed a change of behavior on a trigger.

This trigger is a count on float item. Configured as follows:

{Template  - Infra:edgecheck.sh.healthcheck["\{#IP}"].count(5m,503)}<=4}

The item is a numeric float evaluated every 30 seconds and might return the 503 value in a normal case.

Result:
The item is a numeric float and As seen on screen evaluated every 30 seconds and might add the 503 value.

Since the number of values is not lesser than 4 in the last 5 minutes the alarm shouldn't be triggered. 

But since the update, the trigger is still triggered. We might have founded a workaround by passing the evaluated item to an unsigned integer for now, but since the item might also return negative values in some case, we had to change our scripts.

Expected:
Number of float item is well evaluated in count trigger function.