So was it the intent for everything to go dark and have everyone reset their hubs?
@orangebucket this is probably why you have problem with second device.
I just have one Ikea motion sensor, but i don’t see how hub will know how to differentiate another one if all of this IDs are blank by default
This is how Edge device is added, no Zigbee ID, no Network ID, no Hub,and it’s not Local, it’s still Cloud
Ok lets hope this will be the case
The IDE is part of the legacy platform so it only knows that sort of thing for devices that use DTHs.
If you view the device via the current API (e.g. using the CLI), you will see the EUI (the Zigbee device ID), the network ID, the local execution status and the hub ID.
It is not cloud. It actually runs locally. Also they said that nothing from the edge drivers will be displayed inside the ide
I have tried to change the controller with the tool that the app has in device tools menu and it gives me an error: “Check that your phone is connected to the network”
Could it still not work?
Yes it runs local, but it is seen in IDE as type placeholder and in the app it is in linked services.
The information of the zigbee connection metrics between the device and the hub has also been lost.
I went back to Groovy dth, and it shows correct battery status. Anyway Groovy device, connects through another zigbee repeater, was not. It was connected directly to yhe Hub, which was on the border of the signal, and it was conecting/disconnecting all the time. It never connected through any repeater.
The battery level calculation is not always very reliable.
ikea dth does the calculation by voltage reading.
Now they have fused it with the dth zigbee motion sensor and the calculation do it differently, by percentage remaining reading.
The smartSense motion sense dths, for samjin models, from doing the calculation in the cloud to doing it locally in the hub gives me a difference of up to 10%, since they use different calculation formulas in the dth and the hub. the hub does the standard zigbee percentage calculation.
But I don’t know if this will be your case.
I don’t see in the edge drive code that it does a different battery calculation for the ikea sensor, as I see it in the edge drive of the zigbee smoke sensor for the Frient sensors
I just replaced battery prior to changing to edge driver. It should be at least 99%, not 50
Just switched my Sonoff motion sensor, it shows “phaceholder” on Groovy and works fine. I have two automations using it, the first one turns on a device when movement is detected and shows running local (home icon). The second turns off the device after 5 minutes without movement, but it´s not showinhg the home icon. If I disable the “stay this status for how long?”, the icon appears.
Is it possible to run locally automations with this option enabled?
remains function doesn’t run local yet.
They told us this when lunching the beta
The different percentage calculations is one thing, but it immediately looks from the result like a divide by two has been added/missed, for the IKEA at least.
The normal calculation by reading the remaining percentage, divide by 2. In this case they have divided by 4 or the raw value is not correct.
In the ikea dth it has min and max values of 2.1v and 3.0 v. and uses the voltage reading. The rest of the sensors where they have integrated the Ikea dth use the calculation by direct percentage dividing the raw value by 2.
I do not see in the lua code any special case for the ikea calculation by voltage.
I see that it configure the reports to send percentage, not voltage.
I guess the Ikea sensor will accept this configuration!
In the zigbee smoke sensor edge driver there is the frient sensor that also calculates it by voltage and has its specific code with the definition of the min and max values in the “scr / frient” folder and has its own code in the test folder.
I do not have any ikea sensor, but seeing the livelogging in the cli, @milandjurovic71 could check the battery calculation log, it is not easy since it has very long configuration intervals 21600 sec if there are changes> = 1%
As I was saying, you can try to see the live logging in the CLI, activating it before pairing device with command “smartthings edge: drivers: logcat” as seen in the tutorial and you will be able to see the response of the device when it is paired:
- It will send the information of acceptance of the configuration and battery level value, values in red in the capture. Check if it calculates it by percentage or by voltage. In the capture, value= hex C8 = 200/2 = 100%
It also sends the RSSI and LQI zigbee signal metrics, values marked in blue. I did not know where this could be seen now and it is seen in the live log every time an event is sent to the hub.
Yes, the IDE doesn’t fully recognize the Devices handled by Edge Drivers, that’s why those fields are empty and execution is set as “CLOUD” but they run locally.
If you query the devices list through the ST API, you’ll see their info, such as network ID, device ID, etc.
@nayelyz I am used to being able to ‘re-pair’ devices that are misbehaving instead of deleting them first. Is this something that should be possible with Edge drivers? Only I had a motion sensor that seemed to be genuinely offline and not responsive so I thought I’d pair it again. End result was the motion sensor clearly thought it was still trying to pair, and the app had silently marked it back online. So I had to delete it and pair it again from scratch.
Zwave siren and zwave range extender have just been added.