Hi, everyone
I installed the Climacell Weather Service, I entered all the data according to the explanations, including latitude and longitude and why the data I get from it is inaccurate in the field of temp (I can not check the rest) Anyone encountered this phenomenon? Or know how to help me?
Attached a scree shoot of the programming page. 
Thanks

Use this site to get your latitude/longitude:  https://www.latlong.net/convert-address-to-lat-long.html

My guess is that your numbers are correct but you need to enter longitude as a negative number.  Entering that longitude as a negative number will put you in Pennsylvania   The pair you are using is on the other side of the world. 

Edited July 6, 20205 yr by MrBill

On 7/6/2020 at 6:32 AM, ZorMarom said:

I installed the Climacell Weather Service, I entered all the data according to the explanations, 

 

Hi Zor.

Wondering where you found the explanations for climacell? I can't make heads or tails. 

@andrewm Maybe you can help @PeterBarker11 to setup his Climacell app correctly.

10 hours ago, PeterBarker11 said:

Wondering where you found the explanations for climacell?

The name of the nodeserver in the Polyglot Store should provide a link to the github repository for the nodeserver, and that's where you'll find the README instructions for the nodeserver you're installing.  Just click on the name.  That may help provide you with some answers.

https://github.com/bpaauwe/udi-climacell-poly

 

Thanks very much. I was able to setup the parameters via the suggested link, but in the admin console interface I'm not receiving any data.

Now maybe I need to configure something on the isy side to present this data?

From a screen capture I've seen of someone's admin console weather node they are receiving several different fields of data.

This is for weatherbit but I'm assuming they should all present their data in a similar way.

@PeterBarker11I'm assuming based on your post in the other thread that this is now working for you?

In case anyone else sees this while looking for the solution.  I believe this was resolved by restarting the admin console.   When a new node server is installed, the admin console must be restarted before it can properly display the new nodes created by the node server.

yes that's correct. Thanks for pointing that out.

I'm realizing that trying to source answers to the same question from two different conversations may be bad practice?