Neueste Beiträge

#1

Sonstige Systeme / Aw: fhempy: tuya (lokal)

Letzter Beitrag von cyrusfd - 27 April 2024, 09:20:58

Hallo,

ich kann meine Wärmepumpe (BWT) über Set steuern, bekomme aber keine aktualisierten Readings. In meiner Tuya-App auf dem Handy bzw auf der WP sieht man direkt die Eingaben über Fhem.
Nur bei einem Neustart des Fhempy-Servers werden die Readings aktualisiert.

Code Auswählen Erweitern

2024-04-27 03:30:27,090 - ERROR    - websocket: ping/pong timed out - goodbye
2024-04-27 03:30:38,457 - INFO     - websocket: Websocket connected
2024-04-27 06:56:51,515 - INFO     - fhempy.lib.fhem_pythonbinding: Start update...
2024-04-27 06:56:51,518 - INFO     - fhempy.lib.pkg_installer: Attempting install of fhempy
2024-04-27 06:57:16,897 - INFO     - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2024-04-27 06:57:16,910 - INFO     - fhempy.lib.fhem_pythonbinding: Restart initiated...
2024-04-27 06:57:16,912 - INFO     - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2024-04-27 06:57:16,912 - INFO     - websockets.server: server closing
2024-04-27 06:57:26,926 - INFO     - websockets.server: connection closed
2024-04-27 06:57:26,927 - INFO     - websockets.server: server closed
2024-04-27 06:57:26,935 - INFO     - fhempy.lib.fhem_pythonbinding: Exit 1
Activating virtual environment...OK
2024-04-27 06:57:28,818 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 06:57:28,821 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 06:57:28,881 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 06:57:38,815 - INFO     - websockets.server: connection open
2024-04-27 06:57:38,817 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 06:57:40,889 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
Activating virtual environment...OK
2024-04-27 07:26:59,289 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 07:26:59,294 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 07:26:59,388 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 07:26:59,802 - INFO     - websockets.server: connection open
2024-04-27 07:26:59,803 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 07:27:01,601 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
2024-04-27 07:30:40,802 - INFO     - fhempy.lib.fhem_pythonbinding: Restart initiated...
2024-04-27 07:30:40,805 - INFO     - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2024-04-27 07:30:40,806 - INFO     - websockets.server: server closing
2024-04-27 07:30:50,822 - INFO     - websockets.server: connection closed
2024-04-27 07:30:50,823 - INFO     - websockets.server: server closed
2024-04-27 07:30:50,829 - INFO     - fhempy.lib.fhem_pythonbinding: Exit 1
Activating virtual environment...OK
2024-04-27 07:30:52,712 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 07:30:52,714 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 07:30:52,774 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 07:31:03,259 - INFO     - websockets.server: connection open
2024-04-27 07:31:03,261 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 07:31:04,864 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
2024-04-27 08:05:45,409 - ERROR    - tuya_cloud_connector: Tuya login error response: {'code': 1106, 'msg': 'permission deny', 'success': False, 't': 1714197945384, 'tid': '2f89ac47045c11efb2424a20391ad943'}
Activating virtual environment...OK
2024-04-27 08:06:15,988 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 08:06:15,991 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 08:06:16,052 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 08:06:19,169 - INFO     - websockets.server: connection open
2024-04-27 08:06:19,171 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 08:06:20,841 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
2024-04-27 08:33:23,647 - INFO     - fhempy.lib.fhem_pythonbinding: Shutdown initiated...
2024-04-27 08:33:23,650 - INFO     - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2024-04-27 08:33:23,651 - INFO     - websockets.server: server closing
Activating virtual environment...OK
2024-04-27 08:33:29,885 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 08:33:29,887 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 08:33:29,947 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 08:33:39,768 - INFO     - websockets.server: connection open
2024-04-27 08:33:39,770 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 08:33:42,610 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
Activating virtual environment...OK
2024-04-27 08:39:05,999 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 08:39:06,002 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 08:39:06,063 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 08:39:09,151 - INFO     - websockets.server: connection open
2024-04-27 08:39:09,153 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 08:39:11,091 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
2024-04-27 08:56:31,146 - INFO     - fhempy.lib.pkg_installer: Attempting install of git+https://github.com/fhempy/aiotinytuya#aiotinytuya==1.12.3
2024-04-27 08:56:49,029 - INFO     - fhempy.lib.pkg_installer: Successfully installed git+https://github.com/fhempy/aiotinytuya#aiotinytuya==1.12.3 update!
2024-04-27 09:00:25,737 - INFO     - fhempy.lib.fhem_pythonbinding: Start update...
2024-04-27 09:00:25,739 - INFO     - fhempy.lib.pkg_installer: Attempting install of fhempy
2024-04-27 09:00:50,755 - INFO     - fhempy.lib.pkg_installer: Successfully installed fhempy update!
2024-04-27 09:00:50,773 - INFO     - fhempy.lib.fhem_pythonbinding: Restart initiated...
2024-04-27 09:00:50,775 - INFO     - fhempy.lib.fhem_pythonbinding: All modules successfully undefined!
2024-04-27 09:00:50,776 - INFO     - websockets.server: server closing
2024-04-27 09:01:00,783 - INFO     - websockets.server: connection closed
2024-04-27 09:01:00,784 - INFO     - websockets.server: server closed
2024-04-27 09:01:00,793 - INFO     - fhempy.lib.fhem_pythonbinding: Exit 1
Activating virtual environment...OK
2024-04-27 09:01:02,674 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 09:01:02,678 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 09:01:02,739 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 09:01:11,532 - INFO     - websockets.server: connection open
2024-04-27 09:01:11,533 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 09:01:14,471 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details
Activating virtual environment...OK
2024-04-27 09:10:40,053 - INFO     - fhempy.lib.fhem_pythonbinding: Starting fhempy 0.1.740...
2024-04-27 09:10:40,055 - INFO     - fhempy.lib.fhem_pythonbinding: Waiting for FHEM connection
2024-04-27 09:10:40,115 - INFO     - websockets.server: server listening on 0.0.0.0:15733
2024-04-27 09:10:43,237 - INFO     - websockets.server: connection open
2024-04-27 09:10:43,239 - INFO     - fhempy.lib.fhem_pythonbinding: Incoming FHEM connection: 127.0.0.1
2024-04-27 09:10:46,444 - INFO     - websocket: Websocket connected
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 158, in run
    self.__run_mqtt()
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 172, in __run_mqtt
    mqttc = self._start(mq_config)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/tuya_iot/openmq.py", line 179, in _start
    mqttc = mqtt.Client(mq_config.client_id)
  File "/opt/fhem/.fhempy/fhempy_venv/lib/python3.9/site-packages/paho/mqtt/client.py", line 766, in __init__
    raise ValueError(
ValueError: Unsupported callback API version: version 2.0 added a callback_api_version, see migrations.md for details

#2

Wallboxen / Aw: Tinkerforge WARP3

Letzter Beitrag von Jojo11 - 27 April 2024, 09:12:59

Das Auslesen per Modbus klappt schon mal. Anbei der Code falls es jemand testen möchte (habe noch kein Auto zum Testen). Ist noch nicht alles implementiert und die Bezeichnungen sind auch noch nicht einheitlich, aber zum Testen ist es ok.
In der WARP muss natürlich das Auslesen (+evtl. Schreiben) per Modbus aktiviert werden.

Code Auswählen Erweitern

define warp3 ModbusAttr 1 60 xxx.xxx.xxx.xxx:502 TCP
attr warp3 dev-h-combine 5
attr warp3 dev-h-defPoll 1
attr warp3 dev-i-combine 5
attr warp3 dev-i-defPoll 1

attr warp3 dev-type-FLOAT16-len 2
attr warp3 dev-type-FLOAT16-unpack f>
attr warp3 dev-type-FLOAT32-len 4
attr warp3 dev-type-FLOAT32-unpack f>
attr warp3 dev-type-FLOAT32-format %.2f
attr warp3 dev-type-FLOAT64-len 4
attr warp3 dev-type-FLOAT64-unpack l
attr warp3 dev-type-SIGNED16-len 1
attr warp3 dev-type-SIGNED16-unpack n!
attr warp3 dev-type-STRING17-len 17
attr warp3 dev-type-STRING17-unpack Z*
attr warp3 dev-type-STRING5-len 5
attr warp3 dev-type-STRING5-unpack Z*
attr warp3 dev-type-UNSIGNED16-len 1
attr warp3 dev-type-UNSIGNED16-unpack S>
attr warp3 dev-type-UNSIGNED32-len 2
attr warp3 dev-type-UNSIGNED32-unpack L>
attr warp3 dev-type-UNSIGNED64-len 4
attr warp3 dev-type-UNSIGNED64-unpack Q>

attr warp3 obj-h1002-reading Erlaubter_Ladestrom
attr warp3 obj-h1002-type UNSIGNED32

attr warp3 obj-i0-reading Version_Registertabelle
attr warp3 obj-i0-type UNSIGNED32
attr warp3 obj-i2-reading Firmware-Version_Major
attr warp3 obj-i2-type UNSIGNED32
attr warp3 obj-i4-reading Firmware-Version_Minor
attr warp3 obj-i4-type UNSIGNED32
attr warp3 obj-i6-reading Firmware-Version_Patch
attr warp3 obj-i6-type UNSIGNED32
attr warp3 obj-i12-reading Uptime_s
attr warp3 obj-i12-type UNSIGNED32
attr warp3 obj-i1000-reading IEC-61851-Zustand
attr warp3 obj-i1000-type UNSIGNED32
attr warp3 obj-i1000-map 0:A, 1:B, 2:C, 3:D, 4:E/F
attr warp3 obj-i1002-reading Ladestatus
attr warp3 obj-i1002-type UNSIGNED32
attr warp3 obj-i1002-map 0:Nicht verbunden, 1:Warte auf Freigabe, 2:Lade�bereit, 3:Lädt, 4:Fehler
attr warp3 obj-i1008-reading Ladedauer_s
attr warp3 obj-i1008-type UNSIGNED32
attr warp3 obj-i1010-reading Erlaubter_Ladestrom
attr warp3 obj-i1010-type UNSIGNED32
attr warp3 obj-i2000-reading Stromzähler_Typ
attr warp3 obj-i2000-type UNSIGNED32
attr warp3 obj-i2000-map 0:Kein Strom�zähler, 1:SDM72, 2:SDM630, 3:SDM72 V2
attr warp3 obj-i2002-reading Ladeleistung_W
attr warp3 obj-i2002-type FLOAT32
attr warp3 obj-i2004-reading Ladeenergie_gesamt_kWh
attr warp3 obj-i2004-type FLOAT32
attr warp3 obj-i2008-reading Ladeenergie_aktuell_kWh
attr warp3 obj-i2008-type FLOAT32
attr warp3 obj-i2100-reading Spannung_L1
attr warp3 obj-i2100-type FLOAT32
attr warp3 obj-i2102-reading Spannung_L2
attr warp3 obj-i2102-type FLOAT32
attr warp3 obj-i2104-reading Spannung_L3
attr warp3 obj-i2104-type FLOAT32
attr warp3 obj-i2106-reading Strom_L1
attr warp3 obj-i2106-type FLOAT32
attr warp3 obj-i2108-reading Strom_L2
attr warp3 obj-i2108-type FLOAT32
attr warp3 obj-i2110-reading Strom_L3
attr warp3 obj-i2110-type FLOAT32
attr warp3 obj-i2112-reading Wirkleistung_L1
attr warp3 obj-i2112-type FLOAT32
attr warp3 obj-i2114-reading Wirkleistung_L2
attr warp3 obj-i2114-type FLOAT32
attr warp3 obj-i2116-reading Wirkleistung_L3
attr warp3 obj-i2116-type FLOAT32
attr warp3 obj-i2118-reading Scheinleistung_L1
attr warp3 obj-i2118-type FLOAT32
attr warp3 obj-i2120-reading Scheinleistung_L2
attr warp3 obj-i2120-type FLOAT32
attr warp3 obj-i2122-reading Scheinleistung_L3
attr warp3 obj-i2122-type FLOAT32
attr warp3 obj-i2124-reading Blindleistung_L1
attr warp3 obj-i2124-type FLOAT32
attr warp3 obj-i2126-reading Blindleistung_L2
attr warp3 obj-i2126-type FLOAT32
attr warp3 obj-i2128-reading Blindleistung_L3
attr warp3 obj-i2128-type FLOAT32
attr warp3 obj-i2130-reading Leistungsfaktor_L1
attr warp3 obj-i2130-type FLOAT32
attr warp3 obj-i2132-reading Leistungsfaktor_L2
attr warp3 obj-i2132-type FLOAT32
attr warp3 obj-i2134-reading Leistungsfaktor_L3
attr warp3 obj-i2134-type FLOAT32
attr warp3 obj-i2136-reading Relative_Phasenverschiebung_L1
attr warp3 obj-i2136-type FLOAT32
attr warp3 obj-i2138-reading Relative_Phasenverschiebung_L2
attr warp3 obj-i2138-type FLOAT32
attr warp3 obj-i2140-reading Relative_Phasenverschiebung_L3
attr warp3 obj-i2140-type FLOAT32
attr warp3 obj-i2142-reading Durchschnittliche_Spannung_gegen_Neutral
attr warp3 obj-i2142-type FLOAT32
attr warp3 obj-i2158-reading Frequenz
attr warp3 obj-i2158-type FLOAT32
attr warp3 obj-i2170-reading Transportierte_elektrische_Ladung
attr warp3 obj-i2170-type FLOAT32

attr warp3 room Solar
attr warp3 verbose 3
attr warp3 event-on-change-reading .*
attr warp3 event-on-update-reading .*

Gruß
Jojo

#3

Automatisierung / Aw: [ASC] - Merkwürdiges Venti...

Letzter Beitrag von CoolTux - 27 April 2024, 09:09:33

Besser ASC debug 1 und verbose auf 5

#4

Automatisierung / Aw: Idee und Ratsuche für Umse...

Letzter Beitrag von frober - 27 April 2024, 08:53:10

HTTPMOD könnte evtl. eine Lösung sein.

#5

Solaranlagen / Aw: 76_SolarForecast - Informa...

Letzter Beitrag von Dracolein - 27 April 2024, 08:25:26

Zeig bitte auch noch deinen Eintrag im SF vom Setting des "currentInverterDev"

Bei mir steht z.B. dort ein Summendummy (Ermittelt die Summe Aller Zähler =>> für alle WR !!!)
Ähnlich wie bei Dir

Code Auswählen Erweitern

InverterDummy pv=total_pac:kW etotal=etotal:kWh capacity=9500

Gruß
300P

currentInverterDev
SMATripower6 pv=PV_Gesamterzeugung:W etotal=PV_Gesamtertrag:Wh capacity=12260

Das ist seit Ewigkeiten unberührt...

#6

Unterstützende Dienste / Aw: 95_Shares.pm erweitert um ...

Letzter Beitrag von Jamo - 27 April 2024, 08:21:34

Hallo Torsten, Mumpitzstuff,
ja, ich habe AdGuard - nach setzen der Whitelist gehts jetzt auch bei mir.

Danke an alle!

#7

Bastelecke / Aw: tablet-ui

Letzter Beitrag von frober - 27 April 2024, 08:04:39

Falsches Unterforum. TabletUI ist ein Frontend, Thema Bastelecke passt hier nicht.

Du kannst es selbst unten verschieben.

#8

Homematic / Umzug der RaspberryMatic &HMCC...

Letzter Beitrag von coolice - 27 April 2024, 07:52:31

Guten Morgen zusammen, ich hatte seit einigen Jahren RaspberryMatic auf einem Raspi am laufen und in Verbindung mit einer HMCCU lief das auch 1a.
Nun habe ich den Raspi aussortiert und auf meiner Synology Homeassistant und in dieser RaspberryMatic installiert. Beides läuft, doch ich bekomme die HMCCU nicht ans laufen. Ich habe die IP natürlich angepasst un im Log steht

Code Auswählen Erweitern

2024.04.27 07:42:55 2: HMCCU [HMCCU] RPC server start: 0 started, 0 already running, 0 failed to start
2024.04.27 07:42:55 1: HMCCU [HMCCU] HMCCU: HMCCU Start of RPC server failed Habe im Wiki nochmal nachgelesen und keinen Anhaltspunkt gesehen.Im www habe ich irgendwo gelesen, das man virtuellen Maschinen die Port eintragen muss. Also habe ich

Code Auswählen Erweitern

attr rpcserverport
2001+2001+(10*1) = 7010 gesetzt. Leider auch ohne Erfolg. Kann mir einer auf die Sprünge helfen?

[Revision 28824: controls_fhem.txt: fhemupdate checkin]

#9

FHEM Code changes / Revision 28824: controls_fhem....

Letzter Beitrag von System - 27 April 2024, 07:50:52

Revision 28824: controls_fhem.txt: fhemupdate checkin

controls_fhem.txt: fhemupdate checkin

Source: Revision 28824: controls_fhem.txt: fhemupdate checkin

#10

Sonstiges / Aw: DBLOG / Vorschlag für Ände...

Letzter Beitrag von Tomk - 27 April 2024, 06:52:07

Ich habe "convertTimezone" für DbLog mal ausprobiert. Allerdings werden die svgs in fhem dann nicht mehr korrekt dargestellt, oder? Gibt es eine Lösung welche weiterhin parallelbetrieb von svg und grafana erlaubt?