Just via PM, see my reply to Roberto.
1 Like
thanks roboliv!
openhab can discover all my objects? or I’ve to write all the items manually with the physical addresses?
and what about the thermo central HD4695 and HD4692 probes? have you worked on it?
goog morining!
yesterday I’ve installed a MH201 and after a few configuration mistakes I’ve succefully join some objects!
@roboliv, @Daniele_Z, @efa
can you:
- set log level to DEBUG (see here info)
- delete your MH201 thing (from PaperUI or text file) (you can put it back after the test)
- start a new device discovery and look into the openHAB log (http://<your_OH_ip>:9001).
You should find something similar to the following log lines.
Can you copy-paste here the relevant log lines?
(using openHAB code fences: see the buttons on top of the edit box).
This way I can add discovery support for the MH201.
Bye
M
[INFO ] ==OWN:UPnP== --- Found device # urn:schemas-bticino-it:device:scheduler201:1
[DEBUG] +=== UPnP =========================================
[DEBUG] | ID.UDN : uuid:pnp-scheduler201-1_0-AA:AA:AA:AA:AA:AA
[DEBUG] | ID.DESC URL : http://192.168.1.9:8020/upnp/device/desc.xml?udn=pnp-scheduler201-1_0-AA:AA:AA:AA:AA:AA
[DEBUG] | ID.MAX AGE : 1800
[DEBUG] | --------------
[DEBUG] | MANUFACTURER : BTicino S.p.A. (http://www.bticino.it)
[DEBUG] | MODEL : MH201 | Scenarios Programmer201 | 1.0 (http://www.bticino.it)
[DEBUG] | FRIENDLY NAME: MH201
[DEBUG] | SERIAL # : AA:AA:AA:AA:AA:AA
[DEBUG] | BASE URL : null
[DEBUG] | UPC : null
[DEBUG] +==================================================
[INFO ] ==OWN:UPnP== |- MH201 (BTicino S.p.A.)
[WARN ] ==OWN:UPnP== device is not supported by the binding (UDN=pnp-scheduler201-1_0-AA:AA:AA:AA:AA:AA)
hi massimo,
have I to remove the bridge? or only (only the 30 things!?!) the things that I discover and link with te items?
If I remove the bridge , I’ll lost all the things and item?
just remove the bridge thing, do the test, and re-add the bridge.
Your device things/items will be back online ad the same bridge will be used.
Bye M.
Hello,
here we are: is that what you ask me?
2019-09-06 14:35:09.260 [INFO ] [al.discovery.BusGatewayUpnpDiscovery] - ==OWN:UPnP== --- Found device # urn:schemas-bticino-it:device:IPscenariomodule:1
2019-09-06 14:35:09.262 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - +=== UPnP =========================================
2019-09-06 14:35:09.264 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | ID.UDN : uuid:upnp-IPscenarioModule-1_0-00035097118C
2019-09-06 14:35:09.266 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | ID.DESC URL : http://192.168.82.196:80/scenMod.xml
2019-09-06 14:35:09.268 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | ID.MAX AGE : 500
2019-09-06 14:35:09.270 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | --------------
2019-09-06 14:35:09.272 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | MANUFACTURER : BTicino S.p.A. (http://www.bticino.it)
2019-09-06 14:35:09.274 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | MODEL : MH201 | IP Scenario Module | 1.0 (http://www.bticino.it)
2019-09-06 14:35:09.276 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | FRIENDLY NAME: MH201
2019-09-06 14:35:09.277 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | SERIAL # : 00:03:50:97:11:8C
2019-09-06 14:35:09.279 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | BASE URL : http://192.168.82.196:80/
2019-09-06 14:35:09.281 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - | UPC : null
2019-09-06 14:35:09.282 [DEBUG] [al.discovery.BusGatewayUpnpDiscovery] - +==================================================
2019-09-06 14:35:09.289 [INFO ] [al.discovery.BusGatewayUpnpDiscovery] - ==OWN:UPnP== |- MH201 (BTicino S.p.A.)
2019-09-06 14:35:09.292 [WARN ] [al.discovery.BusGatewayUpnpDiscovery] - ==OWN:UPnP== device is not supported by the binding (UDN=upnp-IPscenarioModule-1_0-00035097118C)
yes exactly, I will add this device in the next release of the binding.
@massi
Ok, thanks a lot Massimo for putting Mh201 in your binding.
Thanks massimo! The problemi now is that google or alexa doesnt recognize the blinds, only as dimmer but there isnt the stop button!
But one question: what is the difference from bticino binding?
did you try to read the example for rollershutter and required tags in the README? if yes, then write on the main thread to get help from others or open a new thread…
you should first read the intro and Features of the main thread…
Yes but I’m afraid blinds in alexa are not supporter yet in Italia…
you should find in the log these lines:
COM SENDING ============>>>>>>>>>>>> *#13**15##
COM RECEIVED <<<<<<<<<<<<============ *#13**15*200##
can you copy here your lines ?
The code after 15*, 200 in the example, is the server type code.
I am interested to know which code corresponds to MH201.
where should I put this configuration?
I installed OpenHAB 2.5.0.M4 with its “binding-bticino1 - 1.14.0.M4”, plus the “Eclipse IoT Market misc-market - 2.5.0.M4” and “OpenWebNet 2.x Binding (Beta) market:binding-4138499 - 1.0”.
When I go to Inbox and press the white ‘+’ on cyan background
I got this empty screen:
and I cannot go further.
The MH201 is right connected and MyHomeSuite see it and I can configure the devices on the bus
have you Activate Dependencies?
using the Karaf console, I give the command:
feature:install openhab-transport-serial
and worked, but with command:
feature:install esh-io-transport-upnp
responded error
Hi @efa,
I just updated the installation instructions for openHAB 2.5.x:
the dependencies to be activated are:
feature:install openhab-transport-serial- and then
- for openHAB 2.4.x:
feature:install esh-io-transport-upnp
- or for openHAB 2.5.x and later:
feature:install openhab-core-io-transport-upnp
- for openHAB 2.4.x: