Does anyone if there is a Inkbird binding in development?
Just bought itc-308 for WiFi and it would be fun to have it in the system
Does anyone if there is a Inkbird binding in development?
Just bought itc-308 for WiFi and it would be fun to have it in the system
I would beinterested in this too. I have a wifi connected temperature controled socket already and was thinking that the bbq thermometers would be a nice addition if I could get Alexa to announce the burgers are ready etc
yes, i am interested in that too. is there a possibility?
The language in this forum is english, please retranslate the posts to english.
Any news on a possible development of the wifi Inkbird binding?
Recently this project supports Inkbird ITH-20R temperature humidity sensor. I have successfully linked 3 sensors to openhub.
It’s a bit of work getting it to work (and unknown if it’ll continue to work after 12 months without paying) but if you follow these steps up until the Configuration section
Tuya - Home Assistant (home-assistant.io)
You’ll then need to install “tuya-cli” on any linux box or your pi (if running a pi) like this:
npm i @tuyapi/cli -g
and then run
tuya-cli wizard
to plug in your Access ID & Access Secret (from the “Get authorization key” section of the HA guide I linked) so you can get your device’s secret key
You can use that info to populate your devices.conf file for this project to get it into openhab via mqtt.
TheAgentK/tuya-mqtt: Nodejs-Script to combine tuyaapi and openhab via mqtt (github.com)
I run docker so I used this docker image, which is just a wrapper for the TheAgentK project above. If you do, it MUST be configured for “host” networking instead of “bridge” or else it will always time out
mwinters-stuff/tuya-mqtt-docker: Docker image for tuya-mqtt (github.com)
All the temps come across * 10 so you will need to transform it to get it to display properly. Here’s the code for my MQTT thing
UID: mqtt:topic:mqttBroker:inkbirdItc308
label: MQTT - Inkbird ITC308
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:mqttBroker
location: Shed
channels:
- id: currentTempF
channelTypeUID: mqtt:number
label: Current Temp F
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/116/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/116/state
transformationPattern: JS:convertTuya-In.js
- id: setpointF
channelTypeUID: mqtt:number
label: Setpoint F
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/106/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/106/state
transformationPattern: JS:convertTuya-In.js
- id: mode
channelTypeUID: mqtt:number
label: Mode
description: ""
configuration:
stateTopic: tuya/itc-308-wifi_thermostat/dps/115/state
- id: heatingHysteresisTemp
channelTypeUID: mqtt:number
label: Heating Hysteresis Temp
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/117/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/117/state
transformationPattern: JS:convertTuya-In.js
- id: coolingBackTemp
channelTypeUID: mqtt:number
label: Cooling Back Temp
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/118/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/118/state
transformationPattern: JS:convertTuya-In.js
- id: highTempWarning
channelTypeUID: mqtt:number
label: High Temp Warning
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/109/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/109/state
transformationPattern: JS:convertTuya-In.js
- id: lowTempWarning
channelTypeUID: mqtt:number
label: Low Temp Warning
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/110/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/110/state
transformationPattern: JS:convertTuya-In.js
- id: refrigerationDelayMins
channelTypeUID: mqtt:number
label: Refrigeration Delay (Minutes)
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/108/command
stateTopic: tuya/itc-308-wifi_thermostat/dps/108/state
- id: temperatureCalibration
channelTypeUID: mqtt:number
label: Temperature Calibration
description: ""
configuration:
commandTopic: tuya/itc-308-wifi_thermostat/dps/102/command
transformationPatternOut: JS:convertTuya-Out.js
stateTopic: tuya/itc-308-wifi_thermostat/dps/102/state
transformationPattern: JS:convertTuya-In.js
and my transforms:
convertTuya-In.js
(function(i) {
return (parseInt(i)/10).toFixed(1);
})(input)
convertTuya-Out.js
(function(i) {
return (parseInt(i)*10);
})(input)
All the temperature items have this state description to make it pretty:
%.1f°F
The Mode item has this config - 2 I am not sure what to call since it’s neither “Cooling” nor “Heating” but not “Off” in the app but still not running either “Cool” or “Hot” outlets so functionally same as “Off”.
config:
options: 0=Off,1=Cooling,2=?,3=Heating,
readOnly: true
Like I said, it’s a bit of work but it seems to work great for me now.