I just installed this PG3 Node Server. It's showing 0 Nodes. (I added an API key obtained from my account at Sensibo.)

I had the PG2 version installed at one time and it added all 4 Skys. I didn't use it much however because of its limited functions. I just saw this PG3 version today and thought I'd try it out.

I have 4 Sensibo Skys in my home.

It should be exactly the same as the PG2 version in terms of functionality. 

If it's not working, please provide logs.

@bpwwer

Log PM'd

Thanks!

I believe I've fixed the problem.  Refresh the node server store and you should see version 2.0.1

Then restart the node server and it should install the new version.  If it still doesn't work, send me a new log.

It won't start. I tried restarting it a few times after refreshing the store. (2.0.1 shows in the store.)

Thanks for your help with this.

I PM'd another log.

Sorry, made a error in the code.  Try version 2.0.2.

That did it - thank you!

As with the PG2 version, there is a mix of fahrenheit and celsius (see screenshot). 

It would be great if it could have 'all fahrenheit' as a choice. I could set the transmitters to Celsius to match the Node server's only choice, but then when my wife changes the temp using Alexa they would be way off.

I understand you may not own any of these, so I'm happy to assist in any way you need me to.

And - I found this: https://support.sensibo.com/l/en/article/73outalwmi-sensibo-api-overview

 

Edited June 9, 20223 yr by Athlon

Forgot the screenshot:

I can see where that is confusing.  The code is also pretty confusing  as it doesn't really deal with temperature units at all.

If I knew more about programming I would tackle this for sure.

I may be way off on what I found, but in the file at github /profile/editor/editors.xml is the temp range allowed in my AC (18 to 30).

And in the API it refers to 

 "temperatureUnit": "string",

but 'temperatureUnit' is not in any of the files at github (that I could see). I wonder if that's meant for celcius or farenheit.

Yes, "temperatureUnit" is either "F" or "C" according to something I saw in the API docs.

The editor should have two ranges, one for each unit along with the matching UOM.    What I find strange is that the targetTemperature (which also doesn't use the correct UOM in the editor) is reported in "F" but is being set in "C"

The API isn't real clear on how the API knows which units to use when reporting temperatures.  Does the device itself have the ability to specify which units you want it to use?

18 minutes ago, bpwwer said:

Does the device itself have the ability to specify which units you want it to use?

Yes, by using the phone app.

Actually, for my purposes, the node server is usable for me. I use my mini splits (4 of them) to augment heating in the winter. I have a program in ISY that turns them on and off based on my Ecobee temperature sensors (using the Ecobee Node server). I've been using IFTTT for that, so having it local now is great.

The program also checks the outside temp as using the mini splits as inverters is not very efficient when it's below 20 degrees F outside.

The remotes that came with them (Mitsubishi) use RF, but with each button press other than 'On' or 'Off' they send ALL of the settings at once somehow. (So I can't use a device like a Harmony for example.) That is why I bought the Sensibo devices - they do that as well. Just changing the temp with those remotes also resends the commands to automate the directional fins, whether or not to heat or cool and a few other settings.

Even with the limited capability of the Node server - I can use it in ISY to just turn them on and off - so what I said earlier about confusion with the Node server and Alexa is not a problem. However, to use the Node server for more than just 'on' and 'off' (like setting a temperature) is not possible for me without that confusion.

Edited June 9, 20223 yr by Athlon

How do you feel about generating an API key for me so I see what the API returns and how it works.  Blindly making changes to the node server and having you test and report isn't very efficient.

I won't intentionally mess with the controls, I mainly want to see the data in the get queries.

I have no problem with that at all. I'll PM you when I can from home later unless I can do it soon from my phone. 

PM sent

Genius ?

2.0.3 is much better!  Thank you!