So it’s a matter of choosing:
Keep using native Tuya integration at HA, and disable the device(s) in MQTT Hub, or use the “from Homey to HA per MQTT” method.
I don’t use Homey Tuya apps btw, only the HA Tuya integration (because it just works )
Thank you for your reply.
I also do not use the Homey Tuya app. A community app without proper support is just an accident waiting to happen.
The Homey entity shown, is not a Tuya integration in Homey, but the Tuya integration in HA, sent to Homey. I understand the confusion; rounding (or trunking) in Homey was non-existent, until recently
These images where posted to show entities from HA to HO working just fine.
All my integrations are realised within HA because it gives me (total) control which is just lacking in the Homey environment.
I agree about disabling the devices in MQTT hub. It doesn’t make sense to sycronise empty packages. But: why is default state “No” under “Exclude from Homekit” if there is no payload anyway?
About the payloads from Homey to HA, can you please elaborate on the "from Homey to HA per MQTT” method? It seems as if the entities from Homey to HA are always empty (in my setup). How do I do this? I do not have an immediate use case for data from Homey to HA, but I guess I’m just curious.
Edit : I do have one integration over Homey: Daikin. Unfortunately, my Daikin units are not accessible over HA. This would be an interesting use case…
For Homey to HA you are using MqttHub?
Then then device capabilities are synced to MqttBroker.
If the device is deactivated now in Homey MqttHub, the HA Mqtt entity is still active, but without a valid state.
Homey firmware 12.0.1 addes dynamic mode lists (enum capabilities).
Now wen can import the HA modes from an entity into a list selection capability in your Homey device.
Mode list are dynamic now in climate/fan/climatefan and vacuum devices.
In addition, you can import select entities into a device using a mode capability using the real HA modes.
Please update your Homey to FW 12.0.1 to be able to update to app version 1.7.x
Please do not install manually (from app store or via CLI) on older Homey FW. The app will be removed because of not matching minimun FW version.
I suddenly can’t add new devices anymore. After reinstalling the “Home Assistant Community App,” it has completely disappeared from my Homey. I can still find it in the store, but when I click “Install,” nothing happens. Has anyone encountered this issue before?
For anyone who likes to reverse a binary sensor’s state
My HA robovac device has ‘water attached’ and ‘mop attached’ binary sensors.
I’ve added them as alarm_generic to Homey, to get a notification on the device tile when something is not attached.
Now, both robovac values are set to “on” when all’s fine, but then it would alarm in Homey.
With a “few minutes” of trial and error, and three mugs of coffee, I figured it out and wanted to share the code for the "Converter Function HA → Homey:
(value) => {
if (value === "off") { return true; }
if (value === "on") { return false; }
}
The Homey device has a mode selection with all standard HA options.
You HA device only sopports a subset.
It was not possible to use dynamic Mode lists. I will check if it’s possible to make id dynamic with Homey FW >=12.0.1
But dor now just use the possible modes
what is even stranger: it only happens in case of one of these thermostats (floor heating) and only when I am decreaseing temperature. When I increase temperature it works perfectly (the other two thermostats work completely fine both ways - up and down…).
(as I discovered as well eheh).
Thanks! 
