Aeotec Multisensor report temperature suddenly of -5866.2 degrees

I’ve got an Aeotec multisensor hardwired which works really well in a space heater in my kids room all connected together to act as a mini heater system in their room.

I found that hardwiring gets this Aeotec sensor to report very fast temp changes which is great! It’s been running for almost a year just fine but suddenly the sensor is reporting a temp of (-5866.2F). I have power cycled with no luck. Is the only thing I can do is to entirely reset the thing adn re-add it? I always hate doing this with Zwave devices due to number of steps.

Anything else I can try?

It may have failed. I would try unplugging it, still without batteries, and leave it off line for at least 20 minuets and then plug it back in and wait and see.

How often is ‘rapid’? If it has been working for a year, your rate is probably ok; unless you have added more Z-wave devices.

I have a couple of these and have had constant issues with them. For me sometimes they stop reporting temperature all together and power cycles do not fix. I speculate this is caused by power fluctuations. When that happens I discovered accidentally that repushing the zwave configuration to the device resolves the issue. Since it’s a recurring problem, I wrote a script that I run via an automation when I don’t get a temperature update for ten minutes. The script below resets the sensor to my default config. You may also try repushing the configuration parameters via the device Config UI.


configure_aoetec_multisensor_node:
  alias: configure_aoetec_multisensor_node
  description: "Configures / reconfigures the AOETec Multisensor"
  fields:
    entity_id:
      description: "Entity Id"
      example: "sensor.sensor_2_temperature"
  mode: single
  variables:
    entity: "{{ entity_id }}"
  sequence:
    - service: system_log.write
      data:
        level: warning
        message: "Running configure aoetec_multisensor_node for {{ entity_id}} "
        logger: zwave
    # https://products.z-wavealliance.org/products/2684/configs
    - service: zwave_js.set_config_parameter
      data_template:
        # Battery
        entity_id: "{{ entity }}"
        parameter: 101
        value: Disable
        bitmask: 1
    - service: zwave_js.set_config_parameter
      data_template:
        # UV
        entity_id: "{{ entity }}"
        parameter: 101
        value: Disable
        bitmask: 16
    - service: zwave_js.set_config_parameter
      data_template:
        # Temp
        entity_id: "{{ entity }}"
        parameter: 101
        value: Enable
        bitmask: 32
    - service: zwave_js.set_config_parameter
      data_template:
        # Humidity
        entity_id: "{{ entity }}"
        parameter: 101
        bitmask: 64
        value: Enable
    - service: zwave_js.set_config_parameter
      data_template:
        # Luminance
        entity_id: "{{ entity }}"
        parameter: 101
        bitmask: 128
        value: Enable
    - service: zwave_js.set_config_parameter
      data_template:
        # Report interval
        entity_id: "{{ entity }}"
        parameter: 111
        value: 240
    - service: zwave_js.set_config_parameter
      data_template:
        # No report on threshold
        entity_id: "{{ entity }}"
        parameter: 40
        value: Disable
    - service: zwave_js.set_config_parameter
      data_template:
        # Disable motion sensor for now.
        entity_id: "{{ entity }}"
        parameter: 4
        value: 0

Second, a best practice is to use the filter integration on all incoming temperature data, this will remove outliers. I do this for all temperature and humidity sensors from all vendors because periodically I get weird readings.


sensor:
  - platform: filter
    name: "sensor_2_temperature_filter"
    entity_id: sensor.sensor_2_temperature
    filters:
      - filter: range
        lower_bound: 0
        upper_bound: 100
      - filter: outlier
        window_size: 4
        radius: 20

1 Like