iobroker.bydhvs 1.3.0 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/CHANGELOG_OLD.md +27 -17
  2. package/README.md +26 -21
  3. package/io-package.json +15 -2
  4. package/main.js +953 -828
  5. package/package.json +17 -17
package/CHANGELOG_OLD.md CHANGED
@@ -1,8 +1,16 @@
1
1
  # Older changes
2
+ ## 1.2.2-0 (2021-05-30)
3
+ * Create States for Diagnose-Data only if necessary
4
+ * changes according review of the adapter
5
+
6
+ ## 1.2.2-0 (2021-05-30)
7
+ * Create States for Diagnose-Data only if necessary
8
+ * changes according review of the adapter
9
+
2
10
  ## 1.2.1 (2021-05-20)
3
11
  * Power is now fixed with 2 number after the decimal point
4
- * bug removed, cell voltage for cell 64 works now
5
-
12
+ * bug removed, cell voltage for cell 64 works now
13
+
6
14
  ## 1.2.0 (2021-05-15)
7
15
  * preparation for being listed in official repository
8
16
  * English part in readme.md
@@ -13,9 +21,8 @@
13
21
  * New: type of battery
14
22
  * compatibility with new js-controller 3.3
15
23
  * compatibility with nodejs 15
16
- * compatibility with admin UI 5
17
-
18
-
24
+ * compatibility with admin UI 5
25
+
19
26
  ## 1.1.0 (2021-04-22)
20
27
  * HVS-Version with two banks and - hopefully - correct display
21
28
  * states are now with units, the existing states are changed
@@ -24,23 +31,26 @@
24
31
  * moved state from State.ErrorNum to System.ErrorNum --> old states exists further on, I do not know how to delete it, adapter.deletestate does not work.
25
32
  * deleted test-answers --> moved to my BYD-HVS-Simulator
26
33
  * some minor bugs removed
27
- * obviously the adapter works for hvm, too -> need more testers and an idea for a new name
28
-
34
+ * obviously the adapter works for hvm, too -> need more testers and an idea for a new name
35
+
29
36
  ## 1.0.0 (2021-04-05)
30
37
  * Update all dependencies
31
- * first public version
38
+ * first public version
39
+
32
40
  ## 0.1.4-beta.0 (2021-04-02)
33
- * 1st change with release-script
41
+ * 1st change with release-script
42
+
34
43
  ## 0.1.3
35
- - Test Mode for getting hex data easily, removed check for 2 modules, moved "diagnosis-states" to extra folder, renaming CellStates
44
+ - Test Mode for getting hex data easily, removed check for 2 modules, moved "diagnosis-states" to extra folder, renaming CellStates
45
+
36
46
  ## 0.1.2
37
- - Battery Voltage is unsigned, should now work with 4 modules
47
+ - Battery Voltage is unsigned, should now work with 4 modules
48
+
38
49
  ## 0.1.1
39
- - start of documentation (German)
50
+ - start of documentation (German)
51
+
40
52
  ## 0.1.0
41
- - (Christian) first testing release with (limited) public announcement
53
+ - (Christian) first testing release with (limited) public announcement
54
+
42
55
  ## 0.0.1
43
- - (Christian) initial release
44
-
45
-
46
-
56
+ - (Christian) initial release
package/README.md CHANGED
@@ -8,15 +8,15 @@ BYD HVS Battery poll data
8
8
 
9
9
  ## Introduction
10
10
 
11
- This Adapter takes data from a byd PV battery ( https://www.bydbatterybox.com/ ) and puts them into datapoints in the adapter. Unfortunally there is no official API and no documentation, so I used wireshark and a byd-hvs-simulater to try to understand the communication. My adapter simulates the byd-app, sends similar packets to the device and analyses the responses.
11
+ This Adapter takes data from a byd PV battery ( https://www.bydbatterybox.com/ ) and puts them into datapoints in the adapter. Unfortunately there is no official API and no documentation, so I used wireshark and a byd-hvs-simulator to try to understand the communication. My adapter simulates the byd-app, sends similar packets to the device and analyses the responses.
12
12
 
13
13
  ## be careful
14
14
 
15
- There are two steps in the beConnect app, in the first step you get the normal data, in the second step you get detail-data for all cells (individual cell temperature and voltage and some more details) To get the detail-data there has to be a delay after one of the data-packets till I can get the result. I think in the meantime alle cells are measured, but I am not sure. So I limited the frequency of reading the detail-data, it is done only ever "n" readings of the normal data, you can change this setting. If you do not need the detail-data: you can switch this part off.
15
+ There are two steps in the beConnect app, in the first step you get the normal data, in the second step you get detail-data for all cells (individual cell temperature and voltage and some more details) To get the detail-data there has to be a delay after one of the data-packets till I can get the result. I think in the meantime alle cells are measured, but I am not sure. I am definitely not sure if you harm your battery with polling this data too often, so be aware: You are on your own risk!
16
16
 
17
- ## hint for systems with 5 modules
17
+ ## support for up to 5 modules
18
18
 
19
- People who have 5 modules: The cell details are read only for the first 4 modules - the protocol is the same for 2-4 modules. I would like to extend it for 5 modules but either somebody buys me the three missing modules ;-) so I can analyse the protocol or I get a wireshark capture from a working connection.
19
+ Up to 5 HVS Modules are now supported.
20
20
 
21
21
  ## settings
22
22
 
@@ -34,7 +34,7 @@ Test Mode - show data in error log: If you check this box: the sent and recieved
34
34
 
35
35
  Prinzipiell ist der Adapter durch Anaylse der Datenpakete zwischen der BYD-App und dem BYD-Akku-System entstanden. Es werden im Wesentlichen die Daten aus dem TAB System Info und aus dem TAB Diagnosis dargestellt. Offensichtlich sind die Daten für "System Info" sofort in der Batterie bereit zum abholen, für die Diagnose-Daten sieht es so aus als wäre ein Messvorgang erforderlich, zwischen der Abfrage und den Werten muss ein Zeitintervall von gut 3 Sekunden eingehalten werden.
36
36
 
37
- Daher lasse ich die Diagnose-Daten auch nicht bei jeder Abfrage der Daten mit ermitteln.
37
+ Ich bin mir nicht sicher ob das BYD-System durch zu häufige Abfragen beschädigt wird, also: Es ist Dein Risiko was Du hier einträgst!
38
38
 
39
39
  ## Zu den Einstellungen:
40
40
  Intervall: Zeitlicher Abstand zwischen den Abfragen des Adapters
@@ -43,34 +43,39 @@ IP-Adresse: Eigentlich logisch, damit ist die IP-Adresse des Adapters gemeint. D
43
43
 
44
44
  Batterie-Details: Steuerung, ob die Details zu den Zellen gelesen werden sollen
45
45
 
46
- Lesezyklen zu Batterie-Details: Anzahl der "Normal-Lese-Zyklen" bis wieder einmal die Diagnose-Daten gelesen werden. Hier die Warnung dazu: Ich habe keine Idee ob man sich durch häufige Diagnose-Messungen Nachteile einhandelt, daher empfehle ich den Wert möglichst hoch zu setzen. Ich wüsste auch nicht was man mit den Diagnose-Daten im regelmäßigen Poll anfangen sollte.
46
+ Lesezyklen zu Batterie-Details: Anzahl der "Normal-Lese-Zyklen" bis wieder einmal die Diagnose-Daten gelesen werden. Hier die Warnung dazu: Ich habe keine Idee ob man sich durch häufige Diagnose-Messungen Nachteile einhandelt, daher empfehle ich den Wert möglichst hoch zu setzen. Ich wüsste auch nicht was man mit den Diagnose-Daten im regelmäßigen Poll anfangen sollte.
47
47
 
48
- Zu den Batterie-Größen: Der Adapter funktioniert auch für Zelltemperaturen und ZellSpannungen bei 2,3 und 4 Batterie-Modulen. Bei einem System mit 5 Modulen werden nur die Zellspannungen der ersten 128 Zellen angezeigt. Für die Zellen 129 bis 160 ist mir nicht bekannt wo die Daten gespeichert werden. Ich würde das gerne mit in den Adapter einbauen, benötige aber dafür einen Wireshark-Mittschnitt der Kommunikation zwischen der beConnect App und dem Speicher. Ich helfe auch gerne wenn jemand nicht weiß wie man den Mittschnitt machen kann, entweder per Teamviewer oder per Postings im Forum. Offensichtlich funktioniert die Kommunikation für die 5. Einheit anders als bei den ersten 4 Einheiten.
48
+ Zu den Batterie-Größen: Der Adapter funktioniert für Zelltemperaturen und ZellSpannungen bei 2-5 Batterie-Modulen.
49
49
 
50
50
 
51
51
  ## Changelog
52
52
  <!--
53
53
  Placeholder for the next version (at the beginning of the line):
54
54
  ### __WORK IN PROGRESS__
55
- -->
55
+ -->
56
+ ### 1.4.0 (2022-10-31)
57
+ * Update of referred modules (mainly around testing)
58
+ * improvmenets contributed by Tapter (5 modules, readme and better readable code)
59
+ * Better detection of battery type and inverter
60
+ * SOC not only from normal data but from diagnosis-data, too. There we have one decimal place more
61
+ * removed frequency limit for battery detail data
62
+ * increased max count of temperature measurements for HVS to 64
63
+ * support for up to 5 HVS modules
64
+
56
65
  ### 1.3.0 (2021-11-06)
57
66
  * updated even more dependencies
58
- * official release with new state SOH
59
-
67
+ * official release with new state SOH
68
+
60
69
  ### 1.2.4-0 (2021-11-02)
61
70
  * Added state: SOH
62
- * updated dependencies as suggested from bot
63
-
71
+ * updated dependencies as suggested from bot
72
+
64
73
  ### 1.2.3 (2021-06-18)
65
- * changed ratio of logo
66
-
74
+ * changed ratio of logo
75
+
67
76
  ### 1.2.2 (2021-06-14)
68
- * bump to new patch-level (to get rid of the "-0")
69
-
70
- ### 1.2.2-0 (2021-05-30)
71
- * Create States for Diagnose-Data only if necessary
72
- * changes according review of the adapter
73
-
77
+ * bump to new patch-level (to get rid of the "-0")
78
+
74
79
  ###
75
80
 
76
81
  ## License
@@ -94,4 +99,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
94
99
  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
95
100
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
96
101
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
97
- SOFTWARE.
102
+ SOFTWARE.
package/io-package.json CHANGED
@@ -1,9 +1,22 @@
1
1
  {
2
2
  "common": {
3
3
  "name": "bydhvs",
4
- "version": "1.3.0",
4
+ "version": "1.4.0",
5
5
  "news": {
6
- "1.3.0": {
6
+ "1.4.0": {
7
+ "en": "5 modules supported, frequency limit for polling removed, security updates",
8
+ "de": "5 Module unterstützt, Frequenzgrenze für die Abfrage entfernt, Sicherheitsupdates",
9
+ "ru": "5 поддерживаемых модулей, частотный лимит для удаления опроса, обновления безопасности",
10
+ "pt": "5 módulos suportados, limite de frequência para votação removido, atualizações de segurança",
11
+ "nl": "vijf modules ondersteund, frequentielimiet voor het vervullen van de beveiliging",
12
+ "fr": "5 modules supportés, limite de fréquence pour le polling supprimé, mises à jour de sécurité",
13
+ "it": "5 moduli supportati, limite di frequenza per la rimozione del polling, aggiornamenti di sicurezza",
14
+ "es": "5 módulos compatibles, límite de frecuencia para las encuestas eliminadas, actualizaciones de seguridad",
15
+ "pl": "5 modułów obsługiwanych, limit częstotliwości zanieczyszczeń, aktualizacja bezpieczeństwa",
16
+ "uk": "5 модулів підтримуються, частотний ліміт для видалення пилу, оновлення безпеки",
17
+ "zh-cn": "5个单元支助,清除的污染频率限制,安全更新"
18
+ },
19
+ "1.3.1": {
7
20
  "en": "updated even more dependencies\nofficial release with new state SOH",
8
21
  "de": "noch mehr Abhängigkeiten aktualisiert\noffizielle Veröffentlichung mit neuem Zustand SOH",
9
22
  "ru": "обновлено еще больше зависимостей\nофициальный релиз с новым состоянием SOH",