echoromeo / pynobo Goto Github PK

Hi! Been playing around with your Home Assistant implementation and found a couple of issues. Would love to get this working all the way but I am really new at this and not capable to try my self :(

Anyways this is what I have noticed:

1. The current temperature of the thermostats is not showed anywhere in hass what I can see?
2. The nobø system can be set up with magnetic sensors on windows nearby that deactivates the heat if opened, I'm not sure if this is even possible via the API but it would be great if these were visible in HassIO as well.
3. The thermostats I HassIO shows two different temperatures, one which I think have no feature? I believe it is used on units with both heating and cooling but its confusing on these.
4. In the nobø app it seems to be possible to change to all the different scenes but the "normal". If you set the normal in nobøs app it does not use the mode "program", it goes to "eco".

Which thermostats are you using on your radiators? Im using NCU 1R but will not hesitate to replace them with NCU 2R if necessary for better compatibility. Further Im using latest version HassIO on a raspberry pi (soon to be an intel nuc)

I hope you will continue to develop this and make it a real component, I would love it.

Thanks in advance!

Originally posted by @bubbzy in #9 (comment)

Hello,
NOBO HUB uses local time, but Home assistant uses UTC time internally and assumes that other integrations also use this time. During the handshake, the UTC time is sent to the NOBO HUB and this will cause a time shift in the switching times in the weekly calendar. It would be possible to fix this.
Thank you

Good day!
I have no experience with python. But I was very interested in your project. Tell me how can I call your script from php?

Hey,

First of all, thanks for doing this.
Been searching a while to integreate my hub to Home Assistant.

But, a newbie question..
How do I get this in to my system?

Best regards,

As an option to including this as a pluing for the various systems, how about implementing an MQTT client and let this run as a standalone service?

I get this error message when testing overnight in Home Assistant.
I guess this happens when the hub restarts:
Catch this exception as well?

Log Details (ERROR)
Sun Jun 17 2018 23:19:57 GMT+0200 (Central European Summer Time)

Unhandeled exception: [Errno 113] No route to host
Traceback (most recent call last):
  File "/config/custom_components/climate/nobo_hub.py", line 536, in socket_receive
    resp = self.get_response(True)
  File "/config/custom_components/climate/nobo_hub.py", line 507, in get_response
    response += self.client.recv(bufsize)
OSError: [Errno 113] No route to host

Fikk denne i natt som da viste seg å være "fatal" for pynobo.

2019-10-23 03:27:02 ERROR (Thread-2) [custom_components.nobo_hub.pynobo.nobo] Unhandeled exception: [Errno 113] Host is unreachable
Traceback (most recent call last):
File "/config/custom_components/nobo_hub/pynobo/nobo.py", line 381, in socket_receive
resp = self.get_response(True)
File "/config/custom_components/nobo_hub/pynobo/nobo.py", line 352, in get_response
response += self.client.recv(bufsize)
OSError: [Errno 113] Host is unreachable

Har endret koden slik at OsError fanges opp istedenfor ConnectionError og ser etterhvert om det blir bedre.

Edit: Ser nå at "Unhandeled exception: [Errno 113] Host is unreachable" forvirret meg. Den er jo håndtert i koden selv om det står "Unhandeled exception" og da nytter det ikke å fange OsError avbrudd.

Skal kikke litt på hvorfor ikke pynobo kommer i gang igjen av seg selv.....

Edit 2: Jeg er trøtt..... Å fange opp OsError er vist veien å gå allikevel

This won't be a real issue, more like a question:

In short: basically I can't get the current temperatures of any of the units, although I'd think this should be possible.

Longer story:

I have a Nobo Eco Hub and a number of NCU-2R units, everything is working very well, pynobo also sees the entire system, there are no problems at all, thanks a lot for the code!

What I'm wondering is this: how is it that the desired temperature of NCU-2R units can be set (in many different ways, app, on the unit itself using the physical buttons, etc), yet the current temperature cannot be read out. The reason I think it can't be read out is that in the code you have, line 269,

"168": Model("168", Model.THERMOSTAT_HEATER, "NCU-2R", supports_comfort=True, supports_eco=True),

So has_temp_sensor is False by default. And indeed the hub.temperatures ordered dict is always blank. The G00 response doesn't contain Y02 apparently (I use the example code from the README). Looking at MODELS it looks like only

"234": Model("234", Model.CONTROL_PANEL, "SW4", has_temp_sensor=True),

has_temp_sensor=True so I'd think pynobo will only report temperatures from this thing.

But I guess all units, even the simplest ones (with a thermostat) must know the temperature somehow, otherwise how do they know when to switch on or off, so why can't we read out this information? What is also suspicious is that on the official app the current temperature is not displayed anywhere either.

It's of course possible that I'm misunderstanding something.