The logger functionality allows critical error and warning messages to be saved to the device’s logMessage attribute (not that there should be many ). This offers a way to store and review historical messages without having to keep the IDE Live Logging screen open.
A word of caution. I can’t be 100% sure yet, without more testing, but I’ve been having very slow repsonse to some of my sockets since switching to this device handler from the standard “z-wave metered socket”. Slow i.e. waiting 30 plus seconds from a socket to respond to a switching command. If at all. Sometimes it can be minutes later, or not at all.
Checked with online support and the logs and the commands are getting sent immediately. The switches then take an age to react - sometimes.
I’ve switched back to “z-wave metered socket” and they are responding as they should so far… will update after a dar or two.
This is unlikely to be anything specific to this device handler; it’s not doing anything special in terms of sending commands. I find this kind of delayed response happens occasionally for all devices and occurs when either the SmartThings cloud or your local Z-wave network is congested.
I have four of these plugs around my house and they all appear to be working with this DTH, although I have noticed one potential issue.
One of the plugs is reporting its power usage about few seconds, whereas all the other plugs don’t. They are all configured with the same settings, i.e. Power Report Threshold is set to 30 as per the recommendations.
Well, I’m switching from Zipato to Samsung, receiving my SmartThings hub tomorrow.
Meanwhile I checked all my GreenWave Reality devices on the old Zipato.
I have 7 (seven!) single power plugs and 3 (three!) 6-socket nodes.
I was glad to read here that they are supported by the SmartThings, BUT, all my GreenWave devices are firmware 4.20 and 4.21, and that seems to be bad news according to the notes here
Has anyone ever found a way to upgrade the firmware on the GreenWave devices? I took one apart just now, having tooled a special two-pronged screwdriver in my workshop, and I do see a 4-pin female-socket on a board. USB?
Any ideas? If not then maybe I’ll call their office in Denmark.
Indeed Philip_Street. However, I have seven of these so I opened one up (after tooling a special two-pronged screwdriver) and found there is just one single hardware port (10-pin, my guess is USB compatible). It is obviously for upgrading firmware etc., but how?
So only the manufacturer and programmers can provide that info, and the FW-files. Just a question of contacting the right people…
BTW, thanks Philip_Street for your Philio PSP01-1 DTH ! (we seem to share a lot of hardware
I’m a bit of a newbie so apologies if I’ve missed something obvious.
When I try to save the script I get:
No signature of method: script_app_metadata_9d2b00a3_edf9_4a34_bcd8_847282dcadb1.metadata() is applicable for argument types: (script_app_metadata_9d2b00a3_edf9_4a34_bcd8_847282dcadb1$_run_closure1) values: [script_app_metadata_9d2b00a3_edf9_4a34_bcd8_847282dcadb1$_run_closure1@430d447d] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)
Any help would be greatly appreciated to mget my Greenwave NS210-g-EN switch working
If this helps replying now Tony I’m not sure what you have done there. Silly question, have you pasted it in as a new device handler in the developer site in the Code tab. This worked perfectly for me when I installed it in May so it should work fine
Bit of a long shot
Been using the DTH from the start and works perfect but i do have a couple of issues with the way the DTH displays on an Android S7 phone
The tile (now) for power useage and the oposite tile for resultant (W) used display really small Text values, so small i can barely see them and the same goes for the (Since) tile and oposite value, again really small text
infact the since value tile is just blank ?? although the value in the oposite tile is displaying Kw/h
Any chance anyone can help with these couple of issues please