I am just a bit unsure where to start, I am experimenting with creating device handlers for a z-wave device. In the new documentation it will not let me create a device handler for a hub connected device unless I am a member of an organisation. I am not a manufacturer of the devices I am trying to create handlers for I am simply just researching into creating handlers. For the moment they are just for my own setup.
In the old documentation there is no requirement it seems to be a member of an organisation. All my smart apps are implemented with a webhook up endpoint according to the new documentation. So if I want to use the old docs and implement a device handler will I have to convert all my apps to groovy? Is there plans to get rid of the groovy way of doing things and if so can only “members of organisations” now create device handlers? If there aren’t plans to get rid of the groovy method why support the two methods?
Bit of an update, I found a sample for a custom device handler and have implemented it in my setup. It is in the classic smartapp using groovy and all works fine. However now when I go to the new smart things app the device is not appearing in my setup and I cannot access it through my smart apps hosted with a web hook endpoint.
There is a pop up in the classic app that asks you to migrate over to the new app. I tried this an it just doesn’t seem to consider devices with custom handlers, the message it gives says that the app will soon be deleted is a bit worrying too.
To cut a long story short, new hub connected devices are still being implemented using the legacy Groovy Device Handlers via the IDE. Other new devices and all new apps can, and really should, use the new methods. Switch off time for the legacy systems hasn’t been announced but is anticipated for 2021.
The Developer Workspace isn’t particularly welcoming for private and community developers. It is improving from where it was two years ago though. You can create an organisation for yourself if you want. There isn’t much point doing it for hub connected devices though.
Not sure what is going on with your device handler. I assume you published it for yourself in the IDE editor? I don’t know exactly what that does but although some things seem to work without it you should still do it.
Thanks for the reply, yeah so the device I am using is the Aeotec Smart Switch 6. I was trying to get the device to read voltage and current as the default handler does not support this even though the device supports it.
I found a custom device handler for the device written by @Robert_Vandervoorthere . Created a new device handler in the IDE and published it for myself. I then assigned the device handler to an already connected Aeotec Z-Wave plug. The only measurements that worked where energy and power so I will have to investigate that further.
Why do you say there isn’t much point in doing this for hub connected devices if the classic way of doing things is going to be turned off? Shouldn’t everyone be doing this for there custom device handlers for hub connected devices?
Because once you have created the project in the organisation workspace you will be directed to the IDE to create and test the project anyway and largely left to get on with it.
