All:
It seems someare using a plain text editor to modify their configuration.yaml?
If so, this is not ideal - you need to use something that is YAML-aware. For example, HA has a VS code plug-in that I can recommend.
All:
It seems someare using a plain text editor to modify their configuration.yaml?
If so, this is not ideal - you need to use something that is YAML-aware. For example, HA has a VS code plug-in that I can recommend.
Thanks for the quick response that fixed it.
Hopefully over the next few days I can can my PIV responding to commands.
Which pins do I have to connect between ATmega32u4 and CC1101 to use evofw3? I prefer hardware UART communication. For the last couple of months, we have worked on a wireless USB Dongle that can communicate with some Orcon ventilation units in Home Assistant, soon we will order a new batch, I would be interested to see if we can run evofw3 as well. Also see this topic: link
You need to speak with Pete at GitHub - ghoti57/evofw3: Major overhaul of evofw2 Evohome listening software to use asynchronous radio mode - I know he has a H/W-based UART that he sells here:
The code supports 16MHZ atmega328 and 8/16 MHz atmega32u4 platforms. The atmega328 uses a SW Uart to interface to the cc1101 while the atmega32u4 uses a HW Uart.
I use one of these for test/dev, as well as a S/W UART, and a HGI80ā¦
I am not familiar with your project, and I am curious: what does it offer that ramses_rf does not? I am always willing to steal other peopleās ideas!
I have not yet implemented a Fan entity in ramses_cc, but that is comingā¦ This is a little difficult because the relationship between ventilation units and remotes is many-to-many (although most are set up one-to-one) - that is why I implemented the Remote entity first.
Actually, I am not sure a Fan entity is needed now!
I dunno if it will help you to know, but there are three āschemesā (the way the packet is laid out) for remotes (Orcon, Itho & Nuaire). Also, there are other command classes in addition to 22F1
& 22F3
, such as 22F7
(turn bypass on/off).
Thanks for your reply. I wanted to control my Orcon MVS 15 from Home Assistant, a few months ago, I didnāt really found a solution to do this, therefore I made one myself:
The RF USB Dongle, called FanX now , has Atmega32u4 and CC1101 transceiver. It has Arduino micro bootloader installed and can be flashed bij the Arduino IDE. The sketch uses Standard Firmata and abuses the ālightā and āsensorā entity as FAN speed. So only thing to get things to work is adding the Firmata code in configurations.yaml:
firmata:
- serial_port: /dev/serial/by-id/usb-Arduino_LLC_FanX_RF_Dongle-if00
serial_baud_rate: 57600
lights:
- name: fan speed
pin_mode: PWM
pin: 3
minimum: 0
maximum: 99
sensors:
- name: fan speed
pin_mode: ANALOG
pin: A0
differential: 1
The dongle will always stay in āclone modeā for 5 seconds just after applying power, if you press a button within this 5sec on the Orcon RF15 remote control, it will clone the addresses. Itās a very basic implementation to get things up and running pretty fast. At this time, only reading and controlling fan speed is supported:
Of course it can also be used in automations. But no reading (yet) of CO2 or whatsoever. At the moment I know it works at least with Orcon MVS 15 and HRC400.
Currently Iām working on a MySensors implementation as well (besides Firmata), that should enable support for Domoticz and others.
Theoretically, evofw3 should be able to run on this dongle by mapping the right IOās, but I was wondering if it would make sense to change the pinning in a way that evofw3 would run without modifications. One specific detail: My HW UART RX and TX of mcu, connects to GDO0 of the CC1101 only. The GDO0 is switched to RX/TX functionality, via SPI commands, just like the original RF15 remote control.
Actually, Iām looking for a way to run ramses_rf on FanX
Sorry, this is not my area - I simply have no idea what youāre talking about - speak to Pete.
Have you seen: HVAC remotes in the wiki. It doesnāt have auto-discovery, but that would be doable.
Hi David,
Unfortunately Iām still experiencing intermittent stability on 0.20.22. In this screenshot you can see it broke about 16hrs ago.
Looks like itās still because of the same error I posted last time:
This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/ramses_cc/climate_heat.py:299
Integration: RAMSES RF (documentation, issues)
First occurred: August 17, 2022 at 6:32:30 PM (3 occurrences)
Last logged: 4:00:03 AM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 519, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 566, in _async_write_ha_state
attr = self.capability_attributes
File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 239, in capability_attributes
self.hass, self.min_temp, self.temperature_unit, self.precision
File "/config/custom_components/ramses_cc/climate_heat.py", line 299, in min_temp
return self._device.config["min_temp"]
TypeError: 'NoneType' object is not subscriptable
This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/ramses_cc/climate_heat.py:152
Integration: RAMSES RF (documentation, issues)
First occurred: 1:02:32 AM (1 occurrences)
Last logged: 1:02:32 AM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 519, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 570, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 538, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 217, in state
if self.hvac_mode is None:
File "/config/custom_components/ramses_cc/climate_heat.py", line 152, in hvac_mode
if self._device.system_mode[CONF_SYSTEM_MODE] == SystemMode.HEAT_OFF:
TypeError: 'NoneType' object is not subscriptable
I think I have identified the issueā¦ I will push a fix to 0.20.22a
I can now partially control my Nuaire Drimaster-Eco-Link-PIV with this integration. I can now call boost, and it will put the fan into purge mode and call normal to set it to auto.
Thanks for all the hard work!
This will definitely stop.
This I need to know if it happens again.
Also @maesenator can you send me a 24h packet log please - I am wondering if your system has issues at the RF layer that is exposing this (otherwise unrelated) issue.
OK, version 0.20.22a released as a beta, fixes include:
TypeError: 'NoneType' object is not subscriptable
TypeError: 'NoneType' object is not subscriptable
When you say āpartiallyā - what canāt you do?
Version 0.20.22b has been released. Fixes some known issues.
Anyone running:
Iāve added config to yaml file to create a packet log. Will send it to you tomorrow after Iāve gathered 24hrs.
I need some 24h packet logs from people with Itho and Nuaire ventilation units - preferably with the remotes being used.
See here: Itho / Orco / Nuaire: Fan metrics, Remote control & Sensor faking via RF
I had the packet log, then updated to 0.20.22c while I removed the config entry for the log file, after the update finished the log file was removed.
I now have nothing.
Iāll make a new one for the next 24hrs and send it to you tomorrow.
Iāll send you the last 2 days of logs. They both should have remote button presses and service calls.
I have lots of sensors from my PIV, but most of them donāt update. Temp, humidity do, as does my Co2 sensor when itās plugged in.
Send you a PM with 9-days of packet logs hope you will find it usefull. My system is Itho.
Thatās really useful - can you send me your known_list
too?
Are you still using use_regex
?