Comments (11)
New version is released.
If gateway is added manually, not autodiscovery, then it is HA way to handle offline devices.
When HA will be ready to do autodiscovery on regex mdns addresess than component will be reconnecting automatically if gateway come online again. Follow this on update: home-assistant/architecture#306
About sensors. With new version of component you are now able to choose sensors from integration.
Please test it and give feedback in other issue if there are problems.
Closing this one.
from home-assistant-bosch-custom-component.
In next version I want to add a list of all available sensors and during setup user will choose which one suppose to fetched by component.
Currently I don't have much time, but hopefully next week I can manage to do it.
What thermostat do you own? Provide model and manufacturer.
from home-assistant-bosch-custom-component.
Gateway is a KM200, heating system is a Logamax plus GB162 and the controller is AFAIK an RC35/Logamatic EMS (do you refer to the controller as thermostat?). All Buderus.
Choosing sensors during setup sounds good!
from home-assistant-bosch-custom-component.
Seems you are working on it in the new config flow-branch, very nice. Otherwise integration still runs smooth.
Only when the gateway is unavailible (powered off) when starting HA it fails and it doesn't seem to try to connect afterwards, but I don't know if that's how HA-integrations behave normally or not.
from home-assistant-bosch-custom-component.
Thank you very much, it's working! Pressure is availible!
Only thing in the logs I noticed are these errors:
2019-12-05 10:39:47 ERROR (SyncWorker_12) [homeassistant.util.logging] Exception in update when dispatching 'bosch_climate_update': ()
Traceback (most recent call last):
File "/config/custom_components/bosch/climate.py", line 176, in update
self._target_temperature = self._hc.target_temperature
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/circuit.py", line 228, in target_temperature
self.current_mode, self.operation_mode_type
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/schedule.py", line 116, in get_temp_for_mode
return cache.get(TEMP, 0)
AttributeError: 'NoneType' object has no attribute 'get'
2019-12-05 10:39:47 ERROR (SyncWorker_3) [homeassistant.util.logging] Exception in update when dispatching 'bosch_climate_update': ()
Traceback (most recent call last):
File "/config/custom_components/bosch/climate.py", line 176, in update
self._target_temperature = self._hc.target_temperature
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/circuit.py", line 228, in target_temperature
self.current_mode, self.operation_mode_type
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/schedule.py", line 116, in get_temp_for_mode
return cache.get(TEMP, 0)
AttributeError: 'NoneType' object has no attribute 'get'
2019-12-05 10:40:30 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.hc4 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 450, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/bosch/climate.py", line 170, in update
self._target_temperature != self._hc.target_temperature or
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/circuit.py", line 228, in target_temperature
self.current_mode, self.operation_mode_type
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/schedule.py", line 116, in get_temp_for_mode
return cache.get(TEMP, 0)
AttributeError: 'NoneType' object has no attribute 'get'
2019-12-05 10:40:30 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.hc3 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 450, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/bosch/climate.py", line 170, in update
self._target_temperature != self._hc.target_temperature or
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/circuit.py", line 228, in target_temperature
self.current_mode, self.operation_mode_type
File "/usr/local/lib/python3.7/site-packages/bosch_thermostat_http/schedule.py", line 116, in get_temp_for_mode
return cache.get(TEMP, 0)
It seems that there are no temperatures in the hcN-entities, but I don't know if there should be.
Maybe it helps, if I should test something let me now.
For me it's perfect now as I have my outdoortemperature and systempressure!
from home-assistant-bosch-custom-component.
can you explain how your setpoints are working?
{
"id": "/heatingCircuits/hc3/switchPrograms/Eigen1",
"type": "switchProgram",
"setpointProperty": {
"id": "/heatingCircuits/hc3/temperatureLevels",
"uri": "http://THERMOSTAT/heatingCircuits/hc3/temperatureLevels"
},
"maxNbOfSwitchPoints": 42,
"maxNbOfSwitchPointsPerDay": 6,
"switchPointTimeRaster": 10,
"writeable": 1,
"switchPoints": [
{
"dayOfWeek": "Mo",
"setpoint": "day",
"time": 10
},
{
"dayOfWeek": "Su",
"setpoint": "night",
"time": 1430
}
]
},
from home-assistant-bosch-custom-component.
hc3 should just run always the same. As I couldn't find a possibility without switching it should change to "day" on Monday, 00:10 and to "night" sundays on 23:50.
1430 is the minutes from midnight, I think?
from home-assistant-bosch-custom-component.
what is purpose of HC3 and HC4?
so it stays on night program only on Sunday for 20 minutes?
Till now all rawscans we had covered whole week and I don't see a way in android app to delete one day
. So I made assumption that each switchProgram has to have: Mo, Tu, We, Th, Fr, Sa, Su
.
Yours is different. So now it is a question.
Is it stays on day
setpoint for whole week or is it going to off
state on Tuesday or something else...
from home-assistant-bosch-custom-component.
HC3 and HC4 are heating circuits, just like HC1 and HC2. We have heatingcircuit for basement, 1st floor, warehouse and hot water.
The program stays on day all week, just sunday 23:50 to monday 00:10 ist night.
I managed these setpoints on the RC35 itself, not in the app. I don't know if it is possible to do this on the app.
from home-assistant-bosch-custom-component.
I think I managed with it.
Update component to v0.5.4 and check out if HC3 and HC4 are working for you now.
from home-assistant-bosch-custom-component.
No errors whatsoever! hc3 and hc4 are updating fine! Thanks very much!
from home-assistant-bosch-custom-component.
Related Issues (20)
- unknown error occurred HOT 3
- TLS issue on init after upgrade to Homeassistant 2024.2.0 HOT 53
- Add ETRV “start calibration” button to the home assistant integration HOT 9
- Total working time is wrong interpreted by HA HOT 2
- Unknown model HOT 9
- Integration wont load after update to HA 2024.2.2 HOT 1
- Integration not loading on startup: Can't find your fw version. HOT 4
- Device is unknown Null HOT 3
- Statistics for the 23rd hour are always missing HOT 8
- Can't install Bosch-Thermostat HOT 3
- Failed to call service bosch/send_custom_put_string. Service call requires responses but caller did not ask for responses
- CT200 Current Set Temp HOT 1
- Using slower stringprep, consider compiling the faster cython/libidn one HOT 1
- Unknown Model HOT 7
- HCM300 energy values to measurements HOT 4
- Bosch CT200 new Firmware v5.00.01 is incompatible HOT 4
- CT200: Integration stopped working after HA update 2024.9 or after update to firmware 05.00.01 HOT 14
- Integration stops working after few hours HOT 16
- Integration stopped working for RC300 after HA update HOT 14
- Home page only shows logo when using ethernet connection
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from home-assistant-bosch-custom-component.