I don’t know how much the nefit and the bosch protocol are alike, but in the mean time I have a basic binding for it here.
The communication and encryption parts are working, which was the touch part.
I also tried to document the protocol so it is easier to implement
Is the Bosch similar? If yes, maybe it I’d as simple as changing the server names etc.
The binding is still quite a hack, I’ll post it once more cleaned
I am an OH2 beginner and also have a Nefit-Easy and would like some more information about the possible present and how to handle it, with some examples of, for example, the Sitemap ed.
(I’m also a Dutch user who will make it easier?)
With best regards,
Cor.
For now, my binding is not ready enough for sharing…It got bit delayed as I am developing the Xiaomi Mi binding.
Hence you can use link in the above mails to import data to OH. ( GitHub - robertklep/nefit-easy-client: Nefit Easy™ client for Node.js)
Will share the binding in the marketplace and provide some samples once mine ready for general testing.
hi @loovanloon
There is no download of jar available atm, you will need to download and compile yourself.
Once bit further, I’ll make it available via the market place, but given that little error handling, little functionality is there I see it more as a developer version than an user version.
@shorty707 the development I did is specifically for the nefit easy thermostat.
as I understood it has many similarities, but I have not checked it, nor made any attempts to support a wider range.
As soon as it is somewhat usable, I’ll make a separate thread for it to avoid the confusion.
I think @hakan is aiming to make a more elaborate binding focussed on supporting devices from the bosch smart home eco system
Since some days before Christmas there is a description of the Bosch Smarthome REST-API available - but so far only Bosch internal.
I asked when it will be made available public.
Because here is asked for two different systems:
Bosch smart home and BSH Home Connect:
I try to implement a Bosch Home Connect binding for the household devices at the moment.
Hi @stfn82 unfortunately I was not able to make the sending of commands messaging working in the same way the device expects.
The libs (smack) I used send valid messages, whereas the device expects some non-standard behavior I did not manage to replicate. (it is mainly in the way & signs are coded and the CR & LF’s. If smack lib allowed to do a replace of & and CR’s I would be fine)
Receiving & decrypting is fine, the strangeness of the messages can be worked around, but sending messages that don’t adhere to the standard, I did not manage.