I debugged and enhanced the Bticino Binding for my use in several categories,
as Heating Control, Automation, Door Entry, Dimmers.
Heating:
added full control to single probes / zones
added full control for Main Control Unit
Automation:
corrected OWN feedback which caused binding to crash
added virtual calculated position feedback based on the runtime of the shutter (has to be pre-configured in the cfg)
the virtual position feedback makes it possible to control the shutter via the HOMEKIT Binding
(but please be aware that 0-100 % (open / closed) is reverted in Homekit
Can’t really give you a answer on that, as I don’t have a 300x13e Wifi,
only have Gateway F454 & Multimedia Touch Screen 4690 to test.
But the mayor requirement is that you have a OWN gateway F454 or F453AV which can supply the video jpeg.
If the Door Entry System is accessible there it should work for OpenHAB too.
If I understand the manual of the 300x13e Wifi correct it has no OWN (OpenWebNet … the Bticino Bus Protokoll) capability. So it will work only with a gateway with OpenHAB.
Reading your extension, you are getting the video signal from the gateway using its IP address. In this case how could I get both video signals from my two cameras? Do you have an idea?
where;
40 … door entry ?? not sure get it from a long search at the internet
00 … address
May you can try it with your camera, as I only have a front door camera to test
It could may look like this for your add. camera:
Switch Camera_Surveilance {bticino=“if=default;who=6;what=0;where=4001”}
for the sitemap:
Image url=“http://x.x.x.x/JPEGgrab.cgi” label=“active Camera” refresh=500
Hi Reinhard,
I would be interested in testing the modified binding but despite countless attempts I could not complete the installation.
Following the online guides, I have performed the following steps:
Uninstall the official bindings through PaperUI;
Copied the org.openhab.binding.bticino-1.11.jar file to the $openHAB-share\openhab2-addons directory;
Hi Reinhard,
I solved the problem. When I uninstall bticino bindings via PaperUI, the 1.x compatibility layer will be uninstalled and so your modified binding does not work. I solved by installing the official bindings via PaperUI and removing it via the console.
Now the modified binding is active.
Unfortunately I have a problem with some of the WHERE addresses.
In the log file I’ve found many error like this one:
2018-03-12 13:28:48.488 [ERROR] [nding.bticino.internal.BticinoDevice] - Gateway [MH200N], Error processing receiveCommand '[For input string: "64#4#01"
It seems that your mod bindings don’t recognize the “where” on a local bus.
If you upload the source code of the binding I will try to resolve this issue.
The error describes that the OWN Command can’t be interpreted in general.
Should not be an result of my additions, as I didn’t changed the principal code.
Anyway some weird Bticino code. Some idea for what it stand? Is it local bus?
If it is, the basic binding is not supporting it by now.
May you can activate the debug to get more detailed logging.
Yes, it’s a local bus address.
If I use the standard binding I can control all light and shutter (who=1,2) and only a little part of termoregulation (who=4) with main and local address. Sadly the monitor don’t work so I can’t have the states of items and I can only read the temperature.
With your addition I lost the control of the local address but the monitor works well on all bus (main and local).
Today I will some test with a debug log and if I find something I will prompt to you.
Regards Giovanni
Got it, I guess I already knew what is the issue.
I added a int variable for the address (where) for my new part of the roller shutter functionality
which make trouble when the where is not only a simple number.
not an issue in principal. Do you have the source code for this addition?
If not I can try to decompile the java class.
But first I would soon approach the maintainer of the plugin to add my additions to the official distribution, as I have quite a good response from the community.
Then as a next step I can add the CEN ++ functionality, so I do not mess up the actual process.
Hi Reinhard,
When i pressed the button for the door lock on the videophone, the status for the door lock in events logs on openhab is not present.
I’m create a rules for the door lock and a light.
When i pressed for the button in openhab, it’s work fine, but whan i pressed the button in my videophone it’snt work.
rule “Portail1”
when
Item Portail_1 received command ON
then
sendCommand(Centre_1, ON)
Thread::sleep(10000)
sendCommand(Centre_1, OFF)
end
unfortunately the functionality to unlock the door is not well documented by Bticino,
It was quite a hack to get the command to be working.
Additionally there is a lot of feedback on the Bticino bus after you press the i.e. the door lock on the videophone, or even actually when you activate the door lock by OpenHAB.
I will need some more time to investigate this, therefore actually only the possibility to open the lock from OpenHAB is implemented. No feedback by now. So your rule can’t be working.
But it’s on my bullet list. May take a while to get a fully working solution.
