Release Lazy.2

.github/workflows/cron.yaml

@@ -9,7 +9,7 @@ jobs:
  runs-on: "ubuntu-latest"
  name: Validate
  steps:
- - uses: "actions/checkout@v2"
+ - uses: "actions/checkout@v3"
 
  - name: HACS validation
  uses: "hacs/action@main"

.github/workflows/pull.yml

@@ -3,12 +3,15 @@ name: Pull actions
 on:
  pull_request:
 
+env:
+ DEFAULT_PYTHON: "3.10"
+
 jobs:
  validate:
  runs-on: "ubuntu-latest"
  name: Validate
  steps:
- - uses: "actions/checkout@v2"
+ - uses: "actions/checkout@v3"
 
  - name: HACS validation
  uses: "hacs/action@main"
@@ -23,10 +26,10 @@ jobs:
  runs-on: "ubuntu-latest"
  name: Check style formatting
  steps:
- - uses: "actions/checkout@v2"
- - uses: "actions/setup-python@v1"
+ - uses: "actions/checkout@v3"
+ - uses: "actions/setup-python@v4"
  with:
- python-version: "3.9"
+ python-version: ${{ env.DEFAULT_PYTHON }}
  - run: python3 -m pip install black
  - run: black .
 
@@ -35,11 +38,11 @@ jobs:
  name: Run tests
  steps:
  - name: Check out code from GitHub
- uses: "actions/checkout@v2"
+ uses: "actions/checkout@v3"
  - name: Setup Python
- uses: "actions/setup-python@v1"
+ uses: "actions/setup-python@v4"
  with:
- python-version: "3.9"
+ python-version: ${{ env.DEFAULT_PYTHON }}
  - name: Install requirements
  run: python3 -m pip install -r requirements_test.txt
  - name: Run tests

.github/workflows/push.yml

@@ -6,12 +6,15 @@ on:
  - master
  - dev
 
+env:
+ DEFAULT_PYTHON: "3.10"
+
 jobs:
  validate:
  runs-on: "ubuntu-latest"
  name: Validate
  steps:
- - uses: "actions/checkout@v2"
+ - uses: "actions/checkout@v3"
 
  - name: HACS validation
  uses: "hacs/action@main"
@@ -26,10 +29,10 @@ jobs:
  runs-on: "ubuntu-latest"
  name: Check style formatting
  steps:
- - uses: "actions/checkout@v2"
- - uses: "actions/setup-python@v1"
+ - uses: "actions/checkout@v3"
+ - uses: "actions/setup-python@v4"
  with:
- python-version: "3.9"
+ python-version: ${{ env.DEFAULT_PYTHON }}
  - run: python3 -m pip install black
  - run: black .
 
@@ -38,11 +41,11 @@ jobs:
  name: Run tests
  steps:
  - name: Check out code from GitHub
- uses: "actions/checkout@v2"
+ uses: "actions/checkout@v3"
  - name: Setup Python
- uses: "actions/setup-python@v1"
+ uses: "actions/setup-python@v4"
  with:
- python-version: "3.9"
+ python-version: ${{ env.DEFAULT_PYTHON }}
  - name: Install requirements
  run: python3 -m pip install -r requirements_test.txt
  - name: Run tests

.gitignore

@@ -3,6 +3,7 @@ pythonenv*
 venv
 .venv
 .coverage
+coverage.xml
 *.secret
 *.user
 traces

.vscode/launch.json

@@ -13,7 +13,7 @@
  "-P",
  "40000",
  "custom_components.meross_lan.emulator:run",
- "custom_components/meross_lan/traces/emulator",
+ "emulator_traces",
  "-K pippo"
  //"-U 01234567890123456789012345678901"
  ]
@@ -46,6 +46,14 @@
  "remoteRoot": "/usr/src/homeassistant"
  }
  ]
+ },
+ {
+ "name": "Python: Debug Tests",
+ "type": "python",
+ "request": "launch",
+ "program": "${file}",
+ "purpose": ["debug-test"],
+ "justMyCode": false
  }
  ]
 }

.vscode/settings.json

@@ -2,11 +2,6 @@
  "python.linting.enabled": true,
  "python.linting.pylintEnabled": true,
  "python.linting.pylintArgs": [
- "--disable=missing-function-docstring",
- "--disable=missing-class-docstring",
- "--disable=invalid-name",
- "--disable=bare-except",
- "--disable=broad-except"
  ],
  "python.pythonPath": "/usr/local/bin/python",
  "files.associations": {
@@ -18,5 +13,10 @@
  },
  "python.analysis.extraPaths": [
  "./custom_components/meross_lan"
+ ],
+ "python.testing.unittestEnabled": false,
+ "python.testing.pytestEnabled": true,
+ "python.testing.pytestArgs": [
+ "."
  ]
 }

README.md

@@ -76,7 +76,7 @@ Most of this software has been developed and tested on my owned Meross devices w
  - [MS100](https://www.meross.com/Detail/46/Smart%20Temperature%20and%20Humidity%20Sensor): Smart Temperature/Humidity Sensor
 - Thermostats
  - [MTS100](https://www.meross.com/Detail/30/Smart%20Thermostat%20Valve): Smart Thermostat Valve
- - [MTS200](https://www.meross.com/Detail/116/Smart%20Wi-Fi%20Thermostat) [experimental]: Smart Wifi Thermostat
+ - [MTS200](https://www.meross.com/Detail/116/Smart%20Wi-Fi%20Thermostat): Smart Wifi Thermostat
 - Covers
  - [MRS100](https://www.meross.com/product/91/article/): Smart WiFi Roller Shutter
  - [MSG100](https://www.meross.com/product/29/article/): Smart WiFi Garage Door Opener
@@ -101,8 +101,8 @@ In general, many device configuration options available in Meross app are not su
 
 ## Service
 
-There is a service 'meross_lan.request' exposed to simplify communication with the device and play with it a bit. It basically requires the needed informations to setup a command request and send it over MQTT or HTTP without the hassle of signatures and timestamps computations. You can check it in the 'Developer Tools' of the HA instance, everything should be enough self-explanatory there.
-I find it a bit frustrating that the HA service infrastructure does not allow to return anything from a service invocation so, the eventual reply from the device will get 'lost' in the mqtt flow. I've personally played a bit with the MQTT integration configuration pane to listen and see the mqtt responses from my devices but it's somewhat a pain unless you have a big screen to play with (or multiple monitors for the matter). Nevertheless you can use the service wherever you like to maybe invoke features at the device level or dig into it's configuration.
+There is a service called `meross_lan.request` exposed to simplify communication with the device and play with it a bit. It basically requires the needed informations to setup a command request and send it over MQTT or HTTP without the hassle of signatures and timestamps computations. You can check it in the 'Developer Tools' of the HA instance, everything should be enough self-explanatory there.
+Since version 3.0.2 the service allows you to publish the device response as a persistent_notification message in HA so you don't have to dig into logs in order to see the reply. The notification is optional and you have to add the `notifyresponse` key to the service call with a value of `true`
 
 ## Troubleshooting