forum

Posted: **18 Nov 2020 11:00**

Hi,

Im getting flooded by this error in the UI log:

Cannot create vDev based on: 35-0-113: TypeError: Cannot read property 'forEach' of null

This has started to appear after installing the UI version/firmware.

Code: Select all

Software info
Firmware version	v3.1.1
UI version	v1.11.1
Built date	16-09-2020 01:08:41

Device:
Everspring Wall Plug Dimmer. Fully functional. Interview complete.

Code: Select all

{
                "creationTime": 1605199497,
                "creatorId": 1,
                "customIcons": {},
                "deviceType": "sensorBinary",
                "h": 592601133,
                "hasHistory": false,
                "id": "ZWayVDev_zway_35-0-113-8-1-A",
                "location": 5,
                "locationName": "Bedroom (removed due to personal references)",
                "metrics": {
                    "icon": "alarm",
                    "level": "off",
                    "title": "Everspring Power Management Alarm (#35)",
                    "isFailed": false,
                    "modificationTime": 1605469800,
                    "lastLevel": "off"
                },
                "nodeId": 35,
                "order": {
                    "rooms": 0,
                    "elements": 0,
                    "dashboard": 0,
                    "room": 1
                },
                "permanently_hidden": false,
                "probeType": "alarm_power",
                "tags": [
                    "bedroom",
                    "management",
                    "powermeter"
                ],
                "visibility": true,
                "updateTime": 1605639604
            },

This is getting to the point in which its to often, to much and also unbearable to have the app isntalled since this creates a push notification each it happens and having 100+ notifications after one hour is not longer an option.

Please direct me to logs where and why this could be happening. Ill supply what ever is needed!

Posted: **18 Nov 2020 11:35**

This problem has been dealt with here in the forum many times. Please use the search function to get the solution.

The issue is coming up very often, always for command class 113. Seems Z-Way has a problem there. With the new notification function now it's more important than before to finally fix it.

Posted: **18 Nov 2020 12:08**

Posted: **18 Nov 2020 14:09**

piet66 wrote: ↑
18 Nov 2020 11:35
This problem has been dealt with here in the forum many times. Please use the search function to get the solution.

The issue is coming up very often, always for command class 113. Seems Z-Way has a problem there. With the new notification function now it's more important than before to finally fix it.

Actually i did but i didnt find the answer the first time. The german thread i could understand.
The thread that solved it for me is -> https://forum.z-wave.me/viewtopic.php?p=88569#p88569

And it was the only thread that actually had an answer based on a serch for "Cannot create vDev based on:" but sure, problem solved(atleast the symptoms, the root cause i know nothing about)

Posted: **18 Nov 2020 23:21**

In any case it is right to point out again and again that the problem must finally be solved.

Posted: **21 Dec 2020 02:20**

Finally we have found the issue. In v3.1.2 this will be fixed. Meanwhile a Force Interview is solving the problem.

Posted: **21 Dec 2020 14:26**

Good news, even I hadn´t it a long time ago the last time. Thumbs Up

Posted: **22 Dec 2020 23:05**

I had it last 9 days ago.

Posted: **28 Dec 2020 00:04**

Is there a way to throttle notifications? When this bug happens for me I just reboot the raspberry pi to reset everything and it will be fine for several weeks between each time it happens. I'm worried about if my gmail will start thinking z-way is spamming and begin to filter messages though.

The Z-way mail notifications are usually very useful but it's annoying to suddenly get notifications every few seconds. I would like to set a limit on how many it can send per minute.

Fingers crossed it is fixed in 3.1.2 as you say

Posted: **28 Dec 2020 03:48**

Please do Force Interview on your device to fix it. v3.1.2 should fix it.

forum

Cannot create vDev based on: 35-0-113: TypeError:

Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError:

Re: Cannot create vDev based on: 35-0-113: TypeError: