Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Thorgal789 · Post by **Thorgal789** » Saturday 12 December 2020 9:26

I m not sure to understand but yes, if you add "_dim" on a group name, it will be a Dimmer group only.
You have an other group type problem ?

Plantje · Post by **Plantje** » Saturday 12 December 2020 9:30

Thorgal789 wrote: ↑Saturday 12 December 2020 9:26 I m not sure to understand but yes, if you add "_dim" on a group name, it will be a Dimmer group only.
You have an other group type problem ?

Nope, that's it! You understood correctly!

Thanks!

Harald777 · Post by **Harald777** » Friday 18 December 2020 23:05

Hi all, looking for some advice for my deCONZ bridge plugin in Domoticz.

Recently I updated my Rasperry Pi to buster and re-installed my Domoticz setup with the deCONZ plugin.
Al was working fine, configured all my switches, light bulbs and sensors via Phoscon and all syncs into Domoticz fine.
But since than when working to configure my setup some more I have experienced 3 times that after some configuration actions in domoticz the app hangs up and shows a empty Domoticz screen.
After reboot Domoticz is up and running again but the Phoscon sensors are working fine in the Phoscon app but they don't work in Domoticz anymore.
No error in the Domoticz log and the sensors are shown.

The only thing that fixes the issue is to remove the deCONZ plugin and reset the gateway and start all over again.

Any tips on how to trouble shoot or fix the issue are much appreciated.

Greetings, Harald

Thorgal789 · Post by **Thorgal789** » Saturday 19 December 2020 0:12

Hello, can you try with the plugin disabled but deconz still running (if you have deconz on the same machine)
Then with the plugin enabled but automation that use domotiz disabled (if you have ones, LUA, scripts, ...)

Not possible having last command used ?

Do you use the last plugin version ?

After reboot Domoticz is up and running again but the Phoscon sensors are working fine in the Phoscon app but they don't work in Domoticz anymore.
No error in the Domoticz log and the sensors are shown.

So it work on phoscon but not domoticz ? Can you use the log level "debug info only" and show me the result for a not working command ?
Only sensors or lights too ? If only sensors, have you try some reactives sensors like the motion or vibration ?

The only thing that fixes the issue is to remove the deCONZ plugin and reset the gateway and start all over again.

But phoscon is working fine, you reset deconz too ?

Harald777 · Post by **Harald777** » Saturday 19 December 2020 10:50

Thorgal789 wrote: ↑Saturday 19 December 2020 0:12 Hello, can you try with the plugin disabled but deconz still running (if you have deconz on the same machine)
Then with the plugin enabled but automation that use domotiz disabled (if you have ones, LUA, scripts, ...)

If I disable the plugin in Domoticz all my sensors, switches and lights are normally working in the Phoscon app

Not possible having last command used ?

Do'nt know what you mean with this.

Do you use the last plugin version ?

Yes latest version, fresh install after the Buster update on my rasberry pi3b

After reboot Domoticz is up and running again but the Phoscon sensors are working fine in the Phoscon app but they don't work in Domoticz anymore.
No error in the Domoticz log and the sensors are shown.

Indeed, that is the situation. Happend now 3 times in two days trying to finish my Domoticz config.

So it work on phoscon but not domoticz ? Can you use the log level "debug info only" and show me the result for a not working command ?
Only sensors or lights too ? If only sensors, have you try some reactives sensors like the motion or vibration ?

Only sensors, my ikea lights are working fine because the Phoscon side is still working.
I had the debug only on, does de log show up in between the normal Domotizc log entries? If yes, no errors there.

The only thing that fixes the issue is to remove the deCONZ plugin and reset the gateway and start all over again.
But phoscon is working fine, you reset deconz too ?

Yes, removed plugin via hardware and added it again.

Thanks for the reply.

Yesterday this happened while configuring my iDetect plugin, Domoticz hangup, empty Domoticz page and after reboot Domoticz up and running again. Phoscon working fine but no link between Phoscon sensors and Domoticz.
I tried a lot to recover without a complete reset but nothing was working, for example removed deCONZ and activated again via domoticz hardware and removing sensors and adding them again but nothing worked.

Because it was late I left it aside and want to bed.
To my surprise everything was up and running normal again this morning, WHAT.
No malfunctions to be found anymore.
Hmmmmm, strange.

Don't know whats going on.

Greetings, Harald

p.s.-1 happend again and it is for sure now caused by iDetect.
Removed iDetect plugin completely, rebooted via Putty and agian no connection between Phoscon and Domoticz.
Will wait a while, perhaps it will come back after a while.

Crash Log shows:

Spoiler: show: 2020-12-19 11:45:43.093 Status: (iDetect) Stop directive received.
2020-12-19 11:45:43.093 Status: (iDetect) Exiting work loop.
2020-12-19 11:45:43.124 Error: Domoticz(pid:653, tid:657('PluginMgr')) received fatal signal 6 (Aborted)
2020-12-19 11:45:43.124 Error: siginfo address=0x28d, address=0xffffffff
2020-12-19 11:45:43.258 (Slimme Meter) P1 Smart Meter (Electriciteit)
2020-12-19 11:45:43.265 (Slimme Meter) Usage (Usage L1)
2020-12-19 11:45:43.270 (Slimme Meter) Usage (Delivery L1)
2020-12-19 11:45:48.638 (RFLink 433 Gateway) Temp (Zolderkamer)
2020-12-19 11:45:48.717 Error: Thread 4 (Thread 0x74b9d220 (LWP 657)):
2020-12-19 11:45:48.717 Error: #0 __waitpid (options=0, stat_loc=0x74b9bed8, pid=1037) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2020-12-19 11:45:48.717 Error: #1 __waitpid (pid=1037, stat_loc=0x74b9bed8, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2020-12-19 11:45:48.717 Error: #2 0x002e29ac in dumpstack_gdb(bool) ()
2020-12-19 11:45:48.717 Error: #3 0x002e2f78 in signal_handler(int, siginfo_t*, void*) ()
2020-12-19 11:45:48.717 Error: #4 <signal handler called>
2020-12-19 11:45:48.717 Error: #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
2020-12-19 11:45:48.717 Error: #6 0x76a16230 in __GI_abort () at abort.c:79
2020-12-19 11:45:48.717 Error: #7 0x75d7c270 in ?? () from /lib/arm-linux-gnueabihf/libpython3.7m.so

p.s.-2 crashed again, without iDetec with an enormous crash log:

Spoiler: show: 2020-12-19 13:30:11.965 Error: > [New LWP 16694]
2020-12-19 13:30:11.965 Error: > [New LWP 16696]
2020-12-19 13:30:11.965 Error: > [New LWP 16697]
2020-12-19 13:30:11.965 Error: > [New LWP 16698]
2020-12-19 13:30:11.965 Error: > [New LWP 16699]
2020-12-19 13:30:11.965 Error: > [New LWP 16700]
2020-12-19 13:30:11.965 Error: > [New LWP 16701]
2020-12-19 13:30:11.965 Error: > [New LWP 16702]
2020-12-19 13:30:11.965 Error: > [New LWP 16703]
2020-12-19 13:30:11.965 Error: > [New LWP 16704]
2020-12-19 13:30:11.965 Error: > [New LWP 16705]
2020-12-19 13:30:11.965 Error: > [New LWP 16706]
2020-12-19 13:30:11.965 Error: > [New LWP 16713]
2020-12-19 13:30:11.965 Error: > [New LWP 16720]
2020-12-19 13:30:11.965 Error: > [New LWP 16721]
2020-12-19 13:30:11.965 Error: > [New LWP 16727]
2020-12-19 13:30:11.965 Error: > [New LWP 16728]
2020-12-19 13:30:11.965 Error: > [New LWP 16729]
2020-12-19 13:30:11.965 Error: > [New LWP 16730]
2020-12-19 13:30:11.965 Error: > [New LWP 16731]
2020-12-19 13:30:11.965 Error: > [New LWP 16732]
2020-12-19 13:30:11.965 Error: > [New LWP 16733]
2020-12-19 13:30:11.965 Error: > [New LWP 16734]
2020-12-19 13:30:11.965 Error: > [New LWP 16735]
2020-12-19 13:30:11.965 Error: > [New LWP 16747]
2020-12-19 13:30:11.966 Error: > [New LWP 16748]
2020-12-19 13:30:11.966 Error: > [New LWP 16893]
2020-12-19 13:30:11.966 Error: > [Thread debugging using libthread_db enabled]
2020-12-19 13:30:11.966 Error: > Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
2020-12-19 13:30:11.966 Error: > __GI___nanosleep (remaining=0x7e9739b8, requested_time=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
2020-12-19 13:30:11.966 Error: > 28 ../sysdeps/unix/sysv/linux/nanosleep.c: No such file or directory.
2020-12-19 13:30:11.966 Error: > Id Target Id Frame
2020-12-19 13:30:11.966 Error: > * 1 Thread 0x76045190 (LWP 16693) "domoticz" __GI___nanosleep (remaining=0x7e9739b8, requested_time=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
2020-12-19 13:30:11.966 Error: > 2 Thread 0x75b69220 (LWP 16694) "Watchdog" __waitpid (options=0, stat_loc=0x75b68380, pid=17820) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2020-12-19 13:30:11.966 Error: > 3 Thread 0x75368220 (LWP 16696) "SQLHelper" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 4 Thread 0x74b67220 (LWP 16697) "PluginMgr" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 5 Thread 0x73dba220 (LWP 16698) "InfluxPush" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 6 Thread 0x735b9220 (LWP 16699) "Webem_ssncleane" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x735b8378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 7 Thread 0x72db8220 (LWP 16700) "WebServer_8080" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x72db7348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 8 Thread 0x723ff220 (LWP 16701) "Webem_ssncleane" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x723fe378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 9 Thread 0x71bfe220 (LWP 16702) "WebServer_8443" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 10 Thread 0x711ff220 (LWP 16703) "Scheduler" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 11 Thread 0x709fe220 (LWP 16704) "TCPServer" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x709fd378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 12 Thread 0x701fd220 (LWP 16705) "MainWorker" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 13 Thread 0x6f9fc220 (LWP 16706) "MainWorkerRxMsg" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f9fbba0, expected=0, futex_word=0xb2c8d8 <m_mainworker+4208>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.966 Error: > 14 Thread 0x6edff220 (LWP 16713) "WebServer_8080" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 15 Thread 0x6e3ff220 (LWP 16720) "RFLink" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 16 Thread 0x6dbfe220 (LWP 16721) "BuienRadar" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 17 Thread 0x6d1ff220 (LWP 16727) "HardwareMonitor" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 18 Thread 0x6c9fe220 (LWP 16728) "MainWorker" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x6c9fd360, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.966 Error: > 19 Thread 0x6c1fd220 (LWP 16729) "P1 Meter" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 20 Thread 0x6b9fc220 (LWP 16730) "Domoticz_HBWork" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.966 Error: > 21 Thread 0x6b1fb220 (LWP 16731) "Pinger" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.967 Error: > 22 Thread 0x6a9fa220 (LWP 16732) "NotificationSys" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6a9f9bcc, expected=0, futex_word=0xb2c3a4 <m_mainworker+2876>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.967 Error: > 23 Thread 0x6a1f9220 (LWP 16733) "RFLink" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x6a1f8360, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.967 Error: > 24 Thread 0x699f8220 (LWP 16734) "EventSystem" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.967 Error: > 25 Thread 0x691f7220 (LWP 16735) "EventSystemQueu" futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x691f6af8, expected=0, futex_word=0xb2b9c4 <m_mainworker+348>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.967 Error: > 26 Thread 0x689f6220 (LWP 16747) "Plugin_ASIO" 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x689f5350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.967 Error: > 27 Thread 0x67f2e220 (LWP 16748) "Plugin_deCONZ" syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.967 Error: > 28 Thread 0x6772d220 (LWP 16893) "PluginMgr" futex_wait_cancelable (private=0, expected=0, futex_word=0x68060e78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
2020-12-19 13:30:11.967 Error: >
2020-12-19 13:30:11.967 Error: > Thread 28 (Thread 0x6772d220 (LWP 16893)):
2020-12-19 13:30:11.967 Error: > #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x68060e78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
2020-12-19 13:30:11.967 Error: > #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x0, cond=0x68060e50) at pthread_cond_wait.c:502
2020-12-19 13:30:11.967 Error: > #2 __pthread_cond_wait (cond=0x68060e50, mutex=0x0) at pthread_cond_wait.c:655
2020-12-19 13:30:11.967 Error: > #3 0x0040c0f4 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.967 Error: > #4 0x00418544 in boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_scheduler_runner>::run() ()
2020-12-19 13:30:11.967 Error: > #5 0x00407768 in boost_asio_detail_posix_thread_function ()
2020-12-19 13:30:11.967 Error: > #6 0x76bed494 in start_thread (arg=0x6772d220) at pthread_create.c:486
2020-12-19 13:30:11.967 Error: > #7 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.967 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.967 Error: >
2020-12-19 13:30:11.967 Error: > Thread 27 (Thread 0x67f2e220 (LWP 16748)):
2020-12-19 13:30:11.967 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.967 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.967 Error: > #2 0x00685368 in Plugins::CPlugin::Do_Work() ()
2020-12-19 13:30:11.967 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.967 Error: > #4 0x76bed494 in start_thread (arg=0x67f2e220) at pthread_create.c:486
2020-12-19 13:30:11.967 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.967 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.968 Error: >
2020-12-19 13:30:11.968 Error: > Thread 26 (Thread 0x689f6220 (LWP 16747)):
2020-12-19 13:30:11.968 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x689f5350, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.968 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.968 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.968 Error: > #3 0x0068a5b0 in Plugins::BoostWorkers() ()
2020-12-19 13:30:11.968 Error: > #4 0x0082fc3c in thread_proxy ()
2020-12-19 13:30:11.968 Error: > #5 0x76bed494 in start_thread (arg=0x689f6220) at pthread_create.c:486
2020-12-19 13:30:11.968 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.968 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.968 Error: >
2020-12-19 13:30:11.968 Error: > Thread 25 (Thread 0x691f7220 (LWP 16735)):
2020-12-19 13:30:11.968 Error: > #0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x691f6af8, expected=0, futex_word=0xb2b9c4 <m_mainworker+348>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.968 Error: > #1 __pthread_cond_wait_common (abstime=0x691f6af8, mutex=0x0, cond=0xb2b998 <m_mainworker+304>) at pthread_cond_wait.c:539
2020-12-19 13:30:11.968 Error: > #2 __pthread_cond_timedwait (cond=0xb2b998 <m_mainworker+304>, mutex=0x0, abstime=0x691f6af8) at pthread_cond_wait.c:667
2020-12-19 13:30:11.968 Error: > #3 0x002667c0 in CEventSystem::EventQueueThread() ()
2020-12-19 13:30:11.968 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.968 Error: > #5 0x76bed494 in start_thread (arg=0x691f7220) at pthread_create.c:486
2020-12-19 13:30:11.968 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.968 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.968 Error: >
2020-12-19 13:30:11.968 Error: > Thread 24 (Thread 0x699f8220 (LWP 16734)):
2020-12-19 13:30:11.968 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.968 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.968 Error: > #2 0x0025dba8 in CEventSystem::Do_Work() ()
2020-12-19 13:30:11.968 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.968 Error: > #4 0x76bed494 in start_thread (arg=0x699f8220) at pthread_create.c:486
2020-12-19 13:30:11.968 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.968 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.969 Error: >
2020-12-19 13:30:11.969 Error: > Thread 23 (Thread 0x6a1f9220 (LWP 16733)):
2020-12-19 13:30:11.969 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x6a1f8360, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.969 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.969 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.969 Error: > #3 0x00410828 in boost::asio::io_context::run() ()
2020-12-19 13:30:11.969 Error: > #4 0x0082fc3c in thread_proxy ()
2020-12-19 13:30:11.969 Error: > #5 0x76bed494 in start_thread (arg=0x6a1f9220) at pthread_create.c:486
2020-12-19 13:30:11.969 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.969 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.969 Error: >
2020-12-19 13:30:11.969 Error: > Thread 22 (Thread 0x6a9fa220 (LWP 16732)):
2020-12-19 13:30:11.969 Error: > #0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6a9f9bcc, expected=0, futex_word=0xb2c3a4 <m_mainworker+2876>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.969 Error: > #1 __pthread_cond_wait_common (abstime=0x6a9f9bcc, mutex=0x0, cond=0xb2c378 <m_mainworker+2832>) at pthread_cond_wait.c:539
2020-12-19 13:30:11.969 Error: > #2 __pthread_cond_timedwait (cond=0xb2c378 <m_mainworker+2832>, mutex=0x0, abstime=0x6a9f9bcc) at pthread_cond_wait.c:667
2020-12-19 13:30:11.969 Error: > #3 0x002c91e4 in CNotificationSystem::QueueThread() ()
2020-12-19 13:30:11.969 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.969 Error: > #5 0x76bed494 in start_thread (arg=0x6a9fa220) at pthread_create.c:486
2020-12-19 13:30:11.969 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.969 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.969 Error: >
2020-12-19 13:30:11.969 Error: > Thread 21 (Thread 0x6b1fb220 (LWP 16731)):
2020-12-19 13:30:11.969 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.969 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.969 Error: > #2 0x005cd254 in CPinger::Do_Work() ()
2020-12-19 13:30:11.969 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.970 Error: > #4 0x76bed494 in start_thread (arg=0x6b1fb220) at pthread_create.c:486
2020-12-19 13:30:11.970 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.970 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.970 Error: >
2020-12-19 13:30:11.970 Error: > Thread 20 (Thread 0x6b9fc220 (LWP 16730)):
2020-12-19 13:30:11.970 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.970 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.970 Error: > #2 0x004641a8 in CDomoticzHardwareBase::Do_Heartbeat_Work() ()
2020-12-19 13:30:11.970 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.970 Error: > #4 0x76bed494 in start_thread (arg=0x6b9fc220) at pthread_create.c:486
2020-12-19 13:30:11.970 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.970 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.970 Error: >
2020-12-19 13:30:11.970 Error: > Thread 19 (Thread 0x6c1fd220 (LWP 16729)):
2020-12-19 13:30:11.970 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.970 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.970 Error: > #2 0x005b8808 in P1MeterSerial::Do_Work() ()
2020-12-19 13:30:11.970 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.970 Error: > #4 0x76bed494 in start_thread (arg=0x6c1fd220) at pthread_create.c:486
2020-12-19 13:30:11.970 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.970 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.970 Error: >
2020-12-19 13:30:11.970 Error: > Thread 18 (Thread 0x6c9fe220 (LWP 16728)):
2020-12-19 13:30:11.970 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x6c9fd360, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.970 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.970 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.970 Error: > #3 0x00410828 in boost::asio::io_context::run() ()
2020-12-19 13:30:11.970 Error: > #4 0x0082fc3c in thread_proxy ()
2020-12-19 13:30:11.971 Error: > #5 0x76bed494 in start_thread (arg=0x6c9fe220) at pthread_create.c:486
2020-12-19 13:30:11.971 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.971 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.971 Error: >
2020-12-19 13:30:11.971 Error: > Thread 17 (Thread 0x6d1ff220 (LWP 16727)):
2020-12-19 13:30:11.971 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.971 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.971 Error: > #2 0x004dc3e8 in CHardwareMonitor::Do_Work() ()
2020-12-19 13:30:11.971 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.971 Error: > #4 0x76bed494 in start_thread (arg=0x6d1ff220) at pthread_create.c:486
2020-12-19 13:30:11.971 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.971 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.971 Error: >
2020-12-19 13:30:11.971 Error: > Thread 16 (Thread 0x6dbfe220 (LWP 16721)):
2020-12-19 13:30:11.971 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.971 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.971 Error: > #2 0x00431a9c in CBuienRadar::Do_Work() ()
2020-12-19 13:30:11.971 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.971 Error: > #4 0x76bed494 in start_thread (arg=0x6dbfe220) at pthread_create.c:486
2020-12-19 13:30:11.971 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.971 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.971 Error: >
2020-12-19 13:30:11.971 Error: > Thread 15 (Thread 0x6e3ff220 (LWP 16720)):
2020-12-19 13:30:11.971 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.971 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.971 Error: > #2 0x005e43f8 in CRFLinkSerial::Do_Work() ()
2020-12-19 13:30:11.971 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.971 Error: > #4 0x76bed494 in start_thread (arg=0x6e3ff220) at pthread_create.c:486
2020-12-19 13:30:11.971 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.971 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.972 Error: >
2020-12-19 13:30:11.972 Error: > Thread 14 (Thread 0x6edff220 (LWP 16713)):
2020-12-19 13:30:11.972 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.972 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.972 Error: > #2 0x00730d78 in http::server::CWebsocketHandler::Do_Work() ()
2020-12-19 13:30:11.972 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.972 Error: > #4 0x76bed494 in start_thread (arg=0x6edff220) at pthread_create.c:486
2020-12-19 13:30:11.972 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.972 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.972 Error: >
2020-12-19 13:30:11.972 Error: > Thread 13 (Thread 0x6f9fc220 (LWP 16706)):
2020-12-19 13:30:11.972 Error: > #0 futex_abstimed_wait_cancelable (private=<optimized out>, abstime=0x6f9fbba0, expected=0, futex_word=0xb2c8d8 <m_mainworker+4208>) at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2020-12-19 13:30:11.972 Error: > #1 __pthread_cond_wait_common (abstime=0x6f9fbba0, mutex=0x0, cond=0xb2c8b0 <m_mainworker+4168>) at pthread_cond_wait.c:539
2020-12-19 13:30:11.972 Error: > #2 __pthread_cond_timedwait (cond=0xb2c8b0 <m_mainworker+4168>, mutex=0x0, abstime=0x6f9fbba0) at pthread_cond_wait.c:667
2020-12-19 13:30:11.972 Error: > #3 0x002b5344 in MainWorker::Do_Work_On_Rx_Messages() ()
2020-12-19 13:30:11.972 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.972 Error: > #5 0x76bed494 in start_thread (arg=0x6f9fc220) at pthread_create.c:486
2020-12-19 13:30:11.972 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.972 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.972 Error: >
2020-12-19 13:30:11.972 Error: > Thread 12 (Thread 0x701fd220 (LWP 16705)):
2020-12-19 13:30:11.972 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.972 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.972 Error: > #2 0x002b1170 in MainWorker::Do_Work() ()
2020-12-19 13:30:11.972 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.972 Error: > #4 0x76bed494 in start_thread (arg=0x701fd220) at pthread_create.c:486
2020-12-19 13:30:11.972 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.972 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.972 Error: >
2020-12-19 13:30:11.973 Error: > Thread 11 (Thread 0x709fe220 (LWP 16704)):
2020-12-19 13:30:11.973 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x709fd378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.973 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.973 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.973 Error: > #3 0x006de5cc in tcp::server::CTCPServer::Do_Work() ()
2020-12-19 13:30:11.973 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.973 Error: > #5 0x76bed494 in start_thread (arg=0x709fe220) at pthread_create.c:486
2020-12-19 13:30:11.973 Error: > #6 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.973 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.973 Error: >
2020-12-19 13:30:11.973 Error: > Thread 10 (Thread 0x711ff220 (LWP 16703)):
2020-12-19 13:30:11.973 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.973 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.973 Error: > #2 0x002d9e28 in CScheduler::Do_Work() ()
2020-12-19 13:30:11.973 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.973 Error: > #4 0x76bed494 in start_thread (arg=0x711ff220) at pthread_create.c:486
2020-12-19 13:30:11.973 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.973 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.973 Error: >
2020-12-19 13:30:11.973 Error: > Thread 9 (Thread 0x71bfe220 (LWP 16702)):
2020-12-19 13:30:11.973 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x71bfd348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.973 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.973 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.973 Error: > #3 0x00726538 in http::server::server_base::run() ()
2020-12-19 13:30:11.973 Error: > #4 0x00323d74 in http::server::CWebServer::Do_Work() ()
2020-12-19 13:30:11.973 Error: > #5 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.973 Error: > #6 0x76bed494 in start_thread (arg=0x71bfe220) at pthread_create.c:486
2020-12-19 13:30:11.973 Error: > #7 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.973 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.974 Error: >
2020-12-19 13:30:11.974 Error: > Thread 8 (Thread 0x723ff220 (LWP 16701)):
2020-12-19 13:30:11.974 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x723fe378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.974 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.974 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.974 Error: > #3 0x00410828 in boost::asio::io_context::run() ()
2020-12-19 13:30:11.974 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.974 Error: > #5 0x76bed494 in start_thread (arg=0x723ff220) at pthread_create.c:486
2020-12-19 13:30:11.974 Error: > Backtrace stopped: Cannot access memory at address 0x2c
2020-12-19 13:30:11.974 Error: >
2020-12-19 13:30:11.974 Error: > Thread 7 (Thread 0x72db8220 (LWP 16700)):
2020-12-19 13:30:11.974 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x72db7348, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.974 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.974 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.974 Error: > #3 0x00726538 in http::server::server_base::run() ()
2020-12-19 13:30:11.974 Error: > #4 0x00323d74 in http::server::CWebServer::Do_Work() ()
2020-12-19 13:30:11.974 Error: > #5 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.974 Error: > #6 0x76bed494 in start_thread (arg=0x72db8220) at pthread_create.c:486
2020-12-19 13:30:11.974 Error: > #7 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.974 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.974 Error: >
2020-12-19 13:30:11.974 Error: > Thread 6 (Thread 0x735b9220 (LWP 16699)):
2020-12-19 13:30:11.974 Error: > #0 0x76aa09d0 in epoll_wait (epfd=<optimized out>, events=0x735b8378, maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
2020-12-19 13:30:11.974 Error: > #1 0x0040a0c8 in boost::asio::detail::epoll_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) ()
2020-12-19 13:30:11.974 Error: > #2 0x0040c00c in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2020-12-19 13:30:11.974 Error: > #3 0x00410828 in boost::asio::io_context::run() ()
2020-12-19 13:30:11.974 Error: > #4 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.974 Error: > #5 0x76bed494 in start_thread (arg=0x735b9220) at pthread_create.c:486
2020-12-19 13:30:11.974 Error: > Backtrace stopped: Cannot access memory at address 0x2c
2020-12-19 13:30:11.975 Error: >
2020-12-19 13:30:11.975 Error: > Thread 5 (Thread 0x73dba220 (LWP 16698)):
2020-12-19 13:30:11.975 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.975 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.975 Error: > #2 0x003c910c in CInfluxPush::Do_Work() ()
2020-12-19 13:30:11.975 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.975 Error: > #4 0x76bed494 in start_thread (arg=0x73dba220) at pthread_create.c:486
2020-12-19 13:30:11.975 Error: > Backtrace stopped: Cannot access memory at address 0x78
2020-12-19 13:30:11.975 Error: >
2020-12-19 13:30:11.975 Error: > Thread 4 (Thread 0x74b67220 (LWP 16697)):
2020-12-19 13:30:11.975 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.975 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.975 Error: > #2 0x0068ac80 in Plugins::CPluginSystem::Do_Work() ()
2020-12-19 13:30:11.975 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.975 Error: > #4 0x76bed494 in start_thread (arg=0x74b67220) at pthread_create.c:486
2020-12-19 13:30:11.975 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.975 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.975 Error: >
2020-12-19 13:30:11.975 Error: > Thread 3 (Thread 0x75368220 (LWP 16696)):
2020-12-19 13:30:11.975 Error: > #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37
2020-12-19 13:30:11.975 Error: > #1 0x009943cc in std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned int, bool, std::chrono::duration<long long, std::ratio<1ll, 1ll> >, std::chrono::duration<long long, std::ratio<1ll, 1000000000ll> >) ()
2020-12-19 13:30:11.975 Error: > #2 0x002f90b4 in CSQLHelper::Do_Work() ()
2020-12-19 13:30:11.975 Error: > #3 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.975 Error: > #4 0x76bed494 in start_thread (arg=0x75368220) at pthread_create.c:486
2020-12-19 13:30:11.975 Error: > #5 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.975 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.975 Error: >
2020-12-19 13:30:11.975 Error: > Thread 2 (Thread 0x75b69220 (LWP 16694)):
2020-12-19 13:30:11.976 Error: > #0 __waitpid (options=0, stat_loc=0x75b68380, pid=17820) at ../sysdeps/unix/sysv/linux/waitpid.c:30
2020-12-19 13:30:11.976 Error: > #1 __waitpid (pid=17820, stat_loc=0x75b68380, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:25
2020-12-19 13:30:11.976 Error: > #2 0x002e29ac in dumpstack_gdb(bool) ()
2020-12-19 13:30:11.976 Error: > #3 0x002e2eb0 in signal_handler(int, siginfo_t*, void*) ()
2020-12-19 13:30:11.976 Error: > #4 <signal handler called>
2020-12-19 13:30:11.976 Error: > #5 raise (sig=10) at ../sysdeps/unix/sysv/linux/raise.c:50
2020-12-19 13:30:11.976 Error: > #6 0x002e3174 in Do_Watchdog_Work() ()
2020-12-19 13:30:11.976 Error: > #7 0x009b695c in execute_native_thread_routine ()
2020-12-19 13:30:11.976 Error: > #8 0x76bed494 in start_thread (arg=0x75b69220) at pthread_create.c:486
2020-12-19 13:30:11.976 Error: > #9 0x76aa0578 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6
2020-12-19 13:30:11.976 Error: > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
2020-12-19 13:30:11.976 Error: >
2020-12-19 13:30:11.976 Error: > Thread 1 (Thread 0x76045190 (LWP 16693)):
2020-12-19 13:30:11.976 Error: > #0 __GI___nanosleep (remaining=0x7e9739b8, requested_time=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
2020-12-19 13:30:11.976 Error: > #1 __GI___nanosleep (requested_time=0x7e9739b8, remaining=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
2020-12-19 13:30:11.976 Error: > #2 0x00277c30 in sleep_seconds(long) ()
2020-12-19 13:30:11.976 Error: > #3 0x001f2980 in main ()
2020-12-19 13:30:11.976 Error: >
2020-12-19 13:30:11.976 Error: > Main thread:
2020-12-19 13:30:11.976 Error: > #0 __GI___nanosleep (remaining=0x7e9739b8, requested_time=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:28
2020-12-19 13:30:11.976 Error: > #1 __GI___nanosleep (requested_time=0x7e9739b8, remaining=0x7e9739b8) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
2020-12-19 13:30:11.976 Error: > #2 0x00277c30 in sleep_seconds(long) ()
2020-12-19 13:30:11.976 Error: > #3 0x001f2980 in main ()
2020-12-19 13:30:11.976 Error: > [Inferior 1 (process 16693) detached]
2020-12-19 13:30:12.870 Status: Closing application!...
2020-12-19 13:30:12.870 Status: Stopping worker...
2020-12-19 13:30:12.999 Status: RxQueue: queue worker stopped...
2020-12-19 13:30:13.500 Status: WebServer(HTTP) stopped
2020-12-19 13:30:14.002 Status: WebServer(SSL) stopped
2020-12-19 13:30:14.009 Status: TCPServer: shared server stopped
2020-12-19 13:30:14.009 Status: Stopping all hardware...
2020-12-19 13:30:14.012 Status: RFLink: Worker stopped...
2020-12-19 13:30:14.013 Status: BuienRadar: Worker stopped...
2020-12-19 13:30:14.017 Status: HardwareMonitor: Hardware Monitor: Stopped...
2020-12-19 13:30:14.020 Status: P1 Smart Meter: Worker stopped...
2020-12-19 13:30:14.021 Status: Pinger: Worker stopped...
2020-12-19 13:30:14.032 Status: (deCONZ) Stop directive received.
2020-12-19 13:30:14.032 Status: (deCONZ) Exiting work loop.
2020-12-19 13:30:14.130 Status: (deCONZ) onDisconnect called for deCONZ_WebSocket
2020-12-19 13:30:14.130 Error: CConnection_disconnect, disconnection request from 'deCONZ' ignored. Transport does not exist.
2020-12-19 13:30:14.234 Status: (deCONZ) Stopping threads.
2020-12-19 13:30:14.265 Status: (deCONZ) Stopped.
2020-12-19 13:30:14.265 Status: Scheduler stopped...
2020-12-19 13:30:14.266 Status: EventSystem: Queue thread stopped...
2020-12-19 13:30:14.266 Status: EventSystem: Stopped...
2020-12-19 13:30:14.282 Status: EventSystem - Python stopped...
2020-12-19 13:30:14.282 Status: NotificationSystem: thread stopped...
2020-12-19 13:30:14.283 Status: PluginSystem: Exiting work loop.
2020-12-19 13:30:14.301 Status: PluginSystem: Stopped.
2020-12-19 13:30:14.484 Status: Mainworker Stopped...

Thorgal789 · Post by **Thorgal789** » Saturday 19 December 2020 20:05

IDK, on the second log, we can see deconz is stopping, so this thread was not in error, but I don't find something usefull on the log.

Code: Select all

2020-12-19 11:45:43.124 Error: Domoticz(pid:653, tid:657('PluginMgr')) received fatal signal 6 (Aborted)

I m not sure But this one mean a problem was from a python plugin, but not sure neither.

After reboot Domoticz is up and running again but the Phoscon sensors are working fine in the Phoscon app but they don't work in Domoticz anymore.
No error in the Domoticz log and the sensors are shown.

This is the part I don't understand, domoticz use the same api than phoscon, can you show the log when making a sensor react (like the motion one, or vibration) with log level "debug info only"
Removing the plugin change nothing, it don't store data, and the files can't be modified by domoticz, perhaps a domoticz database corruption ? I realy don't see why you need to remove it to make the plugin working again.

You can too disable your sensor in device panel, to find if one of them is guilty

Plantje · Post by **Plantje** » Tuesday 22 December 2020 8:32

Is Domoticz and phoscon running on the same machine?

Harald777 · Post by **Harald777** » Tuesday 22 December 2020 22:00

Thorgal789 wrote: ↑Saturday 19 December 2020 20:05
This is the part I don't understand, domoticz use the same api than phoscon, can you show the log when making a sensor react (like the motion one, or vibration) with log level "debug info only"
Removing the plugin change nothing, it don't store data, and the files can't be modified by domoticz, perhaps a domoticz database corruption ? I realy don't see why you need to remove it to make the plugin working again.

You can too disable your sensor in device panel, to find if one of them is guilty

Thanks again for your feedback.
Don't know what was going wrong with the install but finally could not work at al in the Domoticz config.
Started all over again, left the iDetect plugin out off my new config and all working fine again.

The only error that is showing up now is this one:

Code: Select all

Error: (deCONZ) Can't Update Unit > 65520 (groups) : {'nValue': 0, 'sValue': 'off'}

That's the same as in my original config on Raspbian Stretch. Never could solve that but all was and is working fine.

Greetings, Harald

Thorgal789 · Post by **Thorgal789** » Wednesday 23 December 2020 17:20

This error message is "normal", it s provoked by the hidden group, it happen one time at startup, then the plugin add it in base, and this message normaly don't re-appear.

QuadRotas · Post by **QuadRotas** » Sunday 24 January 2021 18:13

After ruining my Pi 4 with working domoticz & deConz I am installing the plugin on an older 3B pi with Domoticz.
When trying to create an api key I get this error:

Code: Select all

pi@raspberry:~/domoticz/plugins/Domoticz-deCONZ $ python3 API_KEY.py 127.0.0.1:80 create
Traceback (most recent call last):
  File "API_KEY.py", line 27, in <module>
    j = eval(response)
  File "<string>", line 2
    <!doctype html>
    ^
IndentationError: unexpected indent

I can't for the life of me figure out why this is happening...

Thorgal789 · Post by **Thorgal789** » Sunday 24 January 2021 18:53

Good question !

I think the url or the port is not good. If you use this url in a web browser, you have other thing than phoscon ?

Code: Select all

http://127.0.0.1:80

To find the good url and port

Code: Select all

https://phoscon.de/discover

And BTW "ruining your pi" ?

Jemand · Post by **Jemand** » Sunday 24 January 2021 20:51

I am using this plugin and it works great. But I have some questions about improvements:
1.) Aqara window-sensors and water detectors also have the temperature but I can't access this property through this plugin
2.) The Aqara-Cube only supports "Shak Wake Drop 90° 180° Push Tap". It would be great to have the value which side is up.
3.) The Aqara vibration-sensor supports a tilt level. It would be great to have this tilt level in domoticz as well

Is there any hope in getting these datapoints through the plugin?

Thanks!

QuadRotas · Post by **QuadRotas** » Sunday 24 January 2021 21:31

Thorgal789 wrote: ↑Sunday 24 January 2021 18:53 Good question !

I think the url or the port is not good. If you use this url in a web browser, you have other thing than phoscon ?
Code: Select all
http://127.0.0.1:80
To find the good url and port
Code: Select all
https://phoscon.de/discover

Oh...good point. There's also a pi-hole installation on this Pi. That might explain the <!doctype html> stuff.
I am happy to have Phoscon run on a different port but I haven't been able to figure out how to change it.

And BTW "ruining your pi" ?

It didn't survive my move to a new apartment. The wifi chip is busted and the SD card is corrupted.

Plantje · Post by **Plantje** » Sunday 24 January 2021 21:53

If you got this far, you have installed the deCONZ app as well. If you open that on your server and click the "Phoscon app" button in the upper right a website will open. What address do you have there?

QuadRotas · Post by **QuadRotas** » Monday 25 January 2021 7:13

Plantje wrote: ↑Sunday 24 January 2021 21:53 If you got this far, you have installed the deCONZ app as well. If you open that on your server and click the "Phoscon app" button in the upper right a website will open. What address do you have there?

The Phoscon app is running but does not see a gateway. Probably because it gets a response from the Pi-Hole webpage that runs at http://<ip address>:80
If anyone can tell me how I can change the port number of the Phoscon app/gateway I could separate Pi-hole from Phoscon, I think.

Thorgal789 · Post by **Thorgal789** » Monday 25 January 2021 9:53

Plantje is right, when a port is used, deconz will use another one, and the API use the same ip and port than phoscon.
You can find them too at https://phoscon.de/discover

You can change the port and block them using https://github.com/dresden-elektronik/p ... /issues/26

The Phoscon app is running but does not see a gateway

Not normal, as the gateway is on the same machine than the webserver, so you can't have network problem here. You have a capture ?

QuadRotas · Post by **QuadRotas** » Monday 25 January 2021 11:19

Thanks for all the input, folks.
I did a complete reinstall of both the Phoscon-app and the Domoticz plugin just now. The app discovered an instance on port 8090. Now I get a different response from python3 API_KEY.py <ip address>:8090 create: "Please unlock the gateway first and retry".
Small progress

!

Thorgal789 · Post by **Thorgal789** » Monday 25 January 2021 16:29

Jemand wrote: ↑Sunday 24 January 2021 20:51 I am using this plugin and it works great. But I have some questions about improvements:
1.) Aqara window-sensors and water detectors also have the temperature but I can't access this property through this plugin
2.) The Aqara-Cube only supports "Shak Wake Drop 90° 180° Push Tap". It would be great to have the value which side is up.
3.) The Aqara vibration-sensor supports a tilt level. It would be great to have this tilt level in domoticz as well

Is there any hope in getting these datapoints through the plugin?

Thanks!

Hello.
1- Normal, it s disabled, because not reliable at all
2 -The aquara cube create 2 widget, one for angle rotation and the one you are speaking. And it s possible to have the raw value (for the side) viewtopic.php?f=59&t=33581&p=253899&hil ... nz#p253899
3 - Give me some hours to add it, using the same way than for the cube.

Thorgal789 · Post by **Thorgal789** » Monday 25 January 2021 16:53

@Jemand for the 3, you miss the titlangle or the vibrationstrength ?
Because you already have a widget for the angle in x,y,z style.

Jemand · Post by **Jemand** » Tuesday 26 January 2021 20:04

Thorgal789 wrote: ↑Monday 25 January 2021 16:53 @Jemand for the 3, you miss the titlangle or the vibrationstrength ?
Because you already have a widget for the angle in x,y,z style.

What I miss is the "tiltangle". As far as I know it is in degrees where xyz is more raw and needs to be converted to use. For that reason a simple tilt-angle would be great. Vibrationstrength is not needed for me.

Thanks also for the other answers to my questions! This brought me into dzVents and now I can handle the cube-side-actions.

Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee) Topic is solved

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Re: Python Zigbee plugin, deCONZ bridge (Using Conbee or Raspbee)

Who is online