Troubleshooting
- On Linux especially see https://github.com/project-chip/matter.js/blob/main/docs/TROUBLESHOOTING.md
- With Alexa only the Default bridge can be used on a host. Multiple Bridges to use with Alexa are only possible on different hosts.
- When an Ecosystem shows the device as disconnected, especially after an adapter restart, then this usually means that the controller has not yet reconnected to the device. This can take some time. If it does not reconnect after a few minutes, then please check the connection information in the UI. If an ecosystem is not connecting at all, please check logs and potentially debug logs and open an issue.
tbd
- Please check Prerequisites to use this adapter and Troubleshooting first
- Check that you are using the latest version available - or if not, if the changelog for the versions since your version contains information about your issue. Then try updating first, please.
- Check existing open GitHub issues. If yours is also listed, there vote for it by adding a thumbs up on the first comment. This helps to prioritize the issues. "Me Too" posts are not needed.
- Create a GitHub issue if your issue is not existing
- Turn on Debug logs for the matter instance, and additionally "Matter Debug" logs on the main page of the adapter settings. Include the logs (as a Text file please, Logfile location usually
/opt/iobroker/logs/...) as text file attachment in your issue report. Please do not cut only the error but also add some minutes of log before and after the error to get some more context. Please also include information on what exactly is seen there, what was done and such. The more context you can provide, the better.
Um IPv6 für den ioBroker Matter Adapter verwenden zu können, muss im LXC Container in Proxmox die Option "SLAAC" aktiviert werden.
Kurze Erklärung zum Thema SLAAC: https://www.elektronik-kompendium.de/sites/net/1902141.htm
Erfolgreich getestet mit Ubuntu 24.04, Debian 12 + Fritzbox 7530 mit DHCP + Defaulteinstellungen für "IPv6 Einstellungen"
Bestimmt kann man das noch optimieren 😉 Aktive Netwerkschnittstelle: wlp0s20f3
/etc/sysctl.conf
- net.ipv6.conf.all.forwarding=0
- net.ipv6.conf.wlp0s20f3.forwarding=0
- net.ipv6.conf.wlp0s20f3.accept_ra=1
- net.ipv6.conf.wlp0s20f3.accept_ra_rt_info_max_plen=64
/etc/network/interfaces
-
iface wlp0s20f3 inet6 auto
-- accept_ra 2
Kontrolle der Einstellungen: (sudo voranstellen)
sysctl -n net.ipv6.conf.wlp0s20f3.forwarding
0
sysctl -n net.ipv6.conf.wlp0s20f3.accept_ra
2
sysctl -n net.ipv6.conf.wlp0s20f3.accept_ra_rt_info_max_plen
64
Ich sehe schon, das die Einträge nicht konsistent sind, habe aber immer mal wieder eine Einstellung geändert->reboot->Test, so läuft es jetzt aber.
In diesem Abschnitt wird gesammelt an welchen Stellen sich die verschiedenen Ökoysteme unterschiedlich verhalten
- Google: Der Temperaturwert wird in der App auf 0.5° gerundet angezeigt
- Google: Nicht unterstützt
- Amazon: Nicht unterstützt