We have updated our native Ezlo Weather integration as well as our OpenWeather integration, latter of which you can use if you have an API key, to expand their capabilities, which means you can make use of an increased number of parameters for your MeshBot automations!
The new parameters include, in addition to temperature,
Feels like temperature
Minimum and maximum temperatures for the day
Atmospheric pressure
Humidity
Weather description, e.g., Clear
Wind speed
As well as information on your selected location like its coordinations, if you like
To use the Ezlo Weather or OpenWeather integration, head into MeshBot automations and add it as an action. From there, you can assign any value provided by Ezlo Weather or OpenWeather to a cloud variable for use with your other MeshBots using our drag & drop interface.
I tried creating a Notification Meshbot for a freeze warning but when I select âNuCALâ from the Node Type dropdown I get âErrorâ next to it and cannot proceed.
We were able to replicate this on v 1.42.2 of Ezlogic. Before we go ahead and report this, can you try to set up the notification as a cloud Meshbot with a notification action?
Select a Cloud Automation Meshbot from the Meshbot type list.
Add a Notification action with a Cloud variable as a trigger
The cloud variable in there you will have to create by outputting the result of an EzloWeather request to that variable. In order to do this, create another test meshbot just to get the service started (you can do a cloud or local automation meshbot for this matter)
Under the action tab, select a NuCal action, select the EzloWeather or OpenWeather service, and select the account that you have set up from the Integration > NuCal tab on Ezlogic.
This should initiate your service and create a variable for you to use as a trigger in a cloud meshbot. You should be able to compare the value of that variable to 0 °C to get a freezing alert.
When I added Ezlo Weather it prompted me twice and I didnât realize it and it created two instances. I deleted both and added it again and exited out when it prompted me for the second instance. But I see nothing on my Dashboard. Am I doing something wrong or it this yet again another bug?
Hello Tim, after adding Ezlo Weather you wonât see it reflected in the dashboard.
Have you tried to use the Ezlo Weather integration heading into MeshBot automation and add it as an action? From there, you can assign any value provided by Ezlo Weather to a cloud variable for use with your other MeshBots using our drag-and-drop interface. If yes, please include a screenshot of the error setup youâre getting.
In addition to our last reply, I tried to replicate the scenario on my end and noticed that the service that stores the variable is not keeping them when requested, so, according to the previous example, in order to get the temperature you would request the variable by using a meshbot:
In theory, after testing the variable, it should keep it.
And then using it to trigger the scene, but whenever we tried to use it, it is empty, so it is one of the reasons why the trigger is not complete for now:
But no worries, I have already requested my Dev team to work on this so you can get a resolution on this matter, we are sorry for the delay, but we assure you we are working in order to get it fixed! Iâll keep you posted.
I get the following error when I try to TEST
{error_code: 200, error_text: â{âdataâ:null,ânucalErrorâ:âError: Po model EzloWeather__1.0.0-MVP as name or parjectId does not exist!\n at PoConfig.getPoModel (/app/node_modules/po-module/config/PoConfig.js:139:13)\n at PoConfig.getMethodDefinition (/app/node_modules/po-module/config/PoConfig.js:145:35)\n at NucalParjectFlow.flowContinue (/app/node_modules/po-module/flow/NucalParjectFlow.js:56:41)\n at ExternalCustomerFlow.flowContinue (/app/node_modules/po-module/flow/ExternalCustomerFlow.js:45:37)\n at PoModule.orchestrate (/app/node_modules/po-module/PoModule.js:41:41)\n at /app/src/routes/custom.js:80:39\n at dispatch (/app/node_modules/koa-router/node_modules/koa-compose/index.js:44:32)\n at next (/app/node_modules/koa-router/node_modules/koa-compose/index.js:45:18)\n at /app/node_modules/koa-body/index.js:141:14\n at runMicrotasks ()â}â}
error_code: 200
error_text: "{âdataâ:null,ânucalErrorâ:"Error: Po model EzloWeather__1.0.0-MVP as name or parjectId does not exist!\n at PoConfig.getPoModel (/app/node_modules/po-module/config/PoConfig.js:139:13)\n at PoConfig.getMethodDefinition (/app/node_modules/po-module/config/PoConfig.js:145:35)\n at NucalParjectFlow.flowContinue (/app/node_modules/po-module/flow/NucalParjectFlow.js:56:41)\n at ExternalCustomerFlow.flowContinue (/app/node_modules/po-module/flow/ExternalCustomerFlow.js:45:37)\n at PoModule.orchestrate (/app/node_modules/po-module/PoModule.js:41:41)\n at /app/src/routes/custom.js:80:39\n at dispatch (/app/node_modules/koa-router/node_modules/koa-compose/index.js:44:32)\n at next (/app/node_modules/koa-router/node_modules/koa-compose/index.js:45:18)\n at /app/node_modules/koa-body/index.js:141:14\n at runMicrotasks
Still getting this error and now I canât delete the Ezlo Weather Enrollment?
It seems anything I try with this controller just doesnât work.
So according to tech support this is being rewritten and there is not timeline for a fix. I thought this was a production unit and was beyond beta testing and code rewrites.
Hello @Tim88
Sorry for the inconvenience you faced. We are still working on removing some technical limitations in this service. This service is temporarily disabled. We are removing it from the list of Cloud Services.
Meanwhile, you can use HTTP request in Local Meshbot with Open Weather API to get weather info.
