Open votecc9 opened 3 years ago
ich habe das gleiche Problem mit einem anderen Gerät [2021-3-9 11:49:38] [homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [2021-3-9 11:49:38] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [2021-3-9 11:50:48] [homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [2021-3-9 11:50:48] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [2021-3-9 11:54:03] [homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [2021-3-9 11:54:03] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
I have the same issue: [3/16/2021, 07:30:19] [homebridge-homematic] This plugin generated a warning from the characteristic 'Smoke Detected': characteristic value expected valid finite number and received "NaN" (number). See https://git.io/JtMGR for more info.
The same Problem as @fighterzg6 here:
[homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. See stack trace further on!
Raspberry4 pivCCU3 Ver.3.57.4 Homebridge 1.3.4 Homematic Plugin 0.2.226 HMIP-BROLL Firmware 1.8.20
Stack trace:
HmIP-RF.00111BE99987E0:4) -> Send Event with value 0
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] transformDatapoint LEVEL_STATUS
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] cache HmIP-RF.00111BE99987E0:4.LEVEL_STATUS (0)
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 0 for HmIP-RF.00111BE99987E0:4.LEVEL_STATUS
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] datapointEvent 4.LEVEL_STATUS with 0 channel HmIP-RF.00111BE99987E0:4
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [RPC] event for HmIP-RF.00111BE99987E0:4.SECTION with value 4
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 4 for HmIP-RF.00111BE99987E0:4.SECTION
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [RPC] Accessory (Rolladen Schlafzimmer rechts Aktor) found by channeladress (HmIP-RF.00111BE99987E0:4) -> Send Event with value 4
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] transformDatapoint SECTION
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] cache HmIP-RF.00111BE99987E0:4.SECTION (4)
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 4 for HmIP-RF.00111BE99987E0:4.SECTION
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] datapointEvent 4.SECTION with 4 channel HmIP-RF.00111BE99987E0:4
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [RPC] event for HmIP-RF.00111BE99987E0:4.PROCESS with value 0
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 0 for HmIP-RF.00111BE99987E0:4.PROCESS
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [RPC] Accessory (Rolladen Schlafzimmer rechts Aktor) found by channeladress (HmIP-RF.00111BE99987E0:4) -> Send Event with value 0
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] transformDatapoint PROCESS
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] cache HmIP-RF.00111BE99987E0:4.PROCESS (0)
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 0 for HmIP-RF.00111BE99987E0:4.PROCESS
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] datapointEvent 4.PROCESS with 0 channel HmIP-RF.00111BE99987E0:4
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] transformDatapoint 4.LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] remoteGetValue Intf:HmIP-RF, Adre:HmIP-RF.00111BE99987E0:4, Dp:LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Core] getValue (HmIP-RF) HmIP-RF.00111BE99987E0:4.LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Core] check cache HmIP-RF.00111BE99987E0:4.LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] hit on HmIP-RF.00111BE99987E0:4.LEVEL 100
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] got value for HmIP-RF.00111BE99987E0:4.LEVEL (Value:100)
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] Convert 10000 for 4.LEVEL is 10000
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] will cache 10000 for HmIP-RF.00111BE99987E0:4.LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] cache HmIP-RF.00111BE99987E0:4.LEVEL (10000)
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Cache] write 10000 for HmIP-RF.00111BE99987E0:4.LEVEL
[19/03/2021, 13:56:34] [inetHomeMatic VCCU3] [Generic] run callback with 10000
[19/03/2021, 13:56:34] [homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[19/03/2021, 13:56:34] [homebridge-homematic] Error:
at CurrentPosition.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CurrentPosition.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1950:16)
at CurrentPosition.Characteristic.updateValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1379:20)
at /usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeMaticHomeKitBlindServiceIP.js:148:23
at /usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeKitGenericService.js:597:9
at HomeMaticPlatform.getValue_rega (/usr/local/lib/node_modules/homebridge-homematic/index.js:645:7)
at HomeMaticPlatform.getValue (/usr/local/lib/node_modules/homebridge-homematic/index.js:675:14)
at HomeMaticHomeKitBlindServiceIP.remoteGetValue (/usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeKitGenericService.js:568:19)
at HomeMaticHomeKitBlindServiceIP.datapointEvent (/usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeMaticHomeKitBlindServiceIP.js:147:10)
at HomeMaticHomeKitBlindServiceIP.event (/usr/local/lib/node_modules/homebridge-homematic/ChannelServices/HomeKitGenericService.js:752:14)
at /usr/local/lib/node_modules/homebridge-homematic/HomeMaticRPC.js:183:19
at Array.map (
Just a guess: Problem may be in HomeKitGenericService.js at line 572. The value for remoteGetValue is multiplied by 100 which will probably not work for Blinds (HMIP-BROLL): remoteGetValue: function (dp, callback) { var that = this var tp = this.transformDatapoint(dp) var interf = this.intf this.log.debug('[Generic] remoteGetValue Intf:%s, Adre:%s, Dp:%s', interf, tp[0], tp[1]) let dpadr = tp[0] + '.' + tp[1] that.platform.getValue(interf, tp[0], tp[1], function (newValue) { that.log.debug('[Generic] got value for %s (Value:%s)', dpadr, newValue) if ((newValue !== undefined) && (newValue !== null)) { if (tp[1] === 'LEVEL') { *newValue = newValue 100** }
Same problem here. When can we expect a fix? This means that no devices work for me with CCU3 3.57.4.
Good afternoon, same issue here.
I set heating controler to "AUS" (off) and my log is full with "this plugin generated a warning from the characteristic...
Only for the contoler they set to AUS. If I reduce to 10 degree, its fine. But maybe a fix for the summer mode (AUS / OFF) is possible, please?
[11/05/2021, 14:58:15] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 4.5 exceeded minimum of 10. See https://git.io/JtMGR for more info.
No update until now. Is there a chance to fix the warning from log, please?
[27/05/2021, 18:53:42] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 4.5 exceeded minimum of 10. See https://git.io/JtMGR for more info.
Hallo,
auch bei bei mir erscheint im Log ständig diese Meldung. Gruß Mario
[6/23/2021, 4:31:30 PM] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Temperature': characteristic was supplied illegal value: number 4.5 exceeded minimum of 10. See https://git.io/JtMGR for more info.
Habe meine CCU2 auf CCU3 geswapt. Keine Homebridge mehr nötig, funktioniert alles top. Ich denke, da tut sich auch nichts mehr hinsichtlich Bugfixing auf CCU2.
@votecc9 Was hat das mit CCU3 zu tun? Kann die CCU3 mittlerweile nativ Homekit?
Ich habe meine Homematic Komponenten an meiner Raspberry Pi Zentrale pivCCU3 laufen und dort die (aktuelle) Version 3.57.5. Damit ich mit Siri meine Komponenten steuern kann habe ich Homebridge mit dem Homematic Plugin.
@votecc9 Was hat das mit CCU3 zu tun? Kann die CCU3 mittlerweile nativ Homekit?
Ich habe meine Homematic Komponenten an meiner Raspberry Pi Zentrale pivCCU3 laufen und dort die (aktuelle) Version 3.57.5. Damit ich mit Siri meine Komponenten steuern kann habe ich Homebridge mit dem Homematic Plugin.
es gibt das passende Addon ebenfalls von @thkl -° HAP-Homematic
Ich bekomme die gleiche Meldung.
Here is the same for:
[21.7.2021, 11:25:06] [homebridge-homematic] This plugin generated a warning from the characteristic 'Current Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info. [21.7.2021, 11:25:06] [homebridge-homematic] This plugin generated a warning from the characteristic 'Target Position': characteristic was supplied illegal value: number 10000 exceeded maximum of 100. See https://git.io/JtMGR for more info.
You can fix the display in the Home App with this workaround:
Homematic BROLL (Rolladen) Aktor Wert korrigieren:
cd /homebridge/node_modules/homebridge-homematic/ChannelServices pico HomeMaticHomeKitBlindServiceIP.js
Diese Zeile von 100 auf 10000 erhöhen: this.maxValueForOpen = this.getClazzConfigValue('maxValueForOpen', 10000)
This will not remove the log messages in Homebridge, but the shutters work properly.
@votecc9 Was hat das mit CCU3 zu tun? Kann die CCU3 mittlerweile nativ Homekit? Ich habe meine Homematic Komponenten an meiner Raspberry Pi Zentrale pivCCU3 laufen und dort die (aktuelle) Version 3.57.5. Damit ich mit Siri meine Komponenten steuern kann habe ich Homebridge mit dem Homematic Plugin.
es gibt das passende Addon ebenfalls von @thkl -° HAP-Homematic
Läuft das Addon besser? Hier ist ja mit einem bugfixing leider nicht mehr zu rechnen…
@votecc9 Was hat das mit CCU3 zu tun? Kann die CCU3 mittlerweile nativ Homekit? Ich habe meine Homematic Komponenten an meiner Raspberry Pi Zentrale pivCCU3 laufen und dort die (aktuelle) Version 3.57.5. Damit ich mit Siri meine Komponenten steuern kann habe ich Homebridge mit dem Homematic Plugin.
es gibt das passende Addon ebenfalls von @thkl -° HAP-Homematic
Läuft das Addon besser? Hier ist ja mit einem bugfixing leider nicht mehr zu rechnen…
Gute Frage. Würde ich auch gerne wissen. Der Fehler geht echt auf die Nerven.
Wenn man sich an das Gui gewöhnt hat(funktioniert mittelprächtig), läuft hap-homematic ohne Probleme. Ich nutze es seit einem Jahr. Auch neue Hom,ematic Devices sind integriert.
Ich kann euch da bestens Home Assistant ans Herz legen. Es gibt ein bestens gepflegtes Homematic Plugin und eine top Einbindung in homekit.
You can fix the display in the Home App with this workaround:
Homematic BROLL (Rolladen) Aktor Wert korrigieren:
cd /homebridge/node_modules/homebridge-homematic/ChannelServices pico HomeMaticHomeKitBlindServiceIP.js
Diese Zeile von 100 auf 10000 erhöhen: this.maxValueForOpen = this.getClazzConfigValue('maxValueForOpen', 10000)
This will not remove the log messages in Homebridge, but the shutters work properly.
This workaround did not work for me, as the issue keeps popping up.
Instead, I made a change inside HomeKitGenericService.js inside remoteGetValue Function:
if (tp[1] === 'LEVEL') { if (newValue <= 1) { new Value = new Value * 100 } }
It seems that the initial setup required a value for level between 0 and 1, while the error above outlines, that the return value is in between 0 and 100. This fix at least helped in my setup solving the issue.
Hello @2slow4u ,
thank you for your message i will try your fix the next days and give you a feedback. How about updates? I think you have to fix this after every update.
Cheers CyberChris79
hallo,
auch bei mir seit letztem Update folgende Fehlermeldung
This plugin generated a warning from the characteristic 'Sonnenscheindauer': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.
und
This plugin generated a warning from the characteristic 'Current Ambient Light Level': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.
Homebridge V1.3.2 homebridge-homematic v0.2.226
Das System ist teilweise derart mit sich selbst beschäftigt, das von mir über IOS erstellt Kurzbefehle nicht mehr korrekt ausgeführt werden. Die Kurzbefehle bestehen aus einer zeitlichen Abfolge (im Sekundenbereich) von Schaltzuständen der Aktoren. Die ersten zwei bis drei Schaltzustände werden erreicht (ist unterschiedlich), die weiteren Schaltzustände bleiben aus. Debugfile ist angehängt. homebridge.log-4.txt
Eine Lösung des Problems wäre klasse.
Vielen Dank, Gruß Andreas
To Reproduce Steps to reproduce the behavior:
Actual behaviour A clear and concise description of what is actually happen.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.