Git Product home page Git Product logo

evofw3's People

Contributors

brucemiranda avatar ghoti57 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

evofw3's Issues

Evofw3 in Domoticz

Short question. Is it possible to use this evofw3 in Domoticz combined with a nanoCul? If yes is there some guide on how to do this?

Sending commands

Hi,

I'm using evfw3 on a DiY NanoCul and receiving communication from the evohome environment goes well.
I also tried to send commands but without result. Is sending of commands supported with evofw3?

Regards,
Ed.

Error messages

I receive the error messages below when I use a nanocul usb stick in Domoticz. There are several devices discovered and works as expected but was hoping the error messages can be eliminated.

2023-11-11 19:06:33.218 Error: Evohome USB: evohome: unknown command 12c8
2023-11-11 19:06:56.216 Error: Evohome USB: evohome: unknown command 1298
2023-11-11 19:07:13.475 Error: Evohome USB: evohome: unknown command 31da
2023-11-11 19:08:13.561 Error: Evohome USB: evohome: invalid message structure - possible corrupt message
2023-11-11 19:08:35.352 Error: Evohome USB: evohome: unknown command 1298
2023-11-11 19:08:36.922 Error: Evohome USB: evohome: unknown command 1fd4
2023-11-11 19:08:41.773 Error: Evohome USB: evohome: unknown command 2e10
2023-11-11 19:09:29.766 Error: Evohome USB: evohome: unknown command 31e0
2023-11-11 19:09:37.971 Error: Evohome USB: evohome: unknown command 2e10
2023-11-11 19:09:42.831 Error: Evohome USB: evohome: unknown command 31d9
2023-11-11 19:10:06.858 Error: Evohome USB: evohome: unknown command 31e0
2023-11-11 19:10:19.075 Error: Evohome

nano CUL not working

I bought a nano CUL, but after loading this software nothing happens.

I suspect that the pinout of the device is different from the pinout that is currently supported.

The device I have is this one: https://www.smart-home-komponente.de/nano-cul/nano-cul-868-extern/
I guess - on inspection - that the cc1101 is connected to 3.3V, while there is only a board definition for a atmega328p w/ 5V.

I followed the instructions from the README, pointed the arduino UI to evofw3.ino and pushed 'Upload'. There were no errors in that step.

From here I expected the 'Serial Monitor' to show some output. nothing. I tried giving commands like !F, V, !V, etc but there never was any response from the Arduino.

Can anyone give me some pointers on how to proceed debugging?

Thanks,

Jacco

Header wrong in Wiki

I can seem to edit or send a PR for a wiki page.

The header description on: seems wrong:
https://github.com/ghoti57/evofw3/wiki/Message-Body#message-body
The wiki states:

00 RQ
01 W
10 I
11 RP

However in the code:

static char const * const MsgType[4] = { "RQ", "I","W","RP" };

The order is: { "RQ", "I","W","RP" }
W and I seem to be swapped in the Wiki page.

Correct order according to the code:

00 RQ
01 I
10 W
11 RP

(I'm quite sure this is wrong in the Wiki, as I handcrafted a packetheader based on the wiki, and an I message was recieved as W by a real HGI80)

I'd be glad to submit a PR to the wiki, but can't figure out how.

No response on specific command

Update: Same behaviour with the latest 0.7.0 firmware.

When I issue the 0x10E0 request targeted to a specific device to an Arduino Nano, running the evofw3 firmware (evofw3\uart 0.6.1), I get no response (even when retrying 10 times). To other devices I do get a response. However when I issue the exact same request via an HGI80 to that specific device I do get a response.

The request that fails to get a response is:

RQ --- 18:000730 10:014494 --:------ 10E0 001 00\r

When I monitor the request being sent by the evofw3 firmware using an HGI80 I see the following:

067 RQ --- 18:070150 10:014494 --:------ 10E0 001 00

When I issue the exact same request (so using 18:000730 as the source) and monitor the request on the device running the evofw3 firmware, I see:

095 RQ --- 18:009964 10:014494 --:------ 10E0 001 00

So the only difference seems to be the source address mapping.

When I issue the request via the HGI80, the response (directly after the first request) I get is:

067 RP --- 10:014494 18:009964 --:------ 10E0 038 000001C8810B0700FEFFFFFFFFFF140807E35238383230000000000000000000000000000000

Do you have any clue why there is no response when using the evofw3 firmware and an CC1101 while there is a response when using a n HGI80?

Setting controller mode or set point not working from Domoticz

Hi,

I bought a NanoCUL a few months back to be able to control my Evohome from Domoticz.

Have been able to discover all valve, but I'm not able to set the controller mode (normal, economy, off, ...) or set points.

I do see Domoticz sending the command, but don't see any response to that:

000 W --- 18:003618 01:204708 --:------ 2E04 008 01FFFFFFFFFFFF00
000 W --- 18:003618 01:204708 --:------ 2E04 008 00FFFFFFFFFFFF00

Somebody I know has a real HGI80 and he sees the following when changing controller mode:

095 W --- 18:012786 01:072015 --:------ 2E04 008 01FFFFFFFFFFFF00
049 I --- 01:072015 --:------ 01:072015 2E04 008 01FFFFFFFFFFFF00
047 I --- 01:072015 01:072015 --:------ 2E04 008 01FFFFFFFFFFFF00
095 W --- 18:012786 01:072015 --:------ 2E04 008 00FFFFFFFFFFFF00
049 I --- 01:072015 --:------ 01:072015 2E04 008 00FFFFFFFFFFFF00
047 I --- 01:072015 01:072015 --:------ 2E04 008 00FFFFFFFFFFFF00

Not sure what the three digits at the beginning of each line represent, but I noticed that in my setup it's always 000 when the second column is showing 'W'.

I understood that TX should be working with the latest firmware, or am I wrong?

Please let me know if you need me to run any tests or in case you need more information.

Thanks,

Frank

ATMega328p stops responding, also weird response to "!F"

Hi,

I have evofw3 running on a 5V ATMega328P. Every now and again (~24-48h) it's stopping emitting any packets and doesn't respond to commands, requiring a reset. I appreciate it may be just the board but on connecting it to my dev PC just now I ended up in a strange state where it wasn't emitting packets but still responded to !F (I'm using that to test comms) - and then spontaneously fixed itself.

Does this point to any specific issue? I appreciate it may be unrelated to the loss of comms I've been getting (when that happens it won't respond to !F)

thanks

!F
# !F F=216572
082 RQ --- 30:071715 01:067930 --:------ 10A0 001 00
074 RP --- 01:067930 30:071715 --:------ 10A0 006 001518000384

etc etc, then board stops emitting packets, but still responds to the !F command with weird numbers, before eventually spontaneously fixing itself:

!F
# !F F=710000
!F
# !F F=442200
!F
# !F F=700000
!F
# !F F=440000
!F
# !F F=210000
!F
# !F F=220000
!F
# !F F=440000
!F
# !F F=620000
066 RP --- 01:067930 30:071715 --:------ 0006 004 00050962
081  I --- 04:146860 --:------ 04:146860 30C9 003 0007E0
089  I --- 04:146848 --:------ 01:067930 12B0 003 060000
081  I --- 04:146848 --:------ 01:067930 12B0 003 060000
!F
# !F F=216572

EDIT: this may be a power supply issue!

nanoCUL not transmitting

Hi all,

I seem to have an issue with evofw3 and my "german" nanoCUL. I flashed initially the latest version of evofw3 but it does not seem to work - the device "is" transmitting (i think) but no one ever responds back.

If I flash the calibrate branch, I can now talk to most devices - they all respond and quickly. Unfortunately, it's only the controller that does not want to respond back but only randomly to some commands. It doesn't even work for ping. But it all works fine for OTH and other devices.

Any suggestions as to what I can try next?

Thanks.

No longer working after upgrading to 0.7

I've just tried to upgrade from 0.4.4 to 0.7.

It's compiled ok and uploaded to the board, but all I'm getting is the version number message, no packets are being decoded.

I have followed the instructions in the readme, selected atmega328P (SW UART). Any clues on what the issue might be?

Starting tuning process on Raspberry Pi

Hi, im trying to check if my setup is working.
I was guessing to check if the autotune process could be run on my Pi.

i tried screen /dev/ttyUSB0 115200 as mentioned in this post:
#6 (comment)

But i doesnt work.
Any tips if this is possible to run on a RPI? If you need any info from me please let me know.
Im not the biggest expert on all of this but im eager to learn and fixed a lot of other things on the RPI.

flashing to nanocul not working

Hi,

I bought the NanoculV3 board linked to under Hardware UART here in the wiki, then followed the Arduino-IDE instructions to flash the firmware.

However I always get these errors in the Arduino IDE:

Arduino: 1.8.16 (Linux), Board:"atmega32u4 (HW UART), atmega32u4 (3.3V 8 MHz), SHA atmega32u4"

De schets gebruikt 18534 bytes (64%)  programma-opslagruimte. Maximum is 28672 bytes.
Globale variabelen gebruiken 1525 bytes (59%) van het dynamisch geheugen. Resteren 1035 bytes voor lokale variabelen. Maximum is 2560 bytes.

avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
Found programmer: Id = ""; type = 
 Software Version = 
avrdude: butterfly_recv(): programmer is not responding
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: buffered memory access not supported. Maybe it isn't
a butterfly/AVR109 but a AVR910 device?
avrdude: initialization failed, rc=-1
         Double check connections and try again, or use -F to override
         this check.
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: leave prog mode
avrdude: butterfly_recv(): programmer is not responding
avrdude: error: programmer did not respond to command: exit bootloader
avrdude: error: programmer did not respond to command: exit bootloader

I played around with the settings for 'pinout', 'processor' and 'programmer', but the result is always the same.

Anybody has an idea how to fix this?
Thanks in advance.

No serial communication after successful board programming. nanoCUL board advice needed

Maybe more hardware related than evofw3, but posting here as I am not sure where else to ask:)

Picked up one of these:
https://www.amazon.de/-/en/gp/product/B07T3H8VF2/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

Seems to be the correct radio, frequency and Firmware.
Received yesterday and installed using Arduino IDE (on MacOS) using the following settings:

GetBoard Info returns: atmega328p (SW UART)

So its set up like so:

Tools-> Board "atmega328p (SW UART)"
Tools-> Processor "atmega328p (5V, 16MHz)"
Tools-> Pinout "Nano"
Tools -> Host "115200"
Tools-> Port = "/dev/cu.usbserial-A50285BI"
Tools - Bootloader "Standard Bootloader"

Sketch -> Verify/Compile
Sketch-> Upload

Both complete with no error

In serial monitor of Arduino IDE there is no output
In terminal monitor there is no communication
Using "screen" command in linux there is no output

Any advice on how to see output form the board or to test if it is actually working?
How often do these devices fail? As Sketch->Upload did not complain, I assume that the board is working.

I just can't see any output (hence ultimate use with ramses_rf/ramses_cc/HA does not see any output.)

Any advice on how to get this responding?

Many thanks

enhancement request: trace flag for device_id

@ghoti57 it would be useful to be able to deterministically discover the evofw3 dongle's device_id.

My use case include scenarios where users have (or potentially have) more than one gateway, so that I can work out which is which without them having to tell my code that things are so.

I note it would also be useful to have this data even whilst having the device in a read-only mode, so sending a dummy packet is not preferred (and I can't be absolutely sure the packet I'm seeing wasn't from another dongle).

The obvious solution would be a traceflag, or to include this data in the !V response.

STM8

Hi
I have the Ebyte E07 dev board with uart. The processor is an stm8, does anyone know how to port this code for an STM8?

Esp8266 or esp32 usefull

Hi,

is it possible to use an ESP8266 or an ESP32 with an attached CC1101 instead of the Arduino?
It would require a rewrite of the code I guess ( watchdog, io, timing, ISR or others perhaps)
but would it be possible?

no messages

I am using nanoCUL (Arduino Nano V3.0 ATMEGA328P + C1101 868 MHz), but no messages are coming even using minicom

minicom -D /dev/ttyUSB0

nanoCUL is plugged to Raspberry Pi 4b.

For flasing fimware I used Arduino IDE, exported binary to Raspberry and successfully flashed using

avrdude -v -p atmega328p -c arduino -P /dev/ttyUSB0 -b 57600 -D -U flash:w:/home/pi/evofw3.ino.arduino_standard.hex:i

dmesg

[ 0.130508] usbcore: registered new interface driver usbfs
[ 0.130593] usbcore: registered new interface driver hub
[ 0.130728] usbcore: registered new device driver usb
[ 0.131103] usb_phy_generic phy: phy supply vcc not found, using dummy regulator
[ 1.144221] usbcore: registered new interface driver r8152
[ 1.144302] usbcore: registered new interface driver lan78xx
[ 1.144378] usbcore: registered new interface driver smsc95xx
[ 1.149552] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 1.149591] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.149627] usb usb1: Product: xHCI Host Controller
[ 1.149655] usb usb1: Manufacturer: Linux 5.4.83-v7l+ xhci-hcd
[ 1.149684] usb usb1: SerialNumber: 0000:01:00.0
[ 1.151575] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 1.151611] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.151645] usb usb2: Product: xHCI Host Controller
[ 1.151673] usb usb2: Manufacturer: Linux 5.4.83-v7l+ xhci-hcd
[ 1.151701] usb usb2: SerialNumber: 0000:01:00.0
[ 1.154857] usbcore: registered new interface driver uas
[ 1.154977] usbcore: registered new interface driver usb-storage
[ 1.166346] usbcore: registered new interface driver usbhid
[ 1.166373] usbhid: USB HID core driver
[ 1.512911] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.695619] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.695659] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.695690] usb 1-1: Product: USB2.0 Hub
[ 1.843264] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 1.874575] usb 2-1: New USB device found, idVendor=152d, idProduct=1337, bcdDevice= 5.08
[ 1.874613] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.874644] usb 2-1: Product: jmicron
[ 1.874670] usb 2-1: Manufacturer: jmicron
[ 1.874697] usb 2-1: SerialNumber: 7F833EEF5DC0
[ 2.023003] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
[ 2.166652] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2.166692] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.166727] usb 1-1.2: Product: NANO CUL
[ 2.166754] usb 1-1.2: Manufacturer: SHK
[ 2.166780] usb 1-1.2: SerialNumber: 868
[ 8.009488] usbcore: registered new interface driver usbserial_generic
[ 8.009560] usbserial: USB Serial support registered for generic
[ 8.075826] usbcore: registered new interface driver ftdi_sio
[ 8.075944] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 8.076399] usb 1-1.2: Detected FT232RL
[ 8.087741] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
[ 8.251806] usbcore: registered new interface driver brcmfmac

lsusb

Bus 002 Device 002: ID 152d:1337 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Still I am not receiving any msg from nanoCUL on serial:

minicom -D /dev/ttyUSB0
Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 11:43:54

Press CTRL-A Z for help on special keys

.# evofw3 0.6.6

Can you help me with this issue?

Thanks

BusWare SSC

I was wondering if the firmware was compatible with this module?

It's a board that sits on top of a RB Pi, compatible with 'culfw' firmware.

image

Please add License

I don't really mind what license.

I quite like MIT license (https://choosealicense.com/licenses/mit/) - that what I generally now use, and what others Evo projects like https://github.com/zxdavb/ramses_rf use. It's simple and permissive.

(In the past I've used the Zlib/LibPNG licenses before https://en.wikipedia.org/wiki/Zlib_License but not so much recently. NOTICE: the Zlib license doesn't require copyright attribution for binary distribution, but the MIT does. BSD licenses have multiple versions which has really discouraged their use).

I don't mind sharing licenses like GPLv2 or GPLv3 at all. No problems with them either - and I use them on some code.

https://choosealicense.com is a good start.

If there are blockers to doing this, then let's discuss here...

can't program this onto my UNO

I can't upload this to my standard Arduino UNO (ATMEGA328P). If I set my board option to atmega328P (SWUART) It fails to upload immediately saying #error no baud rate defined. If I set the board type to atmega32U4 (HW UART), it gets further, but comes up with: Connecting to programmer: .avrdude: butterfly_recv(): programmer is not responding. This error gets repeated multiple times. My programmer is set to AVRISP - although changing that makes no difference. Please - have you any ideas?

Strange behavior on Remeha Elga Ace heatpump after activating Nanocul (evofw3) with Home Assistant (ramses_cc)

Description of setup:

Evohome controller, connected to Remeha Elga Ace heatpump with R8810A1018 (Opentherm module)
Firmware version: WiFi module: 02.00.17.00, Application module: 02.00.19.33

Home Assistant config:

ramses_cc:
  serial_port: 
    port_name: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0
    baudrate: 57600  #  default: 115200
  packet_log: 
    file_name: packet.log
    rotate_backups: 30

Nanocul from this supplier: https://schlauhaus.biz/en/product/nanocul-868/
Firmware: 0.7.1

Problem

After setup of the nanocul and software, all the sensors and entities became visible in Home Assistant. However, the heatpump started showing strange behaviour. Even though there is a heat demand from the Evohome to the heatpump, and output/return watertemp are below set point, every 6-10 minutes the heatpump stops heating for about 2 minutes. After this, the heatpump turns back on. The display on the heatpump doesn't show anything abnormal or error codes.

As soon as I disabled the ramses_cc plugin in Home Assistant, the heatpump started operating normally again. This can be seen in the energy diagram as attached. There was constant heatdemand most of the time between 11.35 and 13.50, but the heatpump was switching on and off. The peak around 13.40 was caused by setting the Evohome to 25 degrees to force a very high setpoint, but here the heatpump also stopped way before the setpoint was reached.

I disabled the plugin at 13.50. The Evohome send heat demand between 13.50 - 14.15 and 14.40 - 15.08. Between these timestamps, there is clear correlation between heat demand and power usage. Between 14.56 and 15.08 there was heat demand, but the heatpump reached it's setpoint. Therefore only the circulation pump was active which causes the lower power usage.

elga_energy_usage

Outdoor temperature is between 10-15 degrees celcius, so defreeze cycles are not relevant.

It seems like the nanocul is interfering the messages between the Evohome and heatpump (connected through R8810A1018) Could this be caused by active probing?

CC1101 to ATMEGA328P pinning

Can you please tell me the pinning between ATMEGA328P (standard UNO) and the CC1101. I don't fully understand atm328_pins.h which I presume sets this. Thanks

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.