-
Notifications
You must be signed in to change notification settings - Fork 4
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
No stream updates for SD device #53
Comments
refreshSD should appear in your given interval |
Hmm, but those (empty?) type 6 datagrams appear every few seconds and I do get very frequent updates of some relevant DP in iobroker if I use the Android app in parallel. |
Yes but a high update rate over long time will result in a block |
Okay, I thought those information are "pushed" using the established websockets connection and Grünbeck only blocks too frequent (complete) connections. But thanks for explaining this and taking care of this great adapter ;-) |
Ich mach mal in Deutsch weiter ;-) Fehlermeldungen tauchen keine auf. Vielleicht ist es ja auch nur ein Serverproblem. |
I have the same issue. I had an SD18, updates of e.g. mflow to ioBroker were almost instant. I replaced the SD18 with an SD21 and now updates are delayed by several minutes and hardly usable. I have no idea what causes this difference. |
Hi!
Some of my stream datapoints don't get frequent (or any) updates at all. Sounds similar to #16
Especially the mflow1 value would be vital for me. It gets updated in the app and, of course, on the device frontpanel.
I've noticed that those "type 6"-messages appear frequently whenever I consume water.
Sometimes, I get a value for mflow1 but it's somehow delayed and goes slowly down to 0 even after water consumption has been stopped for minutes. Again, the app and the device display 0 almost immediately.
UPDATE: Like in previous issues, the values do get frequent updates as soon as I open the app on my phone.
The text was updated successfully, but these errors were encountered: