Is the RFX product supported?

[jazzmonger]

All my data is in the cloud.... it would be amazing to have this working.

I've built an ESP32 based controller for pellet smokers. Integrating the RFX probes is the missing link!

I'm ready for the data!

https://github.com/jazzmonger/Traeger-PID-Controller

[a2hill]

Yep RFX is supported based on feedback I've received (I don't actually have an RFX) I just need to update the readme. Really should start a discussion so people can comment with the devices they've tried it with 😅

[messnerdev]

My RFX devices show up in HomeAssistant, and seem to obtain an initial value (that would update if I restart HomeAssistant), but the value doesn't update with what's reflected in the cloud. I saw some mention of a new Listen Firebase API but didn't quite understand it.

Looking through errors I see a few.

These seem to be because some of the channels within a single probe will report a value of null:

This error originated from a custom integration.

Logger: custom_components.thermoworks_cloud
Source: custom_components/thermoworks_cloud/coordinator.py:123
integration: ThermoWorks Cloud (documentation, issues)
First occurred: 9:19:59 PM (3 occurrences)
Last logged: 9:50:01 PM

Channel 3 for device Blue (rfx meat - M100079434): Missing required attribute(s) for <class 'custom_components.thermoworks_cloud.models.ThermoworksChannel'>: value
Channel 4 for device Red (rfx meat - M100079435): Missing required attribute(s) for <class 'custom_components.thermoworks_cloud.models.ThermoworksChannel'>: value

Not sure what to make of the other two

This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/thermoworks_cloud/sensor.py:246
integration: ThermoWorks Cloud (documentation, issues)
First occurred: 9:50:01 PM (1 occurrence)
Last logged: 9:50:01 PM

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 270, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 481, in _async_refresh
    self.async_update_listeners()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 180, in async_update_listeners
    update_callback()
    ~~~~~~~~~~~~~~~^^
  File "/config/custom_components/thermoworks_cloud/sensor.py", line 246, in _handle_coordinator_update
    raise UpdateFailed(
        f"Cannot update sensor {self.name}: device channel {self._device_channel.display_name()} "
        "is not found")
homeassistant.helpers.update_coordinator.UpdateFailed: Cannot update sensor Unnamed channel (ch. 4): device channel unnamed channel (Ch. 4) is not found

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:657
integration: Sensor (documentation, issues)
First occurred: 9:20:00 PM (10 occurrences)
Last logged: 9:20:00 PM

Error adding entity sensor.10_06_1c_71_21_94_ch_1_temperature for domain sensor with platform thermoworks_cloud
Error adding entity sensor.m100079434_battery for domain sensor with platform thermoworks_cloud
Error adding entity sensor.m100079434_ch_1_temperature for domain sensor with platform thermoworks_cloud
Error adding entity sensor.m100079434_ch_2_temperature for domain sensor with platform thermoworks_cloud
Error adding entity sensor.m100079434_ch_4_temperature for domain sensor with platform thermoworks_cloud
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 657, in _async_add_entities
    await self._async_add_entity(
        entity, False, entity_registry, config_subentry_id
    )
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 778, in _async_add_entity
    entity.add_to_platform_start(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        self.hass,
        ^^^^^^^^^^
        self,
        ^^^^^
        self._get_parallel_updates_semaphore(hasattr(entity, "update")),
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 220, in add_to_platform_start
    super().add_to_platform_start(hass, platform, parallel_updates)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1337, in add_to_platform_start
    raise HomeAssistantError(
    ...<2 lines>...
    )
homeassistant.exceptions.HomeAssistantError: Entity 'sensor.10_06_1c_71_21_94_battery' cannot be added a second time to an entity platform

Attached this from the examples execution if it helps:
thermoworks_devices_data.json

[jazzmonger]

@messnerdev, So what integration are you using to get the RFX to show up???

[messnerdev]

https://github.com/a2hill/ha-thermoworks-cloud

[jazzmonger]

that totally worked! at least the initial load worked. I'll test it all on a cook.

[a2hill]

@messnerdev as far as not getting updated values after the initial load, have you tried decreasing the scan internal in the Home Assistant integration? By default it's set to 1800 seconds.

To do that, you can you click "configure" in the ThermoworksCloud Home Assistant integration and just set a lower value

[a2hill]

@messnerdev As far as the null values for your probes go, are the values always null for those channels? How do the probes appear when you view them in cloud.thermoworks.com?

[jazzmonger]

This seems to work well. I took the probes out this AM. I also defined template sensors that average all available (or all 4) sensors in each probe. I'm still playing with formatting on the graphs. I have the update interval set to 60s.

This is really great work!

[a2hill]

@jazzmonger you should take a look at this thread, I think he's also working on setting up a dashboard in home assistant

a2hill/ha-thermoworks-cloud#12

[messnerdev]

@a2hill Thanks! Updating the scan interval to 30s got my data closer to real-time (thanks for updating the Readme too). It does seem like it just does a current-value poll as opposed to retrieve-values-since-last-request poll (or some sort of pub-sub mechanism). As a bit of a data hoarder I wish I had all historical values, but practically speaking my 30s polling is good enough for most usages, and hopefully not aggressive enough to upset the API.

Hoping to dabble into modeling time-to-reach a specific set point after collecting enough data to train on.

[messnerdev]

@messnerdev As far as the null values for your probes go, are the values always null for those channels? How do the probes appear when you view them in cloud.thermoworks.com?

Here's the data from Thermoworks Cloud

Idk how to make a decent graph in HomeAssistant but channels 2 and 4 are now unavailable. Maybe polling broke after receiving a null value for each

Here's a bit better trend of the Home Assistant data historized in InfluxDB. Seems to loosely reflect the values from Thermoworks Cloud, just with less resolution. Just warming the probe with my hand...

[a2hill]

As a bit of a data hoarder I wish I had all historical values, but practically speaking my 30s polling is good enough for most usages, and hopefully not aggressive enough to upset the API.

@messnerdev If you feel like doing some investigation, I think you may be able to get at that historical data. From what I can see in the API responses from the thermoworks servers there is a reference to a BigQuery tableId and datasetId. I haven't used BigQuery before, but I think it should be possible

Can you open a separate issue for this to track the work?

[a2hill]

Idk how to make a decent graph in HomeAssistant but channels 2 and 4 are now unavailable. Maybe polling broke after receiving a null value for each

@messnerdev This could likely be it, I haven't looked at the logic in there for a while, but it could be something where the polling throws an error because it got an unexpected null and so stops polling

Can you open a separate issue for this?