... and I think I'll be working out a way to prevent people from changing the friendly names of climate entities.
Type: Posts; User: zxdavb
... and I think I'll be working out a way to prevent people from changing the friendly names of climate entities.
My official advice is to use name in params rather than _name in schema.
If one is null, then so would the other be... But that value just shouldn't be null, and I'd like to know why. You...
I have responded to s.webb in the HA forum... I suspect he was doing something inadvisable - it appears that he had a rather fat hand-crafted (aka 'input'/configured) schema. The configured schema...
It has had significant changes, I just haven't published them - will be doing so shortly enough - before Winter starts up again.
As I said - it's evohome (the Web API) version state attrs. I...
Nope. If I do something that drastic, I'll try to let you know.
Sorry for the delay in response (I don't check slack often - and I cannot tell why it doesn't alert me a message has been sent to me).
The confusion has a simple cause:
- climate.bedroom has a...
This is the recommended ser2net config for ramses_cc/ramses_rf on HA:
connection: &con00
accepter: telnet(rfc2217),tcp,5001
timeout: 0
connector:...
... and there's the various optimizations to consider.
You can bind a DTS92(E) as the sensor for an evohome zone - in fact, this is much better than using a TRV as a sensor (more realistic temperatures).
You have one sensor per zone, and each can be a...
I am reviewing ramses_rf packet logs with respect to UFH (underfloor heating) controllers and their heat demand.
This led me to question: are the optimizations available to evohome of any value...
FWIW: I use a Nefit EMS-OT (obtained from ROBBshop) on a WB Greenstar 26si (with a Honeywell/Resideo R8820A OTG) in the UK and it provide OpenTherm capability - it works *very* well for me.
FWIW: I use a Nefit EMS-OT (obtained from ROBBshop) on a WB Greenstar 26si (with a Honeywell/Resideo R8820A OTG) in the UK and it works *very* well for me.
Good work - I wonder if you should be playing with RQ|13:xxxxxx|3EF1...
It will tell you more about what the BDR is doing, internally.
Have you seen:...
It does.
To be clear - the binding is a device_id|idx pair.
By necessity, ramses_rf is reasonably strict with its validity checking. This is mostly due to the high rates of:
a) data corruption of frames (i.e. packets at the RF layer), and
b) the % of a)...
What do you mean by 'works' - do you mean the relay behaves as expected, or that the packet appears in the packet log (and you are not sure what the relay is doing)?
I haven't looked in detail at...
2022-11-10T12:15:00.639272 000 I --- 18:136212 63:262142 --:------ 7FFF 023 001101846177023630303038204931383A313336323132
They are not unexpected. In a way, they shouldn't be there, but I'd...
The sad fact is that and index of 00 means both the 1st zone (counting starts from 0) and 'unspecified'.
2021-10-30T04:30:27.913555 055 I --- 04:098455 --:------ 01:078710 1060 003 0BFF01 #...
I wasn't sure if it would work, now I can see why it wouldn't:
- if you were sending from 18:123456 to 18:123456 (they're the same), then ramses_rf would know to do "18:123456 ---:------...
BTW, try to avoid using zone_idx == `00` - it just leads to confusion.
You can use `0B`, say, but there is no reason why (e.g.) `0F` wont work.
If you want this:
I --- 18:136212 --:------ 18:136212 0008 002 00C8
Then shouldn't you be doing this:
- service: ramses_cc.send_packet
```
I --- 18:201486 --:------ 18:201486 1FC9 018 00-00084B130E FC-3B004B130E 00-1FC94B130E
```
They are either domain_ids, dhw_idx (usu. 00) zone_idx, or nothing (actually, from the CTL it's...
See: https://github.com/zxdavb/ramses_cc/wiki/2.-configuration.yaml#advanced_features
The above supports packets sent from the HGI (or compatible) - no impersonation.
For hose who come here in the future - this may be useful: HP Technote (sorry, is in Dutch)
Bruce may know for sure - but: IIRC, the BDR will ignore any such packet, unless it has been first bound to the source device (which would be the HGI80-compatible device).
If I implement...