Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost access to HM devices after the update to 3.55.10.20210213 #1131

Closed
angelnu opened this issue Feb 16, 2021 · 4 comments
Closed

Lost access to HM devices after the update to 3.55.10.20210213 #1131

angelnu opened this issue Feb 16, 2021 · 4 comments
Labels
⚓ upstream issue This is a bug/issue for/in upstream software (OCCU, etc.) 🐛 bug-report Something isn't working

Comments

@angelnu
Copy link
Contributor

angelnu commented Feb 16, 2021

Describe the bug

After switching to the new 3.55.10.20210213 I lost all my Homematic devices. HMIP still work.

Steps to reproduce the behavior

  1. upgrade to 3.55.10.20210213 using OCI means
  2. after reboot Homematic devices are not shown.
  3. Teaching of Homematic devices works, Homematic IP devices work

Expected behavior
...

Screenshots

I see a lot of error logs from ReGaHss:

-0 local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"xxxxx:1","LEVEL"}, result: [faultCode:-2
-0 local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"xxx:1","LEVEL"}) [CallGetValue():iseXmlRpc.cpp:1435]

System information:

  • RaspberryMatic Version: 3.55.10.20210213
  • Used Hardware: CCU on x86
  • Used HomeMatic RF-Module: HM-MOD-RPI-PCB/HB-RF-USB@usb-0000:00:14.0-6

Additional context

I restored an old backup but this did not help either.

@jens-maus
Copy link
Owner

Hmm, that's actually a hard one. Are the HomeMatic devices still visible in the WebUI or are they completely deleted there?

The error in your logs just state that communication with these devices is not possible. What about rfd process? Is it running? Also make sure multimacd and /dev/eq3loop is there.

@angelnu
Copy link
Contributor Author

angelnu commented Feb 16, 2021

I am checking if this is #903 (comment) back. Trying to remember where I added the mount option in Raspberrymatic ;-)

The symptomps are the same. Yes, rfd is running.

--- Update 1
When I moved to the official chart this weekend I missed the circumvention for the rfd to work on GlusterFS. Re-adding...

@angelnu
Copy link
Contributor Author

angelnu commented Feb 16, 2021

It was indeed the inode problem @jens-maus - and after you run into it the CCU config is messed up and a restore from backup is needed.

Any place to documment this so others might find it (maybe my me in the future :-) )?

We can close this - I will do a PR with some changes I did to the Helm chart during this activity.

@jens-maus
Copy link
Owner

Feel free to add some "Known Limitations" section to the wiki documentation if you like and document it there.

@jens-maus jens-maus added ⚓ upstream issue This is a bug/issue for/in upstream software (OCCU, etc.) 🐛 bug-report Something isn't working labels Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚓ upstream issue This is a bug/issue for/in upstream software (OCCU, etc.) 🐛 bug-report Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants