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

Error-Message in Adapter #50

Open
jhg28 opened this issue Jan 1, 2024 · 1 comment
Open

Error-Message in Adapter #50

jhg28 opened this issue Jan 1, 2024 · 1 comment

Comments

@jhg28
Copy link

jhg28 commented Jan 1, 2024

Starting today I receive the following messages:

admin.0
2024-01-01 19:16:50.409 error Cannot subscribe "viessmannapi.0.2157277.0.general.roles.type:product;Vitocal_250A": Error The pattern "viessmannapi.0.2157277.0.general.roles.type:product;Vitocal_250A" is not a valid ID pattern
host.iobroker-Server
2024-01-01 19:16:50.394 warn States 127.0.0.1:55310 Error from InMemDB: Error: The pattern "viessmannapi.0.2157277.0.general.roles.type:product;Vitocal_250A" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2470:15) at StatesInMemoryServer.handleSubscribe (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (/opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:258:14) at RedisHandler. (/opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:395:26) at RedisHandler.emit (node:events:514:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:209:37) at processImmediate (node:internal/timers:476:21)

admin.0
2024-01-01 19:16:50.389 error Invalid pattern on subscribe: The pattern "viessmannapi.0.2157277.0.general.roles.type:product;Vitocal_250" is not a valid ID pattern

I use ViCare+ in the moment to see if the additional data brings any benefit.

Maybe this creates the error messages.
Additionally it looks like, that Viessmann changed something in the data.

@TA2k
Copy link
Owner

TA2k commented Jan 1, 2024

With v2.4.0 ?

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

2 participants