The issue with the LUA scripts and the “Anonymous plugin acquired!” was escalated, reviewed, and resolved. The fix was included in a build that is being tested as a future firmware release.
The virtual switches problem is currently under investigation. However, we may have tools to remove virtual devices. If you want to remove a specific virtual device, please let us know through firstname.lastname@example.org or send me a PM with the name of the device and I’ll take care of it.
I just wanted to ask what the plans are with the data logging function. I found some older entries (ECS-323, ECS-267, ECS-194) on this subject. Should we combine these into a new feature request? Is there a timetable for when this feature will be installed?
Where would the data be stored? Would the internal memory easily suffice for this (are actually just a few numerical values) or would that be outsourced to the cloud? Perhaps an external memory could also be specified (USB stick or NAS).
An easily configurable interface would be great, where you can view the values in real time and customize the display (period, chart type, etc., overlay several series of measurements from different devices, etc.). An export as a dashboard tile would also be great.
It would also be cool if the data obtained from this could also be used for MeshBots. For example, define the average temperature value of the day or other period as an expression, or carry out an action if switch XY is pressed more than 10 times a day.
It should also be possible to specify how often the data is collected/stored. For example, temperature data from device XY every 10 minutes, humidity every 20 minutes, etc.
OK I tried it too and cannot delete a virtual switch.
I am unwilling to log into my device via SSH to get a command line and execute from there. I don’t believe any operation should be that cryptic for these devices. I consider using the online API tool the upward end of complexity for me.
So its back to you EZLO… You were good enough to add a creation of virtual switches via simple means. The delete device system needs to be able to delete virtual switches as well. That seemed an obvious user requirement (i.e. if you can create something you should be able to delete it as well) but ergo here it is.
OK so I went the SSH route and was able to delete the two virtual switches I didn’t need. It forced me to use Putty and SSH into the device log in as root and then create /tmp directory to copy the remove command to. I then executed it successfully on the two device id’s.
I tried to delete the /tmp directory after I was done but got an error so I don’t know if the copied files are still there or not.
The virtual switches are now missing in the iPhone app and the device section of the ezlogic.mios.com device area. But they still show up in the dashboard section of the ezlogic.mios.com GUI. Not sure why they persist there. I did do a reboot of EZLO and re-logged into ezlogic.mios.com but the now missing virtual switches are still showing on the dashboard.
Lastly this is far too cryptic a way to manage the device. If the target market is to bring home automation to the masses, Linux command line shells is not the way to get there. Those are the techie fringe users and aren’t a big enough population to get this to a critical mass marketplace.
Bottom line, a GUI based “remove virtual switch” function is needed to complement the create virtual switch recently added in.