Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

Does it work for you? #7

Open
pdugas opened this issue Oct 9, 2020 · 11 comments
Open

Does it work for you? #7

pdugas opened this issue Oct 9, 2020 · 11 comments

Comments

@pdugas
Copy link
Owner

pdugas commented Oct 9, 2020

I am interested in hearing from folks using this integration and how good or bad it's working. Post here please.

@akluthe
Copy link

akluthe commented Oct 30, 2020

Just hooked this up tonight on my RT-340. Looking good so far.

@pdugas
Copy link
Owner Author

pdugas commented Dec 15, 2020

Got an email yesterday from Dan who says it's working with his RT-700.

@danielsfrazier
Copy link

Didn't see this 'issue' before I sent my email or I would have posted here. It's working good for me so far. I've only done a little test last night to turn on and off the grill and watch the graph/values change on my mobile. One thing I noticed was when I turned off the grill, the fan didn't run to clear the firepot like normal. This is probably because I didn't let it get to temp and run it for a while. I'll use it later in the week for a real cook and see how it behaves.

@pdugas
Copy link
Owner Author

pdugas commented Dec 16, 2020

As you can imagine, I turned mine on and off many times during development. I saw the same thing with the fan only continuing to run after it had actually been on long enough to warm up.

@mclever
Copy link

mclever commented Jan 21, 2021

Seems to work fine on mine. I'd really like to figure out how to detect when the alarm on temp probe a/b is hit so I can broadcast to google home. Thanks for all you have done so far!

@pdugas
Copy link
Owner Author

pdugas commented Jan 21, 2021

@mclever an automation using a template trigger something like below should fire when the probe temp is within 5 degrees of the target. Probably need to wrap that in a test to ensure the unit is powered on; i.e. not is_state('sensor.smoker_probe_a_temperature', 'unavailable') or something like that.

(states('sensor.smoker_probe_a_temperature')|float) > (states('input_number.smoker_probe_a_target')|float) - 5

@druw900
Copy link

druw900 commented Apr 22, 2021

I am having problems getting it connected to my RT-700. I tried with an IP I got from the logs on my phone and with an IP I got from my router. Also, used the deviceID and localKey I got from the logs on my phone. In the UI the status for the entities all show unavailable. Do I have to be connected to the network in the same way the device is, for example 2ghz vs 5ghz vs network cable? Are there ways to troubleshoot the connection?

@pdugas
Copy link
Owner Author

pdugas commented Apr 22, 2021

If you can ping the IP of the recteq from the HA box then I would assume the issue is not the network. You may want to fiddle with the tuyapower command line tool to see if you can communicate with it.

@druw900
Copy link

druw900 commented Apr 22, 2021

If you can ping the IP of the recteq from the HA box then I would assume the issue is not the network. You may want to fiddle with the tuyapower command line tool to see if you can communicate with it.

I tried the tuyapower but couldn't find any devices when I was wired or on wifi. I also tested pinging the device from inside the HA container and I got a response.

@pdugas
Copy link
Owner Author

pdugas commented Apr 22, 2021

You could enable more detailed logging.

# /root/config/configuration.yaml
logger:
  default: info
  logs:
    custom_components.recteq: debug
    pytuya: debug

@intlabs
Copy link

intlabs commented Jun 15, 2021

Works brilliantly with my RT-590, thanks! :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants