3. NuCAL (Services) as an Action
Now you can enroll to the service (we are going to provide more services soon) and use it as an Action.
Let’s see how to use Google Sheets.
To create a spreadsheet using MeshBot you should do the following:
Go to Local MeshBot page
Select a NuCAL in Action
Select Google Sheets service
Select an Account
3.1 If you don’t have account yet, press “Add Account” button and go through authentication flow, opened in a new tab.
3.2 Select existing account
One step closer! Interestingly, all(?) my devices from my Vera Plus are now showing up in the dashboard - although they aren’t updating with the correct status. Not sure what’s going on there. My first thought was that it was the voi_control NuCAL integration partially working, such that the devices that Alexa could see were showing up…but then I realized that a WiFi device that is only on alexa wasn’t showing up, so maybe voi_control has nothing to do with it? Dunno
All of these new device tiles that have appeared from Vera firmware hubs are dead for me, no control and no status feedback.
It has also imported some Vera firmware 3rd party plugin devices but not all of them. I can now see some tiles on the dashboard relating to the following Vera plugins, Harmony, WOL with Ping, MSW Weather, RGBW Controller etc.
Also no Vera firmware hubs appear in the dashboard filters in the Controllers section. I think this was possibly unintended for these devices to appear at this time. This has happened before also in the past, where devices from Vera firmware hubs were visible on the Ezlo Dynamic Dashboard.
Ideally in the longer term we would like for devices from Vera firmware hubs to appear into the Ezlo system, in to the dashboard and into meshbot rules etc. I could then stop using Rene’s bridge plugin and not bridge over any devices and instead allow their system to natively make them appear.
However I would have two feature requests if this is to happen with official support.
Ability to block a Controller and all of its devices from appearing in to the Ezlo system if desrired. For example my Vera Edge is a 100% test hub and I wouldn’t want any of its devices to appear at all into the Ezlo System.
Ability to pick and choose which devices from a Vera firmware hub are allowed to appear into the Ezlo system, for example on my production Vera Plus I would want most of its devices to appear on the Ezlo System, but there are certain devices I would want to block and restrict from appearing and would not want those to be seen on the Ezlo dashboard / meshbots etc.
You can probably use Rene’s Vera to Ezlo Bridge plugin here, to get your DSC devices from your Vera controller into the Ezlo system and they will work that way.
That’s assuming the DSC Vera plugin adds its devices as standard Vera device types.
I for example have AltHue Vera plugin devices (Philips Hue Lights) on my Ezlo Plus and they work via the bridge plugin.
Thanks for confirming that’s what I thought. Hopefully in the future then support for devices still paired to Vera firmware hubs to be presented into the Ezlo system.
Yeah, probably, but I’m trying to avoid “band-aid” fixes (even good ones!) in favor of keeping my Ezlo installation as “pure” as possible (though I did cave and install MSR recently…) until such a time as I can move over 100%. From what I’ve seen/heard, I’m hopeful that the Ezlo team will be able to get at least a Beta version of the DSC plugin out in the next month or two, which I think will be the tipping point for me. We’ll see
have you tried the Virtual Container capability in EZLogic? (you can create a Virtual device and link it to properties of as many devices as you want).
