Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GroupValueResponse is ignored #162

Closed
skrutzler opened this issue Mar 25, 2021 · 17 comments
Closed

GroupValueResponse is ignored #162

skrutzler opened this issue Mar 25, 2021 · 17 comments

Comments

@skrutzler
Copy link
Contributor

skrutzler commented Mar 25, 2021

Once the iobroker knx adapter sends a GroupValueRead (Object with R&W flag) the knx bus shows that there is also a GroupValueResponse, but that one is ignored. The Iobroker object stays at 0°C.
The iobroker object is only updated once the knx device is sending the KNX Object on its own.

# | Zeit | Dienst | Flags | Prio | Quelladresse | Quellname | Zieladresse | Zielname | Rout | Typ | DPT | Info
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
2709 | 25.03.2021 14:14:33,345 | vom Bus |   | Niedrig | 1.0.199 | IO-Broker | 5/0/15 | EG - Wohnzimmer - Temperatur | 6 | GroupValueRead |   |  
2710 | 25.03.2021 14:14:33,448 | vom Bus |   | Niedrig | 1.0.30 | Wohnzimmer Präsenzmelder Multisensor | 5/0/15 | EG - Wohnzimmer - Temperatur | 6 | GroupValueResponse | 9.001 Temperatur (°C) | 0C 79 \| 22,9 °C

Version 1.0.44

@skrutzler skrutzler changed the title GroupValueResponse wird ignoriert GroupValueResponse is ignored Mar 25, 2021
@Videonisse
Copy link

Videonisse commented Mar 27, 2021

I have the same problem. Have tested with all the versions v1.0.41 to 1.0.45 without success. node: v12.21.0, js-controller: 3.2.16. Forum post: https://forum.iobroker.net/topic/26167/test-adapter-knx-v1-0-x/442?_=1616858621504

I actually thought this was working earlier but not sure anymore. I tried using the older knxproj-file from ETS 5.7.4 together with the above versions and used a clean installation of the Instance every time. Lastly, I also removed the KNX Adapter and reinstalled the latest version and created a new instance with import from ETS 5.7.5. Problem persists.

Also tested to change the State DB from File to Redis, but didn't help. Object DB is File.

The problem seems to be with all DPs, but the one I mostly tested with is a Dimmer Level Status % for a Light. DPT5.001.

See below several parts of the log-file. The first log level was set to More but for the lasts I changed to Most. They are all from v.1.0.45.

DP Object - GA 4/7/21

{
"_id": "knx.1.Belysning.Dimmer.Kök_Ljusskena_matbord_LGx1_Status_Dimvärde_8bit",
"type": "state",
"common": {
"name": "Kök Ljusskena matbord LGx1 Status Dimvärde 8bit",
"type": "number",
"role": "value",
"read": true,
"write": true,
"unit": "%",
"max": 100,
"min": 0
},
"native": {
"dpt": "DPT5.001",
"address": "4/7/21",
"addressRefId": "P-095B-0_GA-13",
"statusGARefId": "",
"actGARefId": "P-095B-0_GA-10",
"update": false,
"objRef": "O-10_R-1627",
"devName": "M-0048_A-493A-1C-D4B1",
"devInst": "P-095B-0_DI-16",
"objectSize": ""
},
"from": "system.adapter.knx.1",
"user": "system.user.admin",
"ts": 1616846273617,
"acl": {
"object": 1636,
"state": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator"
}
}

@Videonisse
Copy link

@chefkoch009 Any chance you could confirm if this actually is a bug in the Adapter, or if it works as it should on other installations?

As I also wrote on the Forum, it's very easy to reproduce:

  • Benutzte ein Dimmer Licht. Schalte es mal ein und kontrolliere die Status wert (%) in ioBroker (DPT5.001)
  • KNX Adapter Instanz anhalten
  • Ändere Dimmer wert (Busmonitor oder an Schalter)
  • Starte KNX Adapter
  • Beobachte ob Dimmer Status wert in ioBroker upgedatet wird oder nicht, ohne die Lampe zu schalten/dimmern.

@skrutzler
Copy link
Contributor Author

skrutzler commented Apr 12, 2021

is there any progress on this topic or can I somewhere help?
This is a rather serious issue and makes the iobroker/adapter not usable for me.
@chefkoch009

@RESDE
Copy link

RESDE commented Apr 16, 2021

@Videonisse the communication between the KNX Gateway and the KNX adapter is heavily depending on your ETS setup ( gateway. In many other users all state updates driven from IOBroker are working coorrectly.
Before keeping flodding this topic with long log protocolls which are hard to read anyway I can offer you to import your ETS project file and test out what else can impact the propper communication from/into the ETS world. Please send me an PN to my github user.
@skrutzler: the KNX adapter only reacts based on the propper import of the GA addresses. Many issues are here available where it is proven that wrong flags in the GA setup in ETS leads not to a propper KNX adapter data exchange. Have you read all these issues and are you clear that the GA flags in your ETS project are set accurately.
If you can confirm this would you mind to post then the relevant GA adresses with a screenshot of the ETS (and with the linked devices) and then as well the object definitions out of the knx adapter (especially the read/write tru/efalse options)

@Videonisse
Copy link

@RESDE Sorry but I don't know how to send a PM to a GitHub user, is it possible?

I created a test project with just one light and has been testing this with a separate instance of the KNX Adapter. My KNX interface is a Weinzierl KNX IP Interface 730. Using this I have exactly the same problem as when I'm using my production setup.

Are you 100% sure that there is no problem with other installations where it seems to work? Have you tried to reproduce the issue as I tried to explain above?

First I was sure it was working for me as well, as time stamp and everything indicates this, but it's not. I have asked in the forum if someone could do the test and confirm if it work for not for them, but no one as answered. Until it's confirmed, I believe it actually is a bug.

Here is my knxproj file:
ioBroker test GroupValueRespons.zip

(How can I paste log files without that Githib removes the linebreaks?)

@Videonisse
Copy link

Below is again some log information as screen dumps instead of text.

(The value was 40%, then is Adapter turned off and the value changed in KNX to 37%. When the Adapter is turned on, it sends a GroupValueRead and also receives the new value of 37%. Timestamp for Object is updated BUT THE NEW VALUE IS NOT WRITTEN TO OBJECT:

ioBroker Log
image

ioBroker Objects
image

ETS5 Busmonitor
image

@RESDE
Copy link

RESDE commented Apr 18, 2021

@Videonisse for a PN just check out my User RES_DE in the IOBroker Forum there is the opportunity that we xchange Themen

@Videonisse
Copy link

Clarification regarding the problem: There is no problem with the "response" values for boolean values or numbers that is = 0 (zero). I have tested numbers with 1 byte DPT 5.001 (%) and 2 bytes DPT 7.012 (mA).

The problem is with values greater than 0 (zero). They are received (visible in adapter log) but NOT written to the state database and not updated in the object.

Anyone else with the same problem?

@Videonisse
Copy link

@chefkoch009 are there any chance you could give some feedback regarding your thoughts about this issue?

It's really quick and easy to reproduce and if the above screen dumps wasn't clear enough, below shows with 100% certainty that that response value is received by the KNX Adapter but NOT written to the state database. If this isn't a serious bug in the KNX Adapter, what is the cause of the problem?

The easiest way to reproduce the Issue:

  1. Switch a dimmer light off. Notice the dim value object (should be 0%)
  2. Turn off KNX Adapter instance
  3. Switch the dimmer light on
  4. Turn on KNX Adapter instance
  5. Notice the dim value object (should anything else than 0%)

In the below screen dumps, in step 5, the dim value remains 0% but log shows clearly that a value of 50% was received. Timestamp confirmed that the object was updated, but not with the new value.

Step1:
image

Step 5:
image

image

Additional: if the light is toggled off/on when KNX Adapter is active, the problem will not be identified as the new value is received as GroupValueWrite.
image

@skrutzler
Copy link
Contributor Author

skrutzler commented Jun 17, 2021

so the issue is reproducable. is there any progress? @chefkoch009

@Videonisse
Copy link

@chefkoch009 This Issue remains with v2.0.2. Any idea why the value is not updated?

@Drkongo
Copy link

Drkongo commented Feb 17, 2022

Any news on this topic.
I have the same problem with v. 2.0.5.
My temperature objects stay with value null.

@chefkoch009
Copy link
Collaborator

i fixed in V2.0.12 some things related to this issue. could you check it please?

@Videonisse
Copy link

Nice, thanks! I have only done one quick test (the one explained above) and now it works! I appreciate your effort!

@chefkoch009
Copy link
Collaborator

so, this issue can be closed?

@Videonisse
Copy link

From my perspective yes. Maybe also issue #122 can be closed?

@chefkoch009
Copy link
Collaborator

Great. So I close this issue... thanks for response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants