{"id":495,"date":"2024-04-22T13:24:02","date_gmt":"2024-04-22T13:24:02","guid":{"rendered":"https:\/\/geisti.de\/?p=495"},"modified":"2024-04-22T13:36:07","modified_gmt":"2024-04-22T13:36:07","slug":"venuspi-aggregate-batteries-22-04-2024","status":"publish","type":"post","link":"https:\/\/geisti.de\/index.php\/2024\/04\/22\/venuspi-aggregate-batteries-22-04-2024\/","title":{"rendered":"VenusPi Aggregate Batteries 22.04.2024"},"content":{"rendered":"\n<p><a href=\"https:\/\/github.com\/kwindrem\/SetupHelper\">https:\/\/github.com\/kwindrem\/SetupHelper<\/a><\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">wget -qO - <a href=\"https:\/\/github.com\/kwindrem\/SetupHelper\/archive\/latest.tar.gz\">https:\/\/github.com\/kwindrem\/SetupHelper\/archive\/latest.tar.gz<\/a> | tar -xzf - -C \/data\nmv \/data\/SetupHelper-latest \/data\/SetupHelper\n\/data\/SetupHelper\/setup<\/pre>\n\n\n\n<p>Und dann mit dem Helper BatteryAggregator by pulquero installieren.<br><br>Einstellungen f\u00fcr dbus-serialbattery:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>root@raspberrypi2:~# cd dbus-serialbattery\nroot@raspberrypi2:~\/dbus-serialbattery# cat config.ini\n&#91;DEFAULT]\n; --------- Set logging level ---------\n; ERROR: Only errors are logged\n; WARNING: Errors and warnings are logged\n; INFO: Errors, warnings and info messages are logged\n; DEBUG: Errors, warnings, info and debug messages are logged\nLOGGING = INFO\n\n; --------- Battery Current limits ---------\nMAX_BATTERY_CHARGE_CURRENT = 140.0\nMAX_BATTERY_DISCHARGE_CURRENT = 140.0\n\n; --------- Cell Voltages ---------\n; Description:\n; Cell min\/max voltages which are used to calculate the min\/max battery voltage\n; Example:\n; 16 cells * 3.45V\/cell = 55.2V max charge voltage. 16 cells * 2.90V = 46.4V min discharge voltage\nMIN_CELL_VOLTAGE = 2.900\n; Max voltage (can seen as absorption voltage)\nMAX_CELL_VOLTAGE = 3.450\n; Float voltage (can be seen as resting voltage) - original: 3.375\nFLOAT_CELL_VOLTAGE = 3.410\n\n; --------- SOC reset voltage ---------\n; Description:\n; May be needed to reset the SoC to 100% once in a while for some BMS, because of SoC drift.\n; Specify the cell voltage where the SoC should be reset to 100% by the BMS.\n; - JKBMS: SoC is reset to 100% if one cell reaches OVP (over voltage protection) voltage\n; As you have to adopt this value to your system, I reccomend to start with\n; OVP voltage - 0.030 (see Example).\n; - Try to increase (add) by 0.005 in steps, if the system does not switch to float mode, even if\n; the target voltage SOC_RESET_VOLTAGE * CELL_COUNT is reached.\n; - Try to decrease (lower) by 0.005 in steps, if the system hits the OVP too fast, before all\n; cells could be balanced and the system goes into protection mode multiple times.\n; Example:\n; If OVP is 3.650, then start with 3.620 and increase\/decrease by 0.005\n; Note:\n; The value has to be higher as the MAX_CELL_VOLTAGE\n; You also have to set CELL_VOLTAGES_WHILE_CHARGING accordingly, if you set CCCM_CV_ENABLE to true\n; else the charging current will be reduced to 0 before the target voltage is reached and the\n; battery will never switch to float\nSOC_RESET_VOLTAGE = 3.500\n; original: 3.650\n; Specify after how many days the soc reset voltage should be reached again\n; The timer is reset when the soc reset voltage is reached\n; Leave empty if you don't want to use this\n; Example:\n; Value is set to 15\n; day 1: soc reset reached once\n; day 16: soc reset reached twice\n; day 31: soc reset not reached since it's very cloudy\n; day 34: soc reset reached since the sun came out\n; day 49: soc reset reached again, since last time it took 3 days to reach soc reset voltage\nSOC_RESET_AFTER_DAYS =\n\n; --------- Bluetooth BMS ---------\n; Description:\n; Specify the Bluetooth BMS and it's MAC address that you want to install. Leave emty to disable\n; Available Bluetooth BMS:\n; Jkbms_Ble, LltJbd_Ble\n; Example for one BMS:\n; BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00\n; Example for multiple BMS:\n; BLUETOOTH_BMS = Jkbms_Ble C8:47:8C:00:00:00, Jkbms_Ble C8:47:8C:00:00:11, Jkbms_Ble C8:47:8C:00:00:22\nBLUETOOTH_BMS = Jkbms_Ble C8:47:8C:E2:A2:A2, Jkbms_Ble C8:47:80:01:82:59\n\n; --------- Bluetooth use USB ---------\n; Description: Some users reported issues to the built in bluetooth module, you can try to fix it with an USB\n; module. After a change you have to run reinstall-local.sh and to manual reboot the device!\n; The usb bluetooth module must have BLE support (bluetooth version >= 4.0)\n; Other bluetooth devices such as Ruuvi tags not tested yet.\n; False: Use the built in bluetooth module\n; True: Disable built in bluetooth module and try to use USB module\nBLUETOOTH_USE_USB = False\n\n; --------- CAN BMS ---------\n; Description:\n; Specify the CAN port(s) where the BMS is connected to. Leave empty to disable\n; Available CAN BMS:\n; Daly_Can, Jkbms_Can\n; Example for one CAN port:\n; CAN_PORT = can0\n; Example for multiple CAN ports:\n; CAN_PORT = can0, can8, can9\nCAN_PORT =\n\n; --------- BMS disconnect behaviour ---------\n; Description:\n; Block charge and discharge when the communication to the BMS is lost. If you are removing the\n; BMS on purpose, then you have to restart the driver\/system to reset the block.\n; False:\n; Charge and discharge is not blocked on BMS communication loss for 20 minutes, if cell voltages are between\n; 3.25 V and 3.35 V. Else the driver block charge and discharge after 60 seconds.\n; True:\n; Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established\n; again or the driver\/system is restarted. This is the Victron Energy default behaviour.\nBLOCK_ON_DISCONNECT = False\n\n; --------- Charge mode ---------\n; Choose the mode for voltage \/ current limitations (True \/ False)\n; False is a step mode: This is the default with limitations on hard boundary steps\n; True is a linear mode:\n; For CCL and DCL the values between the steps are calculated for smoother values (by WaldemarFech)\n; For CVL max battery voltage is calculated dynamically in order that the max cell voltage is not exceeded\nLINEAR_LIMITATION_ENABLE = True\n\n; Specify in seconds how often the linear values should be recalculated\nLINEAR_RECALCULATION_EVERY = 60\n; Specify in percent when the linear values should be recalculated immediately\n; Example:\n; 5 for a immediate change, when the value changes by more than 5%\nLINEAR_RECALCULATION_ON_PERC_CHANGE = 5\n\n; --------- Charge Voltage limitation (affecting CVL) ---------\n; Description:\n; Limit max charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float\n; voltage (FLOAT_CELL_VOLTAGE * cell count) and back\n; False: Max charging voltage is always kept\n; True: Max charging voltage is reduced based on charge mode\n; Step mode: After max voltage is reached for MAX_VOLTAGE_TIME_SEC it switches to float voltage. After\n; SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT it switches back to max voltage.\n; Linear mode: After max voltage is reachend and cell voltage difference is smaller or equal to\n; CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL it switches to float voltage after MAX_VOLTAGE_TIME_SEC\n; additional seconds.\n; After cell voltage difference is greater or equal to CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT\n; OR\n; SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT\n; it switches back to max voltage.\n; Example when set to True:\n; Step mode:\n; The battery reached max voltage of 55.2V and hold it for 900 seconds, the the CVL is switched to\n; float voltage of 53.6V to don't stress the batteries. Allow max voltage of 55.2V again, if SoC is\n; once below 80%\n; Linear mode:\n; The battery reached max voltage of 55.2V and the max cell difference is 0.010V, then switch to float\n; voltage of 53.6V after 900 additional seconds to don't stress the batteries. Allow max voltage of\n; 55.2V again if max cell difference is above 0.080V or SoC below 80%.\n; Charge voltage control management enable (True\/False).\nCVCM_ENABLE = True\n\n; -- CVL reset based on cell voltage diff (linear mode)\n; Specify cell voltage diff where CVL limit is kept until diff is equal or lower\nCELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL = 0.010\n; Specify cell voltage diff where MAX_VOLTAGE_TIME_SEC restarts if diff is bigger\nCELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_TIME_RESTART = 0.013\n; Specify cell voltage diff where CVL limit is reset to max voltage, if value get above\n; the cells are considered as imbalanced, if the cell diff exceeds 5% of the nominal cell voltage\n; e.g. 3.2 V * 5 \/ 100 = 0.160 V\nCELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT = 0.080\n\n; -- CVL reset based on SoC option (step mode &amp; linear mode)\n; Specify how long the max voltage should be kept\n; Step mode: If reached then switch to float voltage\n; Linear mode: If cells are balanced keep max voltage for further MAX_VOLTAGE_TIME_SEC seconds\n; original 900\nMAX_VOLTAGE_TIME_SEC = 900\n; Specify SoC where CVL limit is reset to max voltage\n; Step mode: If SoC gets below\n; Linear mode: If cells are unbalanced or if SoC gets below\nSOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 80\n\n; --------- SOC calculation ---------\n; Description:\n; Calculate the SOC in the driver. Do not use the SOC reported by the BMS\n; SOC_CALCULATION:\n; True: Calc SOC in the driver, do not use SOC reported from BMS\n; - The SOC is calculated by integration of the current reported by the BMS\n; - The current reported from the BMS can be corrected by\n; the map (SOC_CALC_CURRENT_REPORTED_BY_BMS, SOC_CALC_CURRENT_MEASURED_BY_USER)\n; - The SOC is set to 100% if the following conditions apply for at least SOC_RESET_TIME seconds:\n; * Current is lower than SOC_RESET_CURRENT amps\n; * Sum of cell voltages >= self.max_battery_voltage - VOLTAGE_DROP\n; - The calculated SOC is stored in dbus to persist a driver restart\n; False: Use SOC reported from BMS (none of the other parameters apply)\n; More info: https:\/\/github.com\/Louisvdw\/dbus-serialbattery\/pull\/868\nSOC_CALCULATION = False\nSOC_RESET_CURRENT = 7\nSOC_RESET_TIME = 60\nSOC_CALC_CURRENT_REPORTED_BY_BMS = -300, 300\nSOC_CALC_CURRENT_MEASURED_BY_USER = -300, 300\n; Example to set small currents to zero\n; SOC_CALC_CURRENT_REPORTED_BY_BMS = -300, -0.5, 0.5, 300\n; SOC_CALC_CURRENT_MEASURED_BY_USER = -300, 0, 0, 300\n\n; --------- Cell Voltage Current limitation (affecting CCL\/DCL) ---------\n; Description: Maximal charge \/ discharge current will be in-\/decreased depending on min and max cell voltages\n; Example:\n; 18 cells * 3.55V\/cell = 63.9V max charge voltage\n; 18 cells * 2.70V\/cell = 48.6V min discharge voltage\n; But in reality not all cells reach the same voltage at the same time. The (dis)charge current\n; will be (in-\/)decreased, if even ONE SINGLE BATTERY CELL reaches the limits\n\n; Charge current control management referring to cell-voltage enable (True\/False).\nCCCM_CV_ENABLE = True\n; Discharge current control management referring to cell-voltage enable (True\/False).\nDCCM_CV_ENABLE = True\n\n; Set steps to reduce battery current\n; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True\nCELL_VOLTAGES_WHILE_CHARGING = 3.55, 3.50, 3.45, 3.30\nMAX_CHARGE_CURRENT_CV_FRACTION = 0, 0.05, 0.5, 1\n\nCELL_VOLTAGES_WHILE_DISCHARGING = 2.70, 2.80, 2.90, 3.10\nMAX_DISCHARGE_CURRENT_CV_FRACTION = 0, 0.1, 0.5, 1\n\n; --------- Cell Voltage limitation (affecting CVL) ---------\n; This function prevents a bad balanced battery to overcharge the cell with the highest voltage and the bms to\n; switch off because of overvoltage of this cell.\n;\n; Example:\n; 15 cells are at 3.4v, 1 cell is at 3.6v. Total voltage of battery is 54.6v and the Victron System sees no reason to\n; lower the charging current as the control_voltage (Absorbtion Voltage) ist 55.2v\n; In this case the Cell Voltage limitation kicks in and lowers the control_voltage to keep it close to the MAX_CELL_VOLTAGE.\n;\n; In theory this can also be done with CCL, but doing it with CVL has 2 advantages:\n; - In a well balanced system the current can be kept quite high till the end of charge by using MAX_CELL_VOLTAGE for charging.\n; - In systems with MPPTs and DC-feed-in activated the victron systems do not respect CCL, so CVL is the only way to prevent the\n; highest cell in a bad balanced system from overcharging.\n;\n; There are 2 methods implemented to calculate CVL:\n; 1. penalty_sum-Method (CVL_ICONTROLLER_MODE = False)\n; The voltage-overshoot of all cells that exceed MAX_CELL_VOLTAGE is summed up and the control voltage is lowered by this \"penalty_sum\".\n; This is calculated every LINEAR_RECALCULATION_EVERY seconds.\n; In fact, this is a P-Controller.\n; 2. I-Controller (CVL_ICONTROLLER_MODE = True)\n; An I-Controller tries to control the voltage of the highest cell to MAX_CELL_VOLTAGE + CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL.\n; (for example 3.45V+0.01V =3.46V). If the voltage of the highest cell is above this level, CVL is reduced. If the voltage is below, CVL is\n; increased until cellcount*MAX_CELL_VOLTAGE.\n; An I-Part of 0.2 V\/Vs (CVL_ICONTROLLER_FACTOR) has proved to be a stable and fast controlling-behaviour.\n; This method is not as fast as the penalty_sum-Method but usually smoother and more stable against toggeling and has no stationary deviation.\n; More info: https:\/\/github.com\/Louisvdw\/dbus-serialbattery\/pull\/882\nCVL_ICONTROLLER_MODE = False\nCVL_ICONTROLLER_FACTOR = 0.2\n\n; --------- Temperature limitation (affecting CCL\/DCL) ---------\n; Description:\n; Maximal charge \/ discharge current will be in-\/decreased depending on temperature\n; Example:\n; The temperature limit will be monitored to control the currents. If there are two temperature senors,\n; then the worst case will be calculated and the more secure lower current will be set.\n; Charge current control management referring to temperature enable (True\/False).\nCCCM_T_ENABLE = True\n; Charge current control management referring to temperature enable (True\/False).\nDCCM_T_ENABLE = True\n\n; Set steps to reduce battery current\n; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True\nTEMPERATURES_WHILE_CHARGING = 0, 2, 5, 10, 15, 20, 35, 40, 55\nMAX_CHARGE_CURRENT_T_FRACTION = 0.00, 0.10, 0.20, 0.40, 0.80, 1.00, 1.00, 0.40, 0.00\n\nTEMPERATURES_WHILE_DISCHARGING = -20, 0, 5, 10, 15, 45, 55\nMAX_DISCHARGE_CURRENT_T_FRACTION = 0.00, 0.20, 0.30, 0.40, 1.00, 1.00, 0.00\n\n; --------- SOC limitation (affecting CCL\/DCL) ---------\n; Description:\n; Maximal charge \/ discharge current will be increased \/ decreased depending on State of Charge\n; Since the SoC is not as accurate as the cell voltage, this option is disabled by default\n; Example:\n; The SoC limit will be monitored to control the currents.\n; Charge current control management enable (True\/False).\nCCCM_SOC_ENABLE = False\n; Discharge current control management enable (True\/False).\nDCCM_SOC_ENABLE = False\n\n; Set steps to reduce battery current\n; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True\nSOC_WHILE_CHARGING = 98, 95, 90, 85\nMAX_CHARGE_CURRENT_SOC_FRACTION = 0.10, 0.20, 0.50, 1.00\n\nSOC_WHILE_DISCHARGING = 5, 10, 15, 20\nMAX_DISCHARGE_CURRENT_SOC_FRACTION = 0.10, 0.20, 0.50, 1.00\n\n; --------- Time-To-Go ---------\n; Description:\n; Calculates the time to go shown in the GUI\n; Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY\nTIME_TO_GO_ENABLE = True\n\n; --------- Time-To-Soc ---------\n; Description:\n; Calculates the time to a specific SoC\n; Example:\n; TIME_TO_SOC_POINTS = 50, 25, 15, 0\n; 6h 24m remaining until 50% SoC\n; 17h 36m remaining until 25% SoC\n; 22h 5m remaining until 15% SoC\n; 28h 48m remaining until 0% SoC\n; Set of SoC percentages to report on dbus and MQTT. The more you specify the more it will impact system performance.\n; &#91;Valid values 0-100, comma separated list. More that 20 intervals are not recommended]\n; Example: TIME_TO_SOC_POINTS = 100, 95, 90, 85, 75, 50, 25, 20, 10, 0\n; Leave empty to disable\nTIME_TO_SOC_POINTS =\n; Specify TimeToSoc value type &#91;Valid values 1, 2, 3]\n; 1 Seconds\n; 2 Time string d h m s\n; 3 Both seconds and time string \" &#91;d h m s]\"\nTIME_TO_SOC_VALUE_TYPE = 1\n; Specify in seconds how often the TimeToSoc should be recalculated\n; Minimum are 5 seconds to prevent CPU overload\nTIME_TO_SOC_RECALCULATE_EVERY = 60\n; Include TimeToSoC points when moving away from the SoC point &#91;Valid values True, False]\n; These will be as negative time. Disabling this improves performance slightly\nTIME_TO_SOC_INC_FROM = False\n\n; --------- Additional settings ---------\n; Specify one or more BMS types to load else leave empty to try to load all available\n; Available BMS:\n; Daly, Ecs, HeltecModbus, HLPdataBMS4S, Jkbms, Lifepower, LltJbd, Renogy, Seplos\n; Available BMS, but disabled by default (just enter one or more below and it will be enabled):\n; ANT, MNB, Sinowealth\nBMS_TYPE = Jkbms\n\n; Exclute this serial devices from the driver startup\n; Example:\n; \/dev\/ttyUSB2, \/dev\/ttyUSB4\nEXCLUDED_DEVICES =\n\n; Auto reset SoC\n; If on, then SoC is reset to 100%, if the value switches from absorption to float voltage\n; Currently only working for Daly BMS and JKBMS BLE\nAUTO_RESET_SOC = True\n;;;;;;;;;; war True\n\n; Publish the config settings to the dbus path \"\/Info\/Config\/\"\nPUBLISH_CONFIG_VALUES = True\n\n; Select the format of cell data presented on dbus &#91;Valid values 0,1,2,3]\n; 0 Do not publish all the cells (only the min\/max cell data as used by the default GX)\n; 1 Format: \/Voltages\/Cell (also available for display on Remote Console)\n; 2 Format: \/Cell\/#\/Volts\n; 3 Both formats 1 and 2\nBATTERY_CELL_DATA_FORMAT = 1\n\n; Simulate Midpoint graph (True\/False).\nMIDPOINT_ENABLE = False\n\n; Battery temperature\n; Specify how the battery temperature is assembled\n; 0 Get mean of temperature sensor 1 to sensor 4\n; 1 Get only temperature from temperature sensor 1\n; 2 Get only temperature from temperature sensor 2\n; 3 Get only temperature from temperature sensor 3\n; 4 Get only temperature from temperature sensor 4\nTEMP_BATTERY = 0\n\n; Temperature sensor 1 name\nTEMP_1_NAME = Temp 1\n\n; Temperature sensor 2 name\nTEMP_2_NAME = Temp 2\n\n; Temperature sensor 2 name\nTEMP_3_NAME = Temp 3\n\n; Temperature sensor 2 name\nTEMP_4_NAME = Temp 4\n\n; --------- BMS specific settings ---------\n\n; -- LltJbd settings\n; SoC low levels\n; Note:\n; SOC_LOW_WARNING is also used to calculate the Time-To-Go even if you are not using a LltJbd BMS\nSOC_LOW_WARNING = 20\nSOC_LOW_ALARM = 10\n\n; -- Daly settings\n; Battery capacity (amps), if the BMS does not support reading it\n;;;;;BATTERY_CAPACITY = 280\n; Invert Battery Current. Default non-inverted. Set to -1 to invert\n;;;;;INVERT_CURRENT_MEASUREMENT = 1\n\n; -- JKBMS settings\n; Predefines cell count for Jkbms_can\n; The cell count should be auto-detected by identifying the highest cell number,\n; but this process may be sometimes slow what could cause that cells voltage is not not\n; updated in VenusOS. Try this workaround if you experience problems with cell voltage.\nJKBMS_CAN_CELL_COUNT = 1\n\n; -- ESC GreenMeter and Lipro device settings\n;;;;;GREENMETER_ADDRESS = 1\n;;;;;LIPRO_START_ADDRESS = 2\n;;;;;LIPRO_END_ADDRESS = 4\n;;;;;LIPRO_CELL_COUNT = 15\n\n; -- HeltecModbus (Heltec SmartBMS\/YYBMS) settings\n; Set the Modbus addresses from the adapters\n; Separate each address to check by a comma like: 1, 2, 3, \u2026\n; factory default address will be 1\n;;;;;HELTEC_MODBUS_ADDR = 1\n\n; --------- Voltage drop ---------\n; If you have a voltage drop between the BMS and the charger because of wire size or length\n; then you can specify the voltage drop here. The driver will then add the voltage drop\n; to the calculated CVL to compensate.\n; Example:\n; cell count: 16\n; MAX_CELL_VOLTAGE = 3.45\n; max voltage calculated = 16 * 3.45 = 55.20\n; CVL is set to 55.20 V and the battery is now charged until the charger reaches 55.20 V.\n; The BMS now measures 55.05 V since there is a voltage drop of 0.15 V on the cable.\n; Since the dbus-serialbattery reads the voltage of 55.05 V from the BMS the max voltage\n; of 55.20 V is never reached and max voltage is kept forever.\n; By setting the VOLTAGE_DROP to 0.15 V the voltage on the charger is increased and the\n; target voltage on the BMS is reached.\nVOLTAGE_DROP = 0.00<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"<p>https:\/\/github.com\/kwindrem\/SetupHelper wget -qO &#8211; https:\/\/github.com\/kwindrem\/SetupHelper\/archive\/latest.tar.gz | tar -xzf &#8211; -C \/data mv \/data\/SetupHelper-latest \/data\/SetupHelper \/data\/SetupHelper\/setup Und dann mit dem Helper BatteryAggregator by pulquero installieren. Einstellungen f\u00fcr dbus-serialbattery:<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-495","post","type-post","status-publish","format-standard","hentry","category-computergedingens"],"_links":{"self":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts\/495","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/comments?post=495"}],"version-history":[{"count":6,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts\/495\/revisions"}],"predecessor-version":[{"id":501,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/posts\/495\/revisions\/501"}],"wp:attachment":[{"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/media?parent=495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/categories?post=495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geisti.de\/index.php\/wp-json\/wp\/v2\/tags?post=495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}