Seite 3 von 9
Re: Neue FW V2.31.23
Verfasst: 11.01.2018, 06:52
von leonsio
nein ist es nicht
installiere diese einfach nach, sag dann bescheid ob es funktioniert hat
Re: Neue FW V2.31.23
Verfasst: 11.01.2018, 13:01
von Torben0209
Stanni hat geschrieben:
Die Module sind wohl nach dem Update verschwunden. Ist das normal:
Code: Alles auswählen
pi@hm-server:~ $ sudo yahm-module installed
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Installed modules:
Hatte genau das gleich Problem: CCU startete nach dem Update nicht.
-> Pivccu-Treiber neu installiert, dann lief es. Super, Danke!
Re: Neue FW V2.31.23
Verfasst: 11.01.2018, 18:51
von nort
leonsio hat geschrieben:hast du zufällig Gateway zusätzlich am laufen?
nehme an pivccu-treiber ist nicht geladen, homematic geht dann nur über das lan gateway
einfach pivccu-driver erneut installieren und Container Neustarten
mit yahm-ctl info müsste dir alternativ die Modul-FW angezeigt werden, damit kann man verifizieren ob der Treiber geladen wurde
Hallo
ich hatte nur eine erste Testinstallation mit der YAHM 1.8 gemacht und dummerweise manuell mit yahm-lxc -n KONTAINER_NAME -f -v -d /PFAD/ZU/FIRMWARE update die neue Firmware rauf gemacht und das was dann ab da waren IP und Wired beim Geräteanlernen weg.
Ich habe mir jetzt ne neue SD-karte genommen und die develop version von YAHM drauf gemacht jetzt ist beim anlernen zumindestens wieder Homematic und IP, Wired ist immer noch nicht da.
yahm-ctl info hatte module-FW 2.8.5 ausgegeben wenn ich mich recht entsinne.
grüß
Alex
Re: Neue FW V2.31.23
Verfasst: 11.01.2018, 20:46
von Centauri2k
Leo, habe das Modul neu installiert danach lief wieder alles. Scheint dann wohl ein bug im Update Prozess zu sein?
Re: Neue FW V2.31.23
Verfasst: 11.01.2018, 22:27
von leonsio
Ich schau mir den part nochmal an
Re: Neue FW V2.31.23
Verfasst: 12.01.2018, 11:20
von verleihnix
Nach dem Update startet HM nicht.
Habe dann den Treiber neu installiert.
Jetzt startet HM, aber die GUI bleibt blau, kein Content.
Code: Alles auswählen
sudo yahm-lxc update
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Installed version: 2.29.23
Available version: 2.31.23
Trying to create a config-backup from installed version 2.29.23, calling: 'yahm-backup data_backup' script
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Clean up TMP directory
Ask Rega to save the DOM
Creating Backup from /usr/local folder
Creating Homematic backup file
Clean up
STATUS: CCU2 Backup was successfully created: /tmp/YAHM/homematic-ccu2-1515751361.sbk
Backup old LXC config
Backup installed modules
INFO: Config backup file location: /tmp/YAHM_update/yahm/homematic-ccu2-1515751361.sbk
Creating full backup from installed version 2.29.23, calling: 'yahm-backup full_backup' script
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Trying to stop yahm container
Creating new backup from yahm version 2.29.23
tar: yahm/root/tmp/udev/control: socket ignored
tar: yahm/root/tmp/log: socket ignored
STATUS: Backup was successfully created: /tmp/YAHM/yahm_backup-2.29.23.tgz
Please start yahm container with 'sudo yahm-ctl -n yahm start' manually
INFO: Full backup file location: /tmp/YAHM_update/yahm/yahm_backup-2.29.23_20180112.tgz
Delete old YAHM Container version: 2.29.23
Deleting installed YAHM container: yahm version: 2.29.23 To cancel this operation type CTRL+C you have 5 seconds...
... too late ;)
Stopping LXC container
yahm is not running
Container can not be found or is not running
Deleting LXC container
Clean up
Create new YAHM Container version: 2.31.23
Creating new lxc container name: yahm, version 2.31.23
Downloading CCU Firmware
Extracting firmware
Extract ubi image
Writing to: /var/lib/lxc/yahm/root
Cleanup CCU2 source
Applying patch
Applying scripts
Creating SD card
Clean Up
Creating lxc config file
Container version 2.31.23 is created, please use 'yahm-ctl -n yahm start' to start and 'yahm-ctl -n yahm join' for console access
For network configuration see yahm-network script
Restoring old LXC config
Trying to restore old CCU2 backup, calling 'yahm-backup data_restore'
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Clean up TMP directory
Extracting CCU2 backup
WARNING: /usr/local folder with all settings inside yahm container will be removed. You have 5 seconds to cancel this operation...
... to late ;)
Extracting Backup Data
STATUS: Backup version 2.29.23 was successfully restored into yahm container version 2.31.23
Please start yahm container with 'sudo yahm-ctl -n yahm start' manually
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Starting yahm LXC container
sudo yahm-module -m pivccu-driver -f -v enable
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
Executing pivccu-driver module_install()
Found hardware: Raspberry Pi 3
Found OS: raspbian
Found kernel: 4.9.59
Trying to disable bluetooth on Raspberry Pi 3 to use HM-MOD-RPI-PCB
Trying to disable serial console
Serial already disabled
Installing/Setup overlay file
Creating Overlay files
pivccu-bcm2835.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
pivccu-sun8i-h3.dtbo: Warning (unit_address_vs_reg): Node /fragment@0 has a unit name, but no reg property
Setup Kernel Scheduler
kernel.sched_rt_runtime_us = -1
Preparing modification rfd.conf...
[Interface 0] block found in rfd.conf checking it...
Modification rfd.conf done.
Changing multimacd files
Changing lxc config
Copy startup files
PIVCCU was installed successfully, please restart your system to apply changes
STATUS: Module pivccu-driver was successfully installed
sudo yahm-ctl info
!!! You are using develop branch, this branch is unstable. Using at your own risk !!!!
YAHM Version: 1.9
CCU2 Current: 2.31.23
Module information
cat: /sys/module/plat_eq3ccu2/parameters/board_extended_info: No such file or directory
Das Log beim Start:
Code: Alles auswählen
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: ifplugd 0.28 initializing.
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Using interface eth0/4A:49:43:49:79:06 with driver <veth> (version: 1.0)
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Using detection mode: SIOCETHTOOL
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Initialization complete, link beat detected.
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Beep failure, disabled.
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: client: sysctl: error: 'net.ipv4.tcp_timestamps' is an unknown key
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: client: eth0 carrier detected
Jan 12 11:38:59 172.31.1.101 setclock: Try to get time from 172.31.1.1
Jan 12 11:38:59 172.31.1.101 setclock: Fri Jan 12 11:38:59 CET 2018
Jan 12 10:38:59 172.31.1.101 ifplugd(eth0)[160]: Program executed successfully.
Jan 12 10:38:59 172.31.1.101 sshd[231]: Server listening on 0.0.0.0 port 22.
Jan 12 10:38:59 172.31.1.101 sshd[231]: Server listening on :: port 22.
Jan 12 11:38:59 172.31.1.101 cuxd[244]: write_pid /var/run/cuxd.pid [244]
Jan 12 11:38:59 172.31.1.101 cuxd[244]: CUx-Daemon(1.12) on CCU(2.31.23) start PID:244
Jan 12 11:38:59 172.31.1.101 cuxd[244]: load paramsets(/tmp/cuxd.ps.sav) size:1093 update(-235s):Fri Jan 12 11:35:04 2018
Jan 12 11:38:59 172.31.1.101 homematic: started cux-daemon
Jan 12 11:38:59 172.31.1.101 cuxd[244]: 2 device-paramset(s) loaded ok!
Jan 12 11:38:59 172.31.1.101 cuxd[244]: write_proxy /var/cache/cuxd_proxy.ini (244 /usr/local/addons/cuxd/ 1.12 2.31.23 0)
Jan 12 11:38:59 172.31.1.101 cuxd[244]: add interface 'CUxD'
Jan 12 11:38:59 172.31.1.101 cuxd[244]: write 4 interfaces to /usr/local/etc/config/InterfacesList.xml
Jan 12 10:38:59 172.31.1.101 logger: Updating RF Lan Gateway Coprocessor Firmware
Jan 12 10:38:59 172.31.1.101 update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Jan 12 10:38:59 172.31.1.101 logger: Updating RF Lan Gateway Firmware
Jan 12 10:38:59 172.31.1.101 update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Jan 12 10:38:59 172.31.1.101 logger: Updating Wired Lan Gateway Firmware
Jan 12 10:38:59 172.31.1.101 update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Jan 12 11:39:03 172.31.1.101 kernel: [ 1458.910221] eq3loop: created slave ttyS0
Jan 12 11:39:03 172.31.1.101 kernel: [ 1458.913655] eq3loop: created slave mmd_bidcos
Jan 12 11:39:05 172.31.1.101 kernel: [ 1460.965659] eq3loop: eq3loop_open_slave() mmd_bidcos
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.798170] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.798386] eq3loop: eq3loop_close_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.804983] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.805139] eq3loop: eq3loop_close_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.822676] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.826279] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.826298] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Jan 12 11:39:23 172.31.1.101 cuxd[244]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
Jan 12 11:39:24 172.31.1.101 cuxd[244]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
Jan 12 11:39:30 172.31.1.101 logger: rfd_monitor started
Jan 12 10:39:30 172.31.1.101 init: starting pid 494, tty '/dev/tty1': '/sbin/getty -L tty1 115200 linux'
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"000E97098DED57:1","HUMIDITY"} result= [faultCode:-5,faultString:"Unknown Parameter value for value key: HUMIDITY"] [iseXmlRpc.cpp:2605]
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Jan 12 11:39:38 172.31.1.101 rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0612540:1","BRIGHTNESS"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Jan 12 11:39:38 172.31.1.101 ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Jan 12 11:39:39 172.31.1.101 rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Jan 12 11:39:39 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0612521:1","BRIGHTNESS"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2605]
Jan 12 11:39:39 172.31.1.101 ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Jan 12 11:39:39 172.31.1.101 ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Jan 12 11:39:41 172.31.1.101 script: [ALCHY ALLINScript START]
Jan 12 11:39:41 172.31.1.101 script: [ALCHY ALLINScript Abbruch BLOCK]
Jan 12 11:39:48 172.31.1.101 cuxd[244]: INIT 'xmlrpc_bin://127.0.0.1:1999' '1345'
Re: Neue FW V2.31.23
Verfasst: 12.01.2018, 11:54
von leonsio
hi es scheint wohl ein Problem mit der Installation von pivccu-driver zu sein, es läuft nicht
sind auf dem Host das Device vorhanden /dev/raw-uart
poste Auszug von "lsmod"
Re: Neue FW V2.31.23
Verfasst: 12.01.2018, 12:07
von verleihnix
Die CCU scheint zu laufen - über die "Handy-App" kann ich devices schalten.
Code: Alles auswählen
Module Size Used by
xt_tcpudp 2526 2
veth 5878 0
fuse 99603 3
iptable_filter 2197 1
bridge 108705 0
stp 2430 1 bridge
llc 5903 2 bridge,stp
brcmfmac 292632 0
brcmutil 9863 1 brcmfmac
cfg80211 544545 1 brcmfmac
rfkill 20851 2 cfg80211
snd_bcm2835 24427 0
snd_pcm 98501 1 snd_bcm2835
snd_timer 23968 1 snd_pcm
snd 70032 3 snd_timer,snd_bcm2835,snd_pcm
bcm2835_gpiomem 3940 0
pl011_raw_uart 4584 0
generic_raw_uart 10230 3 pl011_raw_uart
fixed 3285 0
uio_pdrv_genirq 3923 0
uio 10204 1 uio_pdrv_genirq
plat_eq3ccu2 1804 0
eq3_char_loop 9744 8
ip_tables 13161 1 iptable_filter
x_tables 20578 3 ip_tables,iptable_filter,xt_tcpudp
ipv6 408900 66 bridge
Re: Neue FW V2.31.23
Verfasst: 12.01.2018, 12:29
von deimos
Hi,
leonsio hat geschrieben:
hi es scheint wohl ein Problem mit der Installation von pivccu-driver zu sein, es läuft nicht
Nö, dann käme das hier nicht:
Code: Alles auswählen
an 12 11:39:03 172.31.1.101 kernel: [ 1458.910221] eq3loop: created slave ttyS0
Jan 12 11:39:03 172.31.1.101 kernel: [ 1458.913655] eq3loop: created slave mmd_bidcos
Jan 12 11:39:05 172.31.1.101 kernel: [ 1460.965659] eq3loop: eq3loop_open_slave() mmd_bidcos
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.798170] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.798386] eq3loop: eq3loop_close_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.804983] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.805139] eq3loop: eq3loop_close_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.822676] eq3loop: eq3loop_open_slave() ttyS0
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.826279] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Jan 12 11:39:17 172.31.1.101 kernel: [ 1472.826298] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Die Ausgaben kommen nur, wenn der multimacd Zugriff auf das raw-uart hat.
Viele Grüße
Alex
Re: Neue FW V2.31.23
Verfasst: 12.01.2018, 13:21
von leonsio
hatte das Problem auch ein mal
lag an HMIPServer es wollte nich hoch kommen, weil danach erst die Logik Schicht hochkommet
wie so oft hat dabei ein reboot geholfen