Mein Forum
Registrieren
Neu hier?
Baukonstruktionen
Fertighaus
Fenster
Dämmung
Dichtheit
Passivhaus
Schimmel
Energieausweis
Heizung
Pellets
Erdwärme
Warmwasser
Stromsparen
Solaranlagen
Photovoltaik
Lüftungsanlagen
Energiespartipps
Berechnungen
|
|
||
MQTT was already running and on my openhab server I can see that it connects .....  But I can´t get any data... |
||
|
||
|
So you are running a own mqtt broker on openhab? That's okey but you need to specify that ip address in NibePi config too. NibePi has an built in broker that it default publishes to, if the "Use mqtt broker" is checked, that ip address that it publishes to can be changed. If you dont need you embedded openhab broker for something else, I would advice you to use the one in NibePi, and only use the openhab client mqtt side and connect to the NibePis broker. If I remember correctly, sometimes openhab just wont receive anything when it's first started, so a restart could also resolve some issues. |
||
|
||
IT must be somethin on the nibepi, i now chack IT with an Android mqtt Client App... Ican connect to mqtt nibepi (10.11.1.162) nur i cant subscribe to a topic  |
||
|
||
|
Reliability issues I have used NibePi for a number of months now, but the RPi/Node/NodeRed/NibePi combination is not as stable as it is required for such an essential part of a home. As a result I plan to migrate this to my "proven platform" which consists of MQTT as the backbone of the smart home with added benefits implemented by reading / writing to the MQTT topics. That way a restart / failure of the RPi running NodeRed doesnt effect the basic functionality and while its running it provides "added value" like comfort functions, historical data storage, retrieval and graph/dashboard generation. I just got the ProDino MKR Zero Ethernet and got an MQTT client running on it in a matter of minutes. So, my plan is to migrate the Nibe communication code completely into the ProDino and use the MQTT client to forward status values / receive commands. Of course the number of priority is to keep the Nibe happy without alarms even if the MQTT server would be unavailable. Which implementation of the basic communication protocol is considered the most reliable at the moment? |
||
|
||
|
Tell me more about what image file you are using. The clean version that Becker uses? Can you screenshot your NibePi config page? I can agree this has been true in the past. Especially running my old 1.0.6 image. But my newer version 1.1 (only released in beta) with a full frontend solution. This has proven to be very stable and user friendly. A very Nice fella has translated most of the swedish to german lately and the newest version includes german Language for most part of the Interface. One rpi running inside with nibepi 1.1 is in my opinion very stable and "fun". You can use node-red to create your own automations running closely attached to the heatpump. No network issues will disturb the communication. At Start up it will generate an alarm but in NibePi that is checked regulary and being reset if alarm occurs. (which dosent happen under normal running mode). If there are issues Im always fixing them as fast as I can and release a new version. But.. A solution with a prodino is also a pretty good choice. Especially now when nibepi supports interfacing with nibegw (from what i have heard can be run on prodino?). I released a simple docker image about a week ago which starts a simple nibegw - mqtt server. That docker image can be run any in the network as the nibegw. If the network fails, the prodino will still ack all the messages and not raise an alarm on the heatpump. |
||
|
||
|
Its not necessarily the NibePi implementation that is causing the stability issues. While NodeRed has made greats leaps with regards to stability, it is still not fit to be an integral part of my platform. It is nice and I use it for many things, but it cannot be a crucial part. I thought about using the ProDino nibegw -> udp -> NibePi implementation, but since its very easy to get MQTT running on ProDino as well, integrating it directly makes more sense to me. I ll see how much work it will be. |
||
|
||
|
I thought about that aswell. But never really started due to time limitations. One thing I would check before you really start: you need to store info about every register (Number,Type, maybe Factor in the flash memory of the Prodino. I am not sure if that is possible, i.e. memory fits. The one from openHAB for the Nibe binding (a link to the repo is some in this thread). I guess nibePi has also been built based on this implementation. |
||
|
||
|
I use the nibepi_1.1_clean.img Do you mean this config page ?  |
||
|
||
|
No, I meant the page you checked the box "Use Mosquitto broker". You also need to specify a topic, host and port on that page. |
||
|
||
|
Ok, now I've found out ... I thought you could just call up the topics via mqtt that you wrote in log.set. But first you have to connect each register with mqtt out in the Node-Red and then it works 😀Thanks @nibepi for your support 👍  |
||
|
||
|
Actually that's the way it should work. But you found a work around. I still think there is something strange with the config. |
||
|
||
|
NibePi 1.1 is now released. Download and burn the image file to a SD-card and it will be a PnP solution with NibePi hardware. Change languages on the first page in the webinterface. German and english translation is availible but not 100% done yet. For more information https://github.com/anerdins/nibepi/blob/master/README.en.md
|
||
|
||
|
Hallo, ich habe jetzt die clean Installation von Nibepi schon eine Zeit lang in Kombination mit Loxone erfolgreich im Einsatz (Statistiken fehlen immer noch aber momentan bin ich zu faul für so etwas) Wie gestaltet sich der update Vorgang der clean Version? (dachte eigentlich das geht bequem aus node-red raus) Danke  |
||
|
||
|
If you're running the clean version you need to upgrade from ssh terminal. Run this command "sudo mount -o remount,rw / && cd /home/pi/.node-red && npm uninstall node-red-contrib-nibepi && npm install --save anerdins/node-red-contrib-nibepi#master && sudo service nodered restart" Right now there is no simple way because the npm register seems to have problem accepting my plugin.
|
||
|
||
|
thanks, that's easy enough :) now everything works fine for me |
||
|
||
|
I am using the "beta" version of 1.1. Is this the same as the mentioned clean version and therefore also the same upgrade process? Furthermore, are individual flows d with this procedure? I am using the self-designed flow of user "becker". Regards, Stefan |
||
|
||
|
If you are using Beckers Flow it's the same update procedure. It will not affect the flows. The real version with specified flows for nibepi frontend can be updates from its frontend.
|
||
|
||
|
nur noch zur Info, ich habe nodered mit den Updatescript aktualisiert dann muss man aber auch das serialport node neu installieren bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) so jetzt ist alles auf den aktuellen Stand :) |
||
|
||
|
Gibt es eigentlich eine Methode anstehende Fehlermeldungen auszulesen (habe jetzt nichts gefunden)? |
||
|
||
|
Du könntest das Alarm-Register auslesen (45001). Den Link zur Dekodiertabelle hatte ich vor einer Weile gepostet: https://www.energiesparhaus.at/forum-nibe-f1x55-alarm-180/57674 (ein bissel runtergehen, da findest du den Link)
|
||
|
||
|
Hallo, ich freue mich zu sehen, dass dieses Projekt so weit fortgeschritten ist. Vielleicht kann mir jemand die drei Fragen kurz und knapp beantworten? Vielen Dank! 1) Ist NibePi einfach ein fertiges Raspberry Image, welches "NibeGW" vorkonfiguiert enthält? (ich las früher immer etwas von "NibeGW") 2) Ich las etwas davon, dass NibePI die Daten über MQTT aussendet, diese kann ich ja mit meinem Smarthome verarbeiten (z.B. HomeAssistant oder OpenHub). Kann ich denn auch Einstellungen meiner VVM500/F2120-12 ändern (insbesondere die Lüftungseinstellungen also 50%, 100% etc.) - das würde ich hin und gerne vom Smartphone tun (ohne die Premium Mitgliedschaft..) 3) Ich glaube früher war immer von einem Arduino die Rede, jetzt wird der Raspberry Zero verwenden? Hat das einen Grund (Ethernet / WLan Anschluss...?) |
Beitrag schreiben oder Werbung ausblenden?
Einloggen
Kostenlos registrieren [Mehr Infos]