Interface > Interface til varme systemer

integration med hass.io

<< < (3/4) > >>

John Doe:

--- Citat fra: motoz efter Okt 25, 2020, 12:18 ---
--- Citér ---The Raspberry Pi is installed with the Home Assistant OS,
--- Afslutning på citat ---
I see. Of course if you start with an OS purpose build to run only one application then it's going to be hard/impossible to do anything else. Home assistant however is (just like pellmon) nothing more than a bunch of python scripts, so nothing prevents you from starting with a general purpose OS instead and install everything that you need on the same computer. Including the broker, of course. If you want to keep the HA OS, then an extra raspberry zero for the broker and pellmon isn't exactly expensive.

--- Afslutning på citat ---

Well, I guess not...  :D

Jre:

--- Citat fra: John Doe efter Okt 25, 2020, 07:37 ---
--- Citat fra: motoz efter Okt 23, 2020, 09:06 ---I don't see why you couldn't run PellMon and PellmonMQTT together with Home Assistant on the same rpi. Do you think of some specific reason?

--- Afslutning på citat ---

The Raspberry Pi is installed with the Home Assistant OS, and is not accessible in any other way than through HA. How would you install another program, without mentioning a broker?

--- Afslutning på citat ---

That is not entirely true.  It is true that the HassOS is build for running HA, but it is still a Linux distro that is just made inaccessible for the user (e.g., ssh to the host os is disabled), as stuff should be running in containers, which makes the OS installation independent and easy to upgrade without breaking any add-ons.

I haven't spent any time reading up on integrations, but a quick glance suggests that they are just python3 code.  So unless Pellmon uses anything else than python for fetching and/or setting values in the controller then it should be fairly straight forward to wrap it and expose directly.

Another alternative could be to just wrap the pellmon software in a container and expose it as an add-on, however that would not integrate the values directly to HA.  Then you would need the pellmon-mqtt, and then connect that to your HA's mqtt broker, i guess?

Jre:
In fact this link would suggest that it is actually a requirement to use a third party library for the actual device coms, when creating an integration in HA: https://developers.home-assistant.io/docs/creating_platform_index#interfacing-with-devices
It just needs to be available at PyPi, which doesn't seem to be the case right now (but could easily be done).

Ah any listed requirements is just passed along to pip so a git+https:// urls is possible, thus no PyPi is strictly needed: https://developers.home-assistant.io/docs/creating_integration_manifest#custom-requirements-during-development--testing

It even seems possible to implement either pulling or pushing of new values to HA: https://developers.home-assistant.io/docs/core/entity/#updating-the-entity
If the values very only published by mqtt, you could even auto discover them: https://developers.home-assistant.io/docs/creating_integration_manifest#mqtt
However I guess it would be cleaner to expose entities directly, and then use the HA mqtt broker/node-red to export any values if you really need them externally, as you most likely just want the values inside HA and no where else?

John Doe:
@Jre it would be very nice to have the values exposed to HA as entities, even if they're not editable. But I'm not a programmer. At all. I would'nt have the slightest idea on how to do it!

motoz:
The PellMon plugin for V7/13 burners  is called NBEcom, it uses the NBEprotocol python module for communicating with the burner. It's a pure python module, but like the rest of PellMon it's python 2, not python3: https://github.com/motoz/PellMon/tree/master/src/Pellmonsrv/plugins/nbecom/nbeprotocol

It should be straightforward to port this python3 and make something for HA out of it. Doing it this way you will not get access to everything else that PellMon provides besides access to the basicburner settings, but nothing prevents running several clients with the burner controller at the same time so pellmon can very well exist side by side with an HA integration and the official android app. I will of course try to support any effort made to make an HA integration out of the NBEprotocol, but myself I don't really understand the point... Maybe someone could change my mind... :-)

Navigering

[0] Emneindeks

[#] Næste side

[*] Forrige side