That works if the device is still on the controller. But is it is not you cannot exclude it without a standalone exclude function. In zwave you can always exclude a device even if it never was included in the controller. Useful in many situations especially if your controller does a spontaneous reset and wipes its config, or second hand devices, or , or…
not my experience…that button starts the process…and you can unpair the device even if its paired with another controller…(like a rescue )…I use it all the time as i test many different controllers i take a device paired with controller A and unpair it with controller B…try it…its a “general exclude” functionality …I got that put in as soon as I bought the company…i couldn’t operate without it …
Aha, you must have a iPhone. The Android app does not have this. It can only Add and delete an existing (unless it is an Alexa, i have a ton of those I cannot get rid off even with a complete deinstall).
Indeed the Android doesn’t have an easily accessible button in the devices view, however it does allow the unpair of any devices, including ones from other hubs.
You can go to any device’s advanced settings tab and click the “Trashcan” icon. You will get a pop up asking for confirmation and which will give the options to cancel the operation, delete the device (if it was a defective one) and unpari the device. If you click unpair the controller goes in unpair mode and the app displays the “Remove devices now…” message. At this moment you can unpair only the device you started the process from or any other zwave devices.
Another option is to try adding the other devices directly, using the specific device model wizard, or the generic zwave wizard. When you get to step 3 and the pairing fails, you can hit retry and this will make the controller go in unpair mode and the app displays the “Remove devices now…” message. At this moment you can unpair any other zwave device.
@Oleh Would it be possible to have an API request to generate a Authentication Token, that the user could then use in http request and curl commands. Or the ability to add a user defined auth token in the Ezlo app, or generate one.
great step forward, but it should be accessible in the app or API. No need for another step/application,. How many users will be frustratted trying to make it work not knowing what or how or where to run the python script. It would be nice to keep security, but simplify it.
Aside the fix nothing else have been changed. After closing the session and login again you should select your hub and connect to it to enable the drop-down menu with the hub commands. The only reason to fail doing so is if suddenly the hub loses internet connection. I have just tried and it worked, however if you keep having the problem let me know to investigate.
I have tested with a Vera Edge running the same version of Linux fw you reported, and I’m able to switch between it and a PlugHub V1 without problem, closing the section and login again. I will add more hubs tomorrow to my test account to see if I manage to replicate this case.
I tried to post a screencast of the issues but these forums don’t allow anything other than static images in select formats. That said, the symptom is that neither of my Linux hubs allowed queries after connecting but the Atom2 hub does. I noticed similar behavior for an Atom that I did not have plugged in.
So, I tried rebooting one of my Linux hubs and I was able to perform queries again. This means that there are 2 core issues.
The connection between the cloud and the hub on Linux FW was in a state that required a reboot to recover (not good). The hub that I rebooted was 90000330. My hub 45006642 is in the same state but I will not reboot it until I hear from you so you guys can diagnose and determine the root cause. @Melih and the engineers know where to find me on Skype if you would like to reach out in a more interactive fashion for diagnosis.
There is no feedback on the apitools webpage that informs the user that it is unable to connect to the hub. Or, it connected to the hub but in a state where queries were not possible. Either way, the apitool should provide some sort of error feedback to the user and ideally a recommended remedy.