multimacd: ..........ERROR with HASSOS
See original GitHub issueDescribe the issue you are experiencing
First i have to thank you for your outstanding efforts! Great work.
Unfortunatly i cant get the RF modul working.
If i can try anything to help (even buying and testing of different hardware to sort things out i am more then ready to do so.
Describe the behavior you expected
I should be able to teach in devices
Steps to reproduce the issue
- exactly followed your description - unfortunatly it doesnt work
…
What is the version this bug report is based on?
3.65.8.20220831
Which base platform are you running?
odroid-n2 (ODROID N2/N2+)
Which HomeMatic/homematicIP radio module are you using?
HmIP-RFUSB
Anything in the logs that might be useful for us?
Mounting /data as /usr/local (Home Assistant Add-On): OK
Starting watchdog...
Identifying host system: oci, OK
Initializing RTC Clock: onboard, OK
Running sysctl: OK
Checking for Factory Reset: not required
Checking for Backup Restore: not required
Initializing System: OK
Setup ca-certificates: OK
Starting logging: OK
Init onboard LEDs: init, OK
Starting irqbalance: OK
Starting iptables: OK
Starting network: eth0: link up, fixed, firewall, inet up, 172.30.33.1, OK
Identifying Homematic RF-Hardware: ....HmRF: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-xhci-hcd.1.auto-1.1, HmIP: HMIP-RFUSB/eQ-3 HmIP-RFUSB@usb-xhci-hcd.1.auto-1.1, OK
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.4.18, not necessary, OK
Starting hs485dLoader: disabled
Starting xinetd: OK
Starting eq3configd: OK
Starting lighttpd: OK
Starting ser2net: disabled
Starting ssdpd: OK
Starting ha-proxy: OK
Starting NUT services: disabled
Initializing Third-Party Addons: OK
Starting LGWFirmwareUpdate: ...OK
Setting LAN Gateway keys: OK
Starting hs485d: disabled
Starting multimacd: ..........ERROR
Starting rfd: ERROR: /dev/mmd_bidcos missing, no BidCos-RF hardware found
Starting HMIPServer: ERROR: /dev/mmd_hmip missing
Starting ReGaHss: .OK
Starting CloudMatic: OK
Starting NeoServer: disabled
Starting Third-Party Addons: OK
find: /usr/local/etc/monit*.cfg: No such file or directory
Starting crond: OK
Setup onboard LEDs: booted, OK
Finished Boot: 3.65.8.20220831 (raspmatic_oci_arm64)
Additional information
I also tryed with the latest snapshot (0930)
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
"Starting multimacd: ...........ERROR" at HassOS #1752 - GitHub
Describe the issue you are experiencing RaspberryMatic startet nicht mehr sauber und bringt im Protokol folgende drei Fehler Starting ...
Read more >Raspberrymatic rfd error - Third party integrations
It worked just fine till now, and the issue happened directly after restart. ... Starting multimacd: .OK Starting rfd: …ERROR
Read more >(PDF) MultiMAC - An adaptive MAC framework for dynamic ...
In this paper, we describe MultiMAC, a framework and experimental platform for evaluating algorithms that dynamically reconfigure MAC and ...
Read more >HASSOS File System error: Did my Home Assistant install ...
208K subscribers in the homeassistant community. Home Assistant is open source home automation that puts local control and privacy first.
Read more >RaspberryMatic 3.61.7.20220226 – Neue Version - Seite 6
Wenn vor einem Monat (?) beim letzten Update kein Problem bestand, ... hs485d: disabled Starting multimacd: not required Starting rfd: .
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Release had been re-scheduled. Please, if you didn’t test the latest RM snapshot yet, no need to reply or answer here. My question was if there is someone how can reproduce it and not if there is someone who can’t reproduce it. Typical WhatsApp group kinda issue, I guess 😃
Ok, I could finally reproduce it here with my test ODROID N2+:
However, with a RaspberryPi or OVA-based HomeAssistantOS everything seems to work fine. Thus, this seems to be a ODROID-N2 limited issue which needs some dedicated investigation+fixes.