nobo_hub Temperature sensor reports target temperature instead of measured temperature after connection loss

GaupeLnx commented 1 year ago

The problem

I use pynobo with homeassistant and saw regualary a temperature spike in the loggings from the nobø sensor switch went int the homeassistant logging and saw every now and then the following logging: it reports the set temperature here while the sensor switch is set to use as temperature sensor. in the nobo app later on it reports the right temperature again

INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer) INFO (MainThread) [pynobo] connection closed INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer INFO (MainThread) [pynobo] reconnecting to hub INFO (MainThread) [pynobo] broadcast received: NOBOHUB102000010 from 192.168.1.15 INFO (MainThread) [pynobo] broadcast received: NOBOHUB102000010 from 192.168.1.15 INFO (MainThread) [pynobo] added/updated zone: stue . . INFO (MainThread) [pynobo] added/updated component: stor vindu venstre . . INFO (MainThread) [pynobo] added/updated component: sensor switch . INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000

This is an ECOHUB and with some radiators and one sensor switch

What version of Home Assistant Core has the issue?

Home Assistant 2023.1.4 Supervisor 2022.12.1 Operating System 9.4 Frontend 20230110.0 - latest

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

nobo_hub

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nobo_hub

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer)
INFO (MainThread) [pynobo] connection closed
INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer
INFO (MainThread) [pynobo] reconnecting to hub
INFO (MainThread) [pynobo] broadcast received: __NOBOHUB__102000010 from 192.168.1.15
INFO (MainThread) [pynobo] broadcast received: __NOBOHUB__102000010 from 192.168.1.15
INFO (MainThread) [pynobo] added/updated zone: stue
.
.
INFO (MainThread) [pynobo] added/updated component: stor vindu venstre
.
.
INFO (MainThread) [pynobo] added/updated component: sensor switch
.
INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000

This is an ECOHUB and with some radiators and one sensor switch

Additional information

As said the temperature shown in the SET temperature ins the sensor_switch In the APP that comes with the nobo you can choose between

Use as temperatur sensor in (and then select a room)

or

Local zone control (which is not chosen but set on 21C)

ib believe that it is the above tempertaure that is shwon instead of the sensor temperature right after the connection loss error

home-assistant[bot] commented 1 year ago

Hey there @echoromeo, @oyvindwe, mind taking a look at this issue as it has been labeled with an integration (nobo_hub) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `nobo_hub` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign nobo_hub` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

nobo_hub documentation nobo_hub source _{^{(message by IssueLinks)}}

oyvindwe commented 1 year ago

Thank you for the error report.

I'm not sure I entirely understand the issue. I assume you have SW4, which cannot set temperature, only mode (calendar/comfort/eco/away), either for a single zone or globally.

This message is from the library (and not the HA integration), and origins from the hub:

INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000

Are there any more messages with updated temperature?

Could you enable debug logging on pynobo and provide with the received messages? Look for log messages that starts with received: Y02

I suspect this is either a bug in the Nobø Ecohub itself, or in the pynobo library, or in the API documentation.

GaupeLnx commented 1 year ago

Your assumption is right (I assume you have SW4, which cannot set temperature, only mode (calendar/comfort/eco/away), either for a single zone..) the switch is an SW4 mounted on the wall in the livingroom and the /comfort and eco temperatures can only be set on the heater panel itself) thats why i put the switch in sensor mode)

i have enabled pynobo to debug mode and will come back with loggings after the issue has been logged again (mostly same time mornings around 7 )

Outside of that the sensor reports the right temperatures

the wrong one from the log (this time with a time stamp was 2023-01-17 07:05:56.323 INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000 the same issue upstood earlier in the night 2023-01-17 07:05:56.323 INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000 (loggings around are the same as shown in the original report

there where no sensor updates inbetween but also the heating was in ECO mode

the next one comes an hour later and reports N/A (whic is not normal on other times the next one is just a good temp)

2023-01-17 08:18:49.667 INFO (MainThread) [pynobo] updated temperature from 234000000211: N/A

then later on it shows the sensor temperatures again (i assume becasue of pressing the overide button on the switch COMFORT mode at 8:38 ) 2023-01-17 08:38:47.426 INFO (MainThread) [pynobo] added/updated override: id 312

2023-01-17 08:38:47.444 INFO (MainThread) [pynobo] updated temperature from 234000000211: 17.875 2023-01-17 08:38:48.153 INFO (MainThread) [pynobo] updated temperature from 234000000211: 18.000 2023-01-17 09:03:39.698 INFO (MainThread) [pynobo] updated temperature from 234000000211: 18.563

I have no earlier logs atm

From: Øyvind Matheson Wergeland @.> Sent: Tuesday, January 17, 2023 12:22 To: home-assistant/core @.> Cc: GaupeLnx @.>; Author @.> Subject: Re: [home-assistant/core] mobo_hub integration reporting set temperature from sensor switch after connection loss (Issue #86077)

Thank you for the error report.

I'm not sure I entirely understand the issue. I assume you have SW4, which cannot set temperature, only mode (calendar/comfort/eco/away), either for a single zone or globally.

This message is from the library (and not the HA integration), and origins from the hub:

INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000

Are there any more messages with updated temperature?

Could you enable debug logging on pynobo and provide with the received messages? Look for log messages that starts with received: Y02

I suspect this is either a bug in the Nobø Ecohub itself, or in the pynobo library, or in the API documentation.

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F86077%23issuecomment-1385277726&data=05%7C01%7C%7C68dee89e370d4210179308daf87d2f87%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638095513788612075%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M4yY7GoJIgKoCy7sCKbSJNJgXzXj5ddmyGjIZIMycbU%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ7SO7S5ECQWUD6JGBT7BEDWSZ6I5ANCNFSM6AAAAAAT5WOHHM&data=05%7C01%7C%7C68dee89e370d4210179308daf87d2f87%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638095513788612075%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QWcnNY1Hv%2Fo06lwj1NT%2Fstj30O%2BuiZvnVQJ5g0ZSTG0%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

GaupeLnx commented 1 year ago

I have switched on debugging for the integration Nobø_HUB in Settings / devices and services / tab integrations But am not sure if that is enough or otherwise do not know where to find the extra loggings Should they be in the same file ? I see some very few INFO

like

2023-01-17 12:46:36.467 INFO (MainThread) [homeassistant.setup] Setting up nobo_hub 2023-01-17 12:46:36.467 INFO (MainThread) [homeassistant.setup] Setup of domain nobo_hub took 0.0 seconds

but they where also in older logfiles

please advise how to get debug loggings for nobø_HUB integration

From: Øyvind Matheson Wergeland @.> Sent: Tuesday, January 17, 2023 12:22 To: home-assistant/core @.> Cc: GaupeLnx @.>; Author @.> Subject: Re: [home-assistant/core] mobo_hub integration reporting set temperature from sensor switch after connection loss (Issue #86077)

Thank you for the error report.

I'm not sure I entirely understand the issue. I assume you have SW4, which cannot set temperature, only mode (calendar/comfort/eco/away), either for a single zone or globally.

This message is from the library (and not the HA integration), and origins from the hub:

INFO (MainThread) [pynobo] updated temperature from 234000000211: 21.000

Are there any more messages with updated temperature?

Could you enable debug logging on pynobo and provide with the received messages? Look for log messages that starts with received: Y02

I suspect this is either a bug in the Nobø Ecohub itself, or in the pynobo library, or in the API documentation.

— Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F86077%23issuecomment-1385277726&data=05%7C01%7C%7C68dee89e370d4210179308daf87d2f87%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638095513788612075%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=M4yY7GoJIgKoCy7sCKbSJNJgXzXj5ddmyGjIZIMycbU%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ7SO7S5ECQWUD6JGBT7BEDWSZ6I5ANCNFSM6AAAAAAT5WOHHM&data=05%7C01%7C%7C68dee89e370d4210179308daf87d2f87%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638095513788612075%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QWcnNY1Hv%2Fo06lwj1NT%2Fstj30O%2BuiZvnVQJ5g0ZSTG0%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.***>

oyvindwe commented 1 year ago

please advise how to get debug loggings for nobø_HUB integration

I think you have to configure it in configuration.yaml, e.g. like this:

logger:
  default: warning
  logs:
    homeassistant.components.nobo_hub: debug
    pynobo: debug

For more info, see https://www.home-assistant.io/integrations/logger/

oyvindwe commented 1 year ago

@home-assistant rename nobo_hub Temperature sensor reports target temperature instead of measured temperature after connection loss

GaupeLnx commented 1 year ago

First, i think there is some misunderstanding from my side. Lookin further into this, i don not think, there is such thing as a target temp for a zone on the SW4.

The temperature listed in the app is the sensor temperature. The loggings i see till now is that there is alllways a connection loss around 7 in the morning where the sensor temp that is read out afterwards is wrong. But on other times the sensor temp read out after the connection loss might... be right

This is too much on a specific time that i dont think its is a bug in nobo_hub probably not even in pynobo what causes this is not clear to me yet but i will keep an eye on it for myself and if relevant report back. Ofcourse, if you have any idea what might be happening here, i am very much interested in your viewpont.

from my viewpoint you can close this as not being a bug from nobø_hub integration. Thanx for you time !

Some part of last nigh loggings where you see that specificly the reading on 7.05 can not be right as you see also befor and after the decline in temperature keeps declining (the hub is namely in eco mode and the roomtemp is slowly going down) and only from 10:00 going up because the hub got switched to home mode

i show ALL the [pynobo] received: ['Y02', '234000000211' from last log and ALL the Connection Reset

2023-01-17 15:14:21.659 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.188']

2023-01-17 16:22:59.194 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '20.938']

2023-01-17 19:05:19.119 INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer) 2023-01-17 19:05:19.125 INFO (MainThread) [pynobo] connection closed 2023-01-17 19:05:19.126 INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer 2023-01-17 19:05:19.126 INFO (MainThread) [pynobo] reconnecting to hub 2023-01-17 19:05:20.437 INFO (MainThread) [pynobo] broadcast received: NOBOHUB123456789 from 10.0.0.12

2023-01-17 19:05:22.302 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '20.938']

2023-01-17 19:32:17.824 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.063']

2023-01-17 22:41:38.206 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.125']

2023-01-18 01:05:27.022 INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer) 2023-01-18 01:05:27.022 INFO (MainThread) [pynobo] connection closed 2023-01-18 01:05:27.023 INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer 2023-01-18 01:05:27.023 INFO (MainThread) [pynobo] reconnecting to hub 2023-01-18 01:05:27.953 INFO (MainThread) [pynobo] broadcast received: NOBOHUB123456789 from 10.0.0.12

2023-01-18 01:05:30.214 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.125']

2023-01-18 01:20:37.276 INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer) 2023-01-18 01:20:37.276 INFO (MainThread) [pynobo] connection closed 2023-01-18 01:20:37.276 INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer 2023-01-18 01:20:37.277 INFO (MainThread) [pynobo] reconnecting to hub

2023-01-18 01:20:40.459 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.125'] 2023-01-18 01:33:05.907 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '20.563'] 2023-01-18 03:05:58.362 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '20.000'] 2023-01-18 04:28:06.718 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '19.438'] 2023-01-18 05:50:14.539 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '18.875']

2023-01-18 07:05:12.224 INFO (MainThread) [pynobo] lost connection to hub ([Errno 104] Connection reset by peer) 2023-01-18 07:05:12.225 INFO (MainThread) [pynobo] connection closed 2023-01-18 07:05:12.225 INFO (MainThread) [pynobo] Reconnecting due to [Errno 104] Connection reset by peer 2023-01-18 07:05:12.225 INFO (MainThread) [pynobo] reconnecting to hub

2023-01-18 07:05:15.361 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '21.125']

2023-01-18 07:33:46.784 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '18.250'] 2023-01-18 09:28:01.554 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '17.688'] 2023-01-18 12:05:04.591 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '18.313'] 2023-01-18 12:15:47.267 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '18.875'] 2023-01-18 12:30:04.102 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '19.500'] 2023-01-18 12:47:55.402 DEBUG (MainThread) [pynobo] received: ['Y02', '234000000211', '20.125']

oyvindwe commented 1 year ago

This looks indeed as a bug in the hub itself. It looks like the hub doesn't always store the last received value (from the SW4). When HA reconnects, it asks for a full status refresh, so at 07:05 I'd expect the hub to response with 18.875.

Some things to investigate:

Cause of connection reset
What does the app display when this happens
Hub firmware version

I suggest moving this discussion out of this issue. If you speak Norwegian, https://www.hjemmeautomasjon.no/forums/topic/4384-pynobo-nob%C3%B8-hub-python-interface/ or https://www.hjemmeautomasjon.no/forums/topic/267-nob%C3%B8-energy-control/ might be forums where someone else has experienced this

Please close this issue (as a codeowner only, I'm can't).

GaupeLnx commented 1 year ago

Thanx for the input! Closing this issue

home-assistant / core