State has wrong type
raintonr opened this issue · 5 comments
After upgrade to js-controller 3.3.0 these errors appear:
2021-03-04 07:54:17.197 - warn: loxone.0 (28539) State "loxone.0.10cba2da-0178-97e9-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.221 - warn: loxone.0 (28539) State "loxone.0.10cba2da-0168-97e1-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.333 - warn: loxone.0 (28539) State "loxone.0.0f20f0a8-00fb-353f-fffff62eeb38b63d.autoState" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.409 - warn: loxone.0 (28539) State "loxone.0.0fc602d5-00db-8c29-ffffba8f9ff5d444.autoState" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.483 - warn: loxone.0 (28539) State "loxone.0.0fc60277-03b6-6d6a-ffffc8bccb4b73f0.autoState" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.560 - warn: loxone.0 (28539) State "loxone.0.0fc60216-010d-28d0-ffffe612b2d90393.autoState" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.717 - warn: loxone.0 (28539) State "loxone.0.14eaadfe-01cc-5604-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.741 - warn: loxone.0 (28539) State "loxone.0.127aea95-0128-e12a-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.763 - warn: loxone.0 (28539) State "loxone.0.127aea97-034a-72d4-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
2021-03-04 07:54:17.786 - warn: loxone.0 (28539) State "loxone.0.127aea97-00ee-29fd-fffff62eeb38b63d.error" has wrong type "number" but has to be "string"
Can you please provide the native part of some of the states (at least one "error" and one "autoState") as I can't figure out which control generates these errors.
Well, in my installation, 10cba2da-0178-97e9-fffff62eeb38b63d is a 1-Wire sensor and looks like this:
NB: I should mention the below comes from my 'prod' installation which is on js-controller 3.2.6, but the Loxone IDs are the same of course (as I only have 1 Loxone system).
{
"from": "system.adapter.loxone.0",
"user": "system.user.admin",
"ts": 1614851082163,
"common": {
"name": "Salon Humidity: error",
"type": "string",
"role": "text",
"read": true,
"write": false,
"smartIgnore": true
},
"native": {
"uuid": "10cba2da-0178-97e8-ffffac6194baf95e"
},
"acl": {
"object": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator",
"state": 1636
},
"_id": "loxone.0.10cba2da-0178-97e9-fffff62eeb38b63d.error",
"type": "state"
}0f20f0a8-00fb-353f-fffff62eeb38b63d is a auto blinds controller and looks like this:
{
"from": "system.adapter.loxone.0",
"user": "system.user.admin",
"ts": 1614851082277,
"common": {
"name": "Kitchen: autoState",
"type": "string",
"role": "text",
"read": true,
"write": false,
"smartIgnore": true
},
"native": {
"uuid": "16aaf077-01e8-b3cf-fffff62eeb38b63d"
},
"acl": {
"object": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator",
"state": 1636
},
"_id": "loxone.0.0f20f0a8-00fb-353f-fffff62eeb38b63d.autoState",
"type": "state"
}After upgrade to js-controller 3.3.4 these errors appear:
I assume you are both using the latest version of ioBroker.loxone.
I will have a look at all my adapters with the latest controller next week.
My ioBroker.loxone version is 2.1.0.