-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Verify Compact mode for your adapter #202
Comments
It seems that enabling compact mode will mix-up the objects, e.g. they will no longer appear under the node they usually should but rather appear on a different instance's node. |
Exact example or Screenshot could might be useful. |
Way to reproduce:
As a result, HmIP devices will show up in both instance nodes, hm-rcp.0 (where they belong) and hm-rcp.1 (which shouldn't be): |
Confirmed, there is a strange behaviour. For me it ended up having only rfd devices in both namespaces (rfd is my hm-rpc.0) @Apollon77 is it already tested, having 2 instances of the same adapter in the same comapct group? |
Technically this should be completely irrelevant if compact mode or not and such. For compact mode there is a slight chance that „global“ working libraries (so libs that do not create object instances and store data on such a level) mix up. Maybe it is something like this? On the other hand vm2 is used where code runs in. I have no idea how separated requires are there then. I can also have a look at the hm-rpc Code later Ingo |
@Apollon77 As mentioned in Telegram, when the whole code is in |
Just variable names should not be the reason ... but great to know |
Seems fixed with js-controller 2.0.40 |
We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.
Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512
On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.
Thank you for your support.
The text was updated successfully, but these errors were encountered: