According to the docs, one should better use state_attr, because it doesn’t give an error, if not available. Sorry @andersonshatch, not meant disrespectful!
Avoid using states.sensor.temperature.state , instead use states('sensor.temperature') . It is strongly advised to use the states() , is_state() , state_attr() and is_state_attr() as much as possible, to avoid errors and error message when the entity isn’t ready yet (e.g., during Home Assistant startup).
That gives us:
# instead of
states.climate.living_room_air_conditioner.attributes.outdoor_temperature
#use
state_attr('climate.living_room_air_conditioner', 'outdoor_temperature')
Cloud integration: If I don’t use (change anything) in AC for some time (hour?), the first command always reports failure. Also temperatures are update only when command is send to the cloud and HA never update’s its state if AC was for example turned off using remote controller or mobile application.
Is there any way to do something with it, maybe some form of active loop can be configured?
@mac_zhou I’ve got your code installed but it’s not properly connecting to my device, I’ve gone through the instructions 3 times just to be sure I didn’t do anything wrong. I have confirmed I have the correct IP address and double checked the ID from the QR code as well. I don’t know what I could be missing…
It shows the correct target temperature that I have set on the unit but inside HA none of my call service commands make any changes to the device, also it reports the indoor temperature as 32 when it’s really more like 69 or 70:
Well, I used midea-discover (had to adapt it for windows) to get the ID.
There it reported ‘unsupported’ (which doen’t make sense really, as ‘0xac’ should be supported right?).
It does seem to get the correct ID though…
Decided to ignore the warning and install the repository anyway.
has somebody tried to decipher the USB protocol between the wifi module and the AC? the wifi modules are somewhat unreliable: need to be repaired every month, at least for me. it would be nice to a mini computer (e.g. pi) directly to the AC’s usb slot.
Any ideas on how to get started on that project? I was thinking of snooping the USB communication using some MITM setup.
Anyone have come across the SK103 usb device ?? can it be adopted to work ?? Currently I tried both default components for both Mac_zhou and andersonshatch with no sucess …
…as does this component. It is working only via LAN, the cloud is not needed at all. As you can see, your module is based on the work of the component here in this thread.
But nevertheless it is another way to get to it, I’m always happy to see more than one solution. But your module isn’t a component for HA, and it isn’t working right now, or do I misunderstand:
In the current version of this module communication using the WiFi SmartKey and the Midea Cloud and communication via a TCP serial bridge connected to the UART port is supported. Direct connection to the WiFi SmartKey interface via a local LAN connection will be added later.
Depends on the model. Different models need to have the fake cloud, others don’t. My Olimpia Splendid (a labeled Midea) for example doesn’t. This component or better the underlying library does account for that.
It is a very deep project, and can be confusing… I need nearly an hour every week to read and check the Telegram group…
But as I said, please keep monitoring the new module, if it works, especially only internal (on LAN), it would be great to have an alternative. And the HA bit (the custom_component) shouldn’t be hard to implement, if the module is ready.
An intresting differentiation there. “OSK-103”. The previous attempts were based on the OSK-102 usb stick. Newer models (like xreme save) use the 103 variant.
As you can see, your module is based on the work of the component here in this thread.
