Skript v.2024-05-22
*** BASE SYSTEM ***
Static hostname: ioBroker
Icon name: computer-container
Chassis: container ☐
Virtualization: lxc
Operating System: Ubuntu 23.04
Kernel: Linux 6.5.13-1-pve
Architecture: x86-64
Firmware Version: 2.H3
model name : AMD Athlon 200GE with Radeon Vega Graphics
Docker : false
Virtualization : lxc
Kernel : x86_64
Userland : 64 bit
Systemuptime and Load:
10:51:20 up 9 days, 10 min, 2 users, load average: 1.62, 0.86, 0.35
CPU threads: 2
*** Time and Time Zones ***
Local time: Sun 2024-06-16 10:51:20 UTC
Universal time: Sun 2024-06-16 10:51:20 UTC
RTC time: n/a
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
*** Users and Groups ***
User that called 'iob diag':
XXXX
HOME=/home/XXXX
GROUPS=XXXX sudo users iobroker
User that is running 'js-controller':
iobroker
[sudo] password for XXXX:
Static hostname: ioBroker
Icon name: computer-container
Chassis: container ☐
Virtualization: lxc
Operating System: Ubuntu 23.04
Kernel: Linux 6.5.13-1-pve
Architecture: x86-64
Firmware Version: 2.H3
model name : AMD Athlon 200GE with Radeon Vega Graphics
Docker : false
Virtualization : lxc
Kernel : x86_64
Userland : 64 bit
Systemuptime and Load:
10:51:20 up 9 days, 10 min, 2 users, load average: 1.62, 0.86, 0.35
CPU threads: 2
*** Time and Time Zones ***
Local time: Sun 2024-06-Sorry, try again.
[sudo] password for ronny:
HOME=/home/iobroker
GROUPS=iobroker tty dialout audio video plugdev
*** Display-Server-Setup ***
Display-Server: false
Desktop:
Terminal: tty
Boot Target: graphical.target
*** MEMORY ***
total used free shared buff/cache available
Mem: 1.1G 509M 192M 81K 372M 564M
Swap: 536M 30M 506M
Total: 1.6G 540M 698M
Active iob-Instances: 4
1024 M total memory
485 M used memory
232 M active memory
541 M inactive memory
183 M free memory
0 M buffer memory
354 M swap cache
512 M total swap
29 M used swap
482 M free swap
*** top - Table Of Processes ***
top - 10:51:40 up 9 days, 10 min, 2 users, load average: 1.52, 0.89, 0.37
Tasks: 34 total, 2 running, 31 sleeping, 0 stopped, 1 zombie
%Cpu(s): 0.0 us,100.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 1024.0 total, 182.0 free, 487.3 used, 354.8 buff/cache
MiB Swap: 512.0 total, 482.7 free, 29.3 used. 536.7 avail Mem
*** FAILED SERVICES ***
UNIT LOAD ACTIVE SUB DESCRIPTION
* run-rpc_pipefs.mount loaded failed failed RPC Pipe File System
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.
*** FILESYSTEM ***
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/pve-vm--210--disk--0 ext4 7.8G 2.1G 5.3G 29% /
none tmpfs 492K 4.0K 488K 1% /dev
tmpfs tmpfs 15G 0 15G 0% /dev/shm
tmpfs tmpfs 5.9G 148K 5.9G 1% /run
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 3.0G 0 3.0G 0% /run/user/1000
Messages concerning ext4 filesystem in dmesg:
dmesg: read kernel buffer failed: Operation not permitted
Show mounted filesystems:
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mapper/pve-vm--210--disk--0 ext4 rw,relatime,stripe=16
|-/run tmpfs tmpfs rw,nosuid,nodev,size=6142320k,nr_inodes=819200,mode=755,uid=100000,gid=100000,inode64
| |-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=3071156k,nr_inodes=767789,mode=700,uid=101000,gid=101000,inode64
| |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k,uid=100000,gid=100000,inode64
| |-/run/credentials/systemd-tmpfiles-setup-dev.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700
| |-/run/credentials/systemd-tmpfiles-setup.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700
| |-/run/credentials/systemd-sysctl.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700
| `-/run/credentials/systemd-sysusers.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700
|-/dev none tmpfs rw,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64
| |-/dev/shm tmpfs tmpfs rw,nosuid,nodev,uid=100000,gid=100000,inode64
| |-/dev/mqueue mqueue mqueue rw,relatime
| |-/dev/ttyUSB0 udev[/ttyUSB0] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/.lxc/proc proc proc rw,relatime
| |-/dev/.lxc/sys sys sysfs rw,relatime
| |-/dev/full udev[/full] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/null udev[/null] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/random udev[/random] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/tty udev[/tty] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/urandom udev[/urandom] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/zero udev[/zero] devtmpfs rw,nosuid,relatime,size=15326340k,nr_inodes=3831585,mode=755,inode64
| |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
| |-/dev/ptmx devpts[/ptmx] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
| |-/dev/console devpts[/0] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
| |-/dev/tty1 devpts[/1] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
| `-/dev/tty2 devpts[/2] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026
|-/proc proc proc rw,nosuid,nodev,noexec,relatime
| |-/proc/sys proc[/sys] proc ro,relatime
| | |-/proc/sys/net proc[/sys/net] proc rw,nosuid,nodev,noexec,relatime
| | |-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime
| | `-/proc/sys/kernel/random/boot_id none[/.lxc-boot-id] tmpfs ro,nosuid,nodev,noexec,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64
| |-/proc/sysrq-trigger proc[/sysrq-trigger] proc ro,relatime
| |-/proc/cpuinfo lxcfs[/proc/cpuinfo] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/diskstats lxcfs[/proc/diskstats] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/loadavg lxcfs[/proc/loadavg] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/meminfo lxcfs[/proc/meminfo] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/slabinfo lxcfs[/proc/slabinfo] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/stat lxcfs[/proc/stat] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| |-/proc/swaps lxcfs[/proc/swaps] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
| `-/proc/uptime lxcfs[/proc/uptime] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
`-/sys sysfs sysfs ro,nosuid,nodev,noexec,relatime
|-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime
|-/sys/devices/virtual/net sysfs[/devices/virtual/net] sysfs rw,nosuid,nodev,noexec,relatime
|-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime
|-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime
|-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime
|-/sys/fs/cgroup none cgroup2 rw,nosuid,nodev,noexec,relatime
`-/sys/devices/system/cpu lxcfs[/sys/devices/system/cpu] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other
Files in neuralgic directories:
/var:
513M /var/
247M /var/cache
241M /var/cache/apt
233M /var/lib
153M /var/cache/apt/archives
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
Archived and active journals take up 8.0M in the file system.
/opt/iobroker/backups:
4.0K /opt/iobroker/backups/
/opt/iobroker/iobroker-data:
60M /opt/iobroker/iobroker-data/
36M /opt/iobroker/iobroker-data/backup-objects
15M /opt/iobroker/iobroker-data/files
13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js
13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static
The five largest files in iobroker-data are:
9.7M /opt/iobroker/iobroker-data/objects.jsonl
6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js
1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map
1.5M /opt/iobroker/iobroker-data/backup-objects/2024-06-16_08-41_objects.jsonl.gz
USB-Devices by-id:
USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
No Devices found 'by-id'
*** NodeJS-Installation ***
/usr/bin/nodejs v18.20.3
/usr/bin/node v18.20.3
/usr/bin/npm 10.7.0
/usr/bin/npx 10.7.0
/usr/bin/corepack 0.28.0
nodejs:
Installed: 18.20.3-1nodesource1
Candidate: 18.20.3-1nodesource1
Version table:
*** 18.20.3-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
100 /var/lib/dpkg/status
18.20.2-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.20.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.20.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.19.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.19.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.18.2-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.18.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.18.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.17.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.17.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.16.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.16.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.15.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.14.2-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.14.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.14.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.13.0+dfsg1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
18.13.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.12.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.11.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.10.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.9.1-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.9.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.8.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.7.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.6.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.5.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.4.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.3.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.2.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.1.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
18.0.0-1nodesource1 600
500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages
Temp directories causing npm8 problem: 0
No problems detected
Errors in npm tree:
*** ioBroker-Installation ***
ioBroker Status
iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Core adapters versions
js-controller: 5.0.19
admin: 6.13.16
javascript: "javascript" not found
nodejs modules from github: 0
Adapter State
+ system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.backitup.0 : backitup : ioBroker - disabled
+ system.adapter.discovery.0 : discovery : ioBroker - enabled
+ system.adapter.jeelink.0 : jeelink : ioBroker - enabled
+ instance is alive
Enabled adapters with bindings
+ system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
ioBroker-Repositories
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.json
Active repo(s): beta
Installed ioBroker-Instances
Used repository: beta
Adapter "admin" : 6.17.14 , installed 6.13.16 [Updatable]
Adapter "backitup" : 3.0.3 , installed 2.11.0 [Updatable]
Adapter "discovery" : 4.5.0 , installed 4.4.0 [Updatable]
Adapter "jeelink" : 1.2.3 , installed 1.2.3
Controller "js-controller": 6.0.4 , installed 5.0.19 [Updatable]
Objects and States
Please stand by - This may take a while
Objects: 162
States: 113
*** OS-Repositories and Updates ***
Hit:1 http://archive.ubuntu.com/ubuntu lunar InRelease
Hit:2 http://archive.ubuntu.com/ubuntu lunar-updates InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:4 http://archive.ubuntu.com/ubuntu lunar-security InRelease
Reading package lists...
Pending Updates: 0
*** Listening Ports ***
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 137730318 1/init
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 137733754 305/master
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 996 137730588 98/systemd-resolved
tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 172229337 5446/iobroker.js-co
tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 172229344 5446/iobroker.js-co
tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 996 137730590 98/systemd-resolved
tcp6 0 0 :::111 :::* LISTEN 0 137730320 1/init
tcp6 0 0 :::22 :::* LISTEN 0 137730597 1/init
tcp6 0 0 :::8081 :::* LISTEN 1001 172229417 5464/io.admin.0
tcp6 0 0 ::1:25 :::* LISTEN 0 137733755 305/master
udp 0 0 127.0.0.54:53 0.0.0.0:* 996 137730589 98/systemd-resolved
udp 0 0 127.0.0.53:53 0.0.0.0:* 996 137730587 98/systemd-resolved
udp 0 0 0.0.0.0:111 0.0.0.0:* 0 137730319 1/init
udp6 0 0 :::111 :::* 0 137730321 1/init
*** Log File - Last 25 Lines ***
2024-06-16 10:41:28.030 - debug: jeelink.0 (5506) data received: [RF12demo.13] A i1 g212 @ 868 MHz q1
2024-06-16 10:41:28.114 - debug: jeelink.0 (5506) data received: Available commands:
2024-06-16 10:41:28.115 - debug: jeelink.0 (5506) data received: <nn>i - set node ID (standard node ids are 1..30)
2024-06-16 10:41:28.115 - debug: jeelink.0 (5506) data received: <n>b - set MHz band (4 = 433, 8 = 868, 9 = 915)
2024-06-16 10:41:28.115 - debug: jeelink.0 (5506) data received: <nnnn>o - change frequency offset within the band (default 1600)
2024-06-16 10:41:28.115 - debug: jeelink.0 (5506) data received: 96..3903 is the range supported by the RFM12B
2024-06-16 10:41:28.116 - debug: jeelink.0 (5506) data received: <nnn>g - set network group (RFM12 only allows 212, 0 = any)
2024-06-16 10:41:28.116 - debug: jeelink.0 (5506) data received: <n>c - set collect mode (advanced, normally 0)
2024-06-16 10:41:28.116 - debug: jeelink.0 (5506) data received: t - broadcast max-size test packet, request ack
2024-06-16 10:41:28.116 - debug: jeelink.0 (5506) data received: ...,<nn>a - send data packet to node <nn>, request ack
2024-06-16 10:41:28.198 - debug: jeelink.0 (5506) data received: if using group 0 then sticky group number is used
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: ...,<nn>s - send data packet to node <nn>, no ack
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: ... <nn> - Space character is a valid delimiter
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: <i>,n - remove group/node index number <i> entry from eeprom
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: <g>n - set group <g> as sticky. Group 0 only, see p command
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: <n>l - turn activity LED on PB1 on or off
2024-06-16 10:41:28.199 - debug: jeelink.0 (5506) data received: ...,m - add message string to ram, see p command
2024-06-16 10:41:28.200 - debug: jeelink.0 (5506) data received: <i>,<g>,<s>p post semaphore <s> for node <i>, group <g> to be
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: sent with its next ack. Group number becomes sticky
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: <n>q - set quiet mode (1 = don't report bad packets)
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: <n>x - set reporting format (0: decimal, 2: decimal+ascii
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: - 1: hex, 3: hex+ascii)
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: 123z - total power down, needs a reset to start up again
2024-06-16 10:41:28.268 - debug: jeelink.0 (5506) data received: Current configuration:
2024-06-16 10:41:28.269 - debug: jeelink.0 (5506) data received: A i1 g212 @ 868 MHz q1
NEWS
Latest posts made by ronny22
-
RE: Jeelink und Technoline, keine Daten im Log
-
Jeelink und Technoline, keine Daten im Log
Hallo Leute
Hardware:
TX29 DHT-IT
TX35 DHT-IT
Raspberry Pi 4
Jeelink v3cAdapter:
Jeelink v1.2.3 (Log auf silly gestellt)Problem:
Keiner der Sensoren scheint in der Log file auf. Woran kann das liegen?
Der Stick wird in Linux angezeigt und startet in ioBroker ohne Warnung.Meine Versuche:
Neuinstallation von IoBroker auf Raspberry Pi 4
Installation von ioBroker in einem Container an meinem Server (Jeelink v3c durchgereicht)
Ältere Adapter von Jeelink versucht
Den Jeelink Adapter von Github installiertBitte um Hilfe
-
RE: RPI 4B unter arm64 auf debian Raspbian buster und deconz
@acme2020 freut mich das ich auch mal was Beitragen konnte
Vermutlich ist jetzt der Conbee2 mit mehr Hardware kompatibel, aber konnte noch nix testen.Der Zigbee Adapter sollte diese Liste hier unterstützen: https://github.com/ioBroker/ioBroker.zigbee/wiki/Supported-devices.
Ob das auch in Kombination mit dem Conbee2 gilt würde mich interessieren. -
RE: Temperatursensor für Außen?
@Ralla66 sagte in Temperatursensor für Außen?:
Dann Druck eben ein Spritzwassergeschützes Gehäuse im 3D Drucker für einen DHT11 aus.
DHT11 is für nix gut. Oder is nur meiner so ungenau? Kann der ins minus? DHT12 hab ich keinen Zuhause, der soll besser sein.
Ich werd den Xiaomi durch einen Aqara tauschen und gut is. Gibt relativ viele positive Erfahrungen damit im Außenbereich.
-
RE: RPI 4B unter arm64 auf debian Raspbian buster und deconz
@maniac_on_moon ich hab die Phoscon Software nicht mehr drauf. Der ioBroker mit Zigbee Adapter unterstützt den Conbee2 Stick.
-
RE: Temperatursensor für Außen?
@Ralla66 sagte in Temperatursensor für Außen?:
warum, solange du kein Fensterrahmen oder Mauerwerk anbohrst ist doch alles ok.
Halter für Fensterrahmen bauen und gut ist.Sowas kommt sicher mal im Haus, aber hier für 155€ und dann bringt mir weder Regensensor oder Windsensor was.
-
RE: Temperatursensor für Außen?
@Ralla66 sagte in Temperatursensor für Außen?:
wenn es mehr sein kann Hier
Das Ding wäre es, aber mitten in der Stadt am Fenster montiert wird schwierig mit dem Vermieter.
-
RE: Temperatursensor für Außen?
@Thomas-Braun sagte in Temperatursensor für Außen?:
@ronny22
Mit dem Raspi4 hast du doch schon bluetooth dabei. Noch den BLE-Adapter dazu und du bist da. Die Frage ist nur ob die beiden Geräte nah genug beeinander stehen.Das ist die Frage, ob es durch empfang hat. Von einem Raum in den anderen mit 80cm Mauer geht bei Bluetooth Kopfhörer nix mehr! Vieleicht bei 5.0. Aber Zigbee funktioniert, alle Räume getestet.
-
RE: Temperatursensor für Außen?
@Thomas-Braun Danke für den Vorschlag.
Hab jetzt etwas durchgestöbert und dürfte tatsächlich nur Bluetooth sein. Wäre dann nur eine Notlösung für mich. -
Temperatursensor für Außen?
Hallo
Status: Blutiger Anfänger
Hardware: Raspberry 4, Conbee2 (ohne Phoscon Software)
Software: ioBroker, Zigbee Adapter.Aktuell habe ich einen Xiaomi Temperatursensor am Fenster außen.
Ich möchte aber etwas was draußen die umstände auf längere Zeit verkraftet.
Was gibt es für meine Hardware und Softwarekombination für kompatible Temperatursensor?
Für innen finde ich ja relativ viel.
Was muss er können: Temp., Luftfeuchtigkeit und Luftdruck.