Frankh

Sjekket ut http://web.craftbeerpi.com ? Tenkte på denne før jeg bestemte jeg for RIMS med PID's ? MK3 virket jo som en grei og rimelig løsning for logg. Lang rekkevidde? Binary sensor hadde jeg heller ikke tenkt på. Dyrere enn MK3 men kommer jo rett inn i HS. Er det innafor med +-3 grader ??

Har lest meg litt opp siden jeg publiserte innlegget. Og har bestilt meg en STC1000 og DS18B20 sensor da de fleste benytter dette oppsettet. Sensoren bør man senke ned i vannbad for å gi fremkalle forsinkelse av temperatursvingninger mtp. hviletid for kompressoren. Men dette kjøres helt uten tilknytning til HS. Qubino Rele har mulighet for ekstern sensor vil gjøre det veeldig lettvint, tenker da log/justering av gjæringstemperatur enten via event/timer eller manuelt gjennom HomeSeer. Hue Sensor er nok en dårlig ide ja.

God kveld. Jeg tenker å få gjæringsforløpet av øl og vin inn i Homeseer. Og i den forbindelse så jeg før meg å benytte en Fibaro relay switch hvor ene kanalen bryter 1 fase til en frostvakt og den andre kanalen bryter 1 fase til kompressoren i kjøleskapet. Hue motion (temp) inne i skapet. Dette tenkte jeg å sette opp via SDJ-Stat thermostat og events. Med alarm på epost ved avvik. Normal avvik på temp. ca. +-1 grad. Tåler kompressoren dette?

Forutsatt at du har en virkende MyQ plugin i HomeSeer så må du tilknytte HomeSeer i Home appen. Har du allerede lagt til HomeSeer i Home appen og ikke finner Garasjeportåpneren i Home kan du kjøre en Hey Google "Sync Devices" Har du ikke lagt til HomeSeer i Home Start Home appen 1. Legg til 2. Konfigurer enheten 3. Konfigurer nye enheter i hjemmet. (eller Allerede konfigurerte enheter?). Jeg bruker kommandoen "Hey Google Garasjeport ON" eller "Hey Google Garasjeport OFF" Om ikke dette var 100% så burde det hjelpe deg på vei (En stund side jeg gjorde det)

My bad, sving horisontalt er nok bare på selve pumpa og ikke Sensibo. Ser for meg at jeg må ha en harmonyhub for å kunne styre denne svingen via HomeSeer. Pumpa er en Mitsubishi FD-Heat Kirigamine (MSZ-35FD).

Korrekt. Men 828EV Ethernet MÅ være tilkoblet internett med kabel. Distansen mellom porten (i ditt tilfelle LM100) og 828EV Ethernet er jeg usikker på. Har du kablet internett i garasjen eller i rimelighetens nærhet er jo det ett plus

Komunikasjonen skjer over Internett og trenger ingen adapter. Du registrerer først konto hos MyQ. (Appstore eller Google Play). Deretter legger du inn brukernavnet og passordet du registrerte deg med i MyQ pluginet. Legg inn pluginet og prøv det. (30 dagers prøveperiode).

Mener du må bruke kommandoen on/off, på/av ikke opp eller ned.

Tut og kjør ??

Hadde utdatert Debian Helt umulig å få sving (horisontalt) inn i plugin? Har satt min pumpe i 45grader for mulighet til å svinge mellom 2 ganger. Men 90% av tiden ønsker jeg den kun til ene gangen men det virker til at hver gang den avrimer så stiller den seg midt på.

Jeg har samme oppsett som deg og bruker MyQ (828EV Ethernet). Funker snus. Fantastisk med event som f.eks. port åpner -> Lys på Hadde jeg skulle valgt om igjen hadde jeg valgt (MyQ G0301 WIFI) da du slipper ledning til fotoceller. Være obs på at åpneren din må ha støtte for MyQ

Utrolig bra Frankis78 Men jeg får følgende feilmelding etter oppstart av HS3. Er det noe jeg har uteglemt? ? Linux (pi3) HS3 Standard Edition 3.0.0.435 Mono JIT compiler version 4.6.2

Takk for svar ? Var usikker på om jeg skulle tørre å skrive hva som var feilen, men men... Det var impulsfjæra som var satt på feil side Takk for svar og god helg ?

Neida, lasten er ikke på mer enn 32W (4 stk. Altea 8W spots) Har satt tilbake til gruppe 1 uten noen forbedring. Tok også en exclude/include uten at det gjorde det noe bedre

Det er den ja?? Har nå fjernet gruppe 1 og lagt til gruppe 4 til -> Homeseer uten at det hjalp. Dimmeren har forbindelse med Homeseer. Hvis jeg slår lyset på fra HS, så går det opp til max for så å slå seg av. Men bryteren i HS viser at lyset enda er påslått. Ikke noe i loggen som skulle tilsi at noe er galt.

Ja med bryter virker lyset normalt. Dette er den eneste Qubino jeg har, men alle Fibaro dimmere jeg har virker som de skal.

Hei! Jeg har fått koblet dimmeren til med fjærbelastet bryter til I1. Og dette virker upåklagelig. Men når det kommer til HS så er det problemer. Ved bevegelse (event) kommer lyset på før det etter ca. 1 sekund slukker av seg selv.. Det vises da som ON i HS. Ved ON/OFF i HS oppfører lyset seg merkelig. Kan komme på for så å slukke av seg selv. Dimming av lyset virker heller ikke i HS. Er det noe med assosiasjonene jeg ikke har rett?

Ahh...Du satte meg på sporet ?☺️Det var Sensibo.hspi eller hva den hete som laget krøll. Tusen hjertelig for innspill. Frank

Takk for svar, men det testa jeg tidlig med samme utfall. 03.28.39.6459:[Plug-In]->Found plug-in: mcsMQTT, version: 3.4.5.2 03.28.41.8425:[Plug-In]->Found plug-in: MQTT, version: 1.5.0.0 03.28.44.0772:[Plug-In]->Found plug-in: RFXCOM, version: 30.0.0.36 * Assertion at metadata.c:980, condition `index < meta->heap_blob.size' not met

Hei! Tenkte jeg skulle teste ut Smater Control sin Sensibo plugin. Gjorde som beskrevet Extract the HSPI_SCREPOSTIROY.EXE file from the zip file and place it in your HS3 directory Restart HS3 Use the HS3 plugin manager to start the repository plugin. Navigate to Plugins / SCREPOSITORY / Manage Smarter Control Plugins Men da jeg skulle installere Sensibo plugin restartet HS og etter det vil den ikke starte. Er det noen måte jeg klarer å få HS opp igjen? Sensibo pluginet ble plutselig ikke så viktig lenger :P Benytter Raspberry pi3 og HS 3.0.0.435 og Screpository (Smarter Control) 5.0.2.0 Får denne feilmeldingen ved ./go pi@raspberrypi:~/HomeSeer $ ./go HomeSeer Linux starting... 01.36.33.7474:[Database]->Opening (Mode=Read Only) up HomeSeer LOG database /home/pi/HomeSeer/Logs/HomeSeerLog.hsd 01.36.34.1212:[Startup]->Loading Settings 01.36.34.2331:[Warning]->HomeSeer was not shut down successfully the previous time it was started. 01.36.34.3752:[Startup]->Settings Loaded. 01.36.39.3716:[Startup]-> 01.36.39.3733:[Startup]->******************************************************************************** 01.36.39.3775:[Startup]-> HomeSeer version 3.0.0.435 Edition: HS3 Standard Starting Now 01.36.39.3798:[Startup]->******************************************************************************** 01.36.39.3816:[Startup]-> 01.36.39.4460:[Startup]->Creating Class Objects... 01.36.39.4532:[Startup]->COM port classes started. 01.36.39.4670:[Startup]->Application interface class started. 01.36.39.4896:[Startup]->Web server class started. 01.36.39.4964:[Startup]->E-Mail SEND class started. 01.36.39.5011:[Startup]->E-Mail RECEIVE class started. 01.36.39.5160:[Startup]->Plug-In Interface class started. 01.36.39.5246:[Startup]->Local voice recognition class started. 01.36.39.5371:[Startup]->Database SAVE process started. 01.36.39.5388:[Startup]->Loading configuration file ... 01.36.39.6013:[Database]->Opening (Mode=Read Only) up HomeSeer database /home/pi/HomeSeer/Data/HomeSeerData.hsd 01.36.42.3120:[Database]->Loading Devices... 01.36.42.3628:[Load Config]->158 total devices loaded. 01.36.42.3738:[Load Config]->Loading Event Groups... 01.36.42.4416:[Load Config]->Loading Events... 01.36.42.7255:[Load Config]->20 total events loaded. 01.36.42.7271:[Load Config]->Loading COUNTERS... 01.36.42.7499:[Load Config]->Loading TIMERS... 01.36.42.8251:[Startup]->HomeSeer version is: 3.0.0.435 01.36.42.8284:[Startup]->Creating Speaker Client Interface Object... 01.36.42.8411:[Startup]->This version of HomeSeer is registered as a HS3STANDARD version. 01.36.43.0266:[Info]->Remote plug-in API interface started on port XXXX 01.36.43.0286:[Startup]->Checking for available plug-ins 01.36.45.6386:[Plug-In]->Found plug-in: JowiHue, version: 2.0.2.6 01.36.47.8000:[Plug-In]->Found plug-in: mcsMQTT, version: 3.4.5.2 01.36.49.9673:[Plug-In]->Found plug-in: MQTT, version: 1.5.0.0 01.36.52.1854:[Plug-In]->Found plug-in: RFXCOM, version: 30.0.0.36 01.36.55.8795:[Plug-In]->Found plug-in: SCREPOSITORY, version: 5.0.2.0 * Assertion at metadata.c:980, condition `index < meta->heap_blob.size' not met Stacktrace: at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke (System.Reflection.MonoCMethod,object,object[],System.Exception&) <0x00043> at System.Reflection.MonoCMethod.InternalInvoke (object,object[]) <0x0003b> at System.RuntimeType.CreateInstanceMono (bool) <0x0012b> at System.RuntimeType.CreateInstanceSlow (bool,bool,bool,System.Threading.StackCrawlMark&) <0x00063> at System.RuntimeType.CreateInstanceDefaultCtor (bool,bool,bool,System.Threading.StackCrawlMark&) <0x00067> at System.Activator.CreateInstance (System.Type,bool) <0x000b3> at System.RuntimeType.CreateInstanceImpl (System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo,object[],System.Threading.StackCrawlMark&) <0x005c3> at System.Activator.CreateInstance (System.Type,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo,object[]) <0x001fb> at System.Activator.CreateInstance (System.Type,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x00047> at System.SecurityUtils.SecureCreateInstance (System.Type,object[],bool) <0x00097> at System.SecurityUtils.SecureCreateInstance (System.Type) <0x0001b> at System.ComponentModel.LicenseManager.ValidateInternalRecursive (System.ComponentModel.LicenseContext,System.Type,object,bool,System.ComponentModel.License&,string&) <0x000c7> at System.ComponentModel.LicenseManager.ValidateInternal (System.Type,object,bool,System.ComponentModel.License&) <0x0004f> at System.ComponentModel.LicenseManager.Validate (System.Type) <0x00027> at HSPI_SENSIBO.Main..cctor () <0x0009b> at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0x0006f> at <unknown> <0xffffffff> at (wrapper managed-to-native) object.__icall_wrapper_mono_generic_class_init (intptr) <0x00037> at HSPI_SENSIBO.HSPI.get_Name () <0x00027> at (wrapper runtime-invoke) <Module>.runtime_invoke_object__this__ (object,intptr,intptr,intptr) <0x000cb> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) <0x00043> at System.Reflection.MonoMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo) <0x000ab> at System.RuntimeType.InvokeMember (string,System.Reflection.BindingFlags,System.Reflection.Binder,object,object[],System.Reflection.ParameterModifier[],System.Globalization.CultureInfo,string[]) <0x010a7> at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet (object,System.Type,string,object[],string[],bool[]) <0x000cb> at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet (object,System.Type,string,object[],string[],System.Type[],bool[]) <0x00057> at Scheduler.clsHSPI/Worker.ProcessAssembly () <0x00137> at (wrapper remoting-invoke-with-check) Scheduler.clsHSPI/Worker.ProcessAssembly () <0x00063> at (wrapper xdomain-dispatch) Scheduler.clsHSPI/Worker.ProcessAssembly (object,byte[]&,byte[]&) <0x00103> at (wrapper xdomain-invoke) Scheduler.clsHSPI/Worker.ProcessAssembly () <0x000e3> at (wrapper remoting-invoke-with-check) Scheduler.clsHSPI/Worker.ProcessAssembly () <0x0004b> at Scheduler.clsHSPI/PluginAttributes.Process () <0x0041b> at Scheduler.clsHSPI.FindInterfaces (bool&) <0x004cf> at (wrapper remoting-invoke-with-check) Scheduler.clsHSPI.FindInterfaces (bool&) <0x00073> at Scheduler.SC_Main.c730f8742e287d8f2971f387fee693ad4 () <0x0008b> at Scheduler.SC_Main.StartUp () <0x00903> at HSConsole.HSConsole.Main () <0x00413> at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0x000bf> Native stacktrace: Debug info from gdb: [New LWP 1197] [New LWP 1198] [New LWP 1201] [New LWP 1202] [New LWP 1203] [New LWP 1205] [New LWP 1206] [New LWP 1207] [New LWP 1208] [New LWP 1209] [New LWP 1210] [New LWP 1211] [New LWP 1212] [New LWP 1213] [New LWP 1214] [New LWP 1215] [New LWP 1226] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". 0x76e194cc in __waitpid (pid=1227, stat_loc=0x7e8bfa00, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 29 ../sysdeps/unix/sysv/linux/waitpid.c: Ingen slik fil eller filkatalog. Id Target Id Frame * 1 Thread 0x76f30570 (LWP 1196) "(System)_17-okt" 0x76e194cc in __waitpid (pid=1227, stat_loc=0x7e8bfa00, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 2 Thread 0x763ff470 (LWP 1197) "SGen worker" 0x76e1494c in __pthread_cond_wait (cond=0x3258f0, mutex=0x3258bc) at pthread_cond_wait.c:186 3 Thread 0x76a53470 (LWP 1198) "Finalizer" 0x76e17014 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x31d8c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 4 Thread 0x7374b470 (LWP 1201) "Logging Class C" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x7374a704) at pthread_cond_timedwait.c:198 5 Thread 0x734ff470 (LWP 1202) "Timer-Scheduler" 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe6fa40, mutex=0xe6fa24, abstime=0x734fe35c) at pthread_cond_timedwait.c:198 6 Thread 0x733ff470 (LWP 1203) "(System)_17-okt" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x733fed54) at pthread_cond_timedwait.c:198 7 Thread 0x72fff470 (LWP 1205) "Threadpool work" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72ffed60) at pthread_cond_timedwait.c:198 8 Thread 0x7335d470 (LWP 1206) "Threadpool work" 0x76d90cb0 in poll () at ../sysdeps/unix/syscall-template.S:84 9 Thread 0x72cff470 (LWP 1207) "Threadpool work" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72cfed60) at pthread_cond_timedwait.c:198 10 Thread 0x72aff470 (LWP 1208) "Threadpool work" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72afed60) at pthread_cond_timedwait.c:198 11 Thread 0x72230470 (LWP 1209) "(System)_17-okt" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x7222f6d4) at pthread_cond_timedwait.c:198 12 Thread 0x72130470 (LWP 1210) "(System)_17-okt" 0x76e1494c in __pthread_cond_wait (cond=0xe70898, mutex=0xe7087c) at pthread_cond_wait.c:186 13 Thread 0x72030470 (LWP 1211) "(System)_17-okt" 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe70cd8, mutex=0xe70cbc, abstime=0x7202f464) at pthread_cond_timedwait.c:198 14 Thread 0x71f30470 (LWP 1212) "(System)_17-okt" 0x76e1494c in __pthread_cond_wait (cond=0xe70e70, mutex=0xe70e54) at pthread_cond_wait.c:186 15 Thread 0x71e30470 (LWP 1213) "(System)_17-okt" 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x71e2f56c) at pthread_cond_timedwait.c:198 16 Thread 0x71aff470 (LWP 1214) "(System)_17-okt" 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe70b40, mutex=0xe70b24, abstime=0x71afe44c) at pthread_cond_timedwait.c:198 17 Thread 0x718ef470 (LWP 1215) "(System)_17-okt" 0x76e186a0 in accept () at ../sysdeps/unix/syscall-template.S:84 18 Thread 0x71537470 (LWP 1226) "Timer-Scheduler" 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe72dc8, mutex=0xe72dac, abstime=0x715362e4) at pthread_cond_timedwait.c:198 Thread 18 (Thread 0x71537470 (LWP 1226)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe72dc8, mutex=0xe72dac, abstime=0x715362e4) at pthread_cond_timedwait.c:198 #1 0x0021caf8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 17 (Thread 0x718ef470 (LWP 1215)): #0 0x76e186a0 in accept () at ../sysdeps/unix/syscall-template.S:84 #1 0x0022e1c0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 16 (Thread 0x71aff470 (LWP 1214)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe70b40, mutex=0xe70b24, abstime=0x71afe44c) at pthread_cond_timedwait.c:198 #1 0x0021caf8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 15 (Thread 0x71e30470 (LWP 1213)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x71e2f56c) at pthread_cond_timedwait.c:198 #1 0x002488f4 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 14 (Thread 0x71f30470 (LWP 1212)): #0 0x76e1494c in __pthread_cond_wait (cond=0xe70e70, mutex=0xe70e54) at pthread_cond_wait.c:186 #1 0x0021cdfc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 13 (Thread 0x72030470 (LWP 1211)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe70cd8, mutex=0xe70cbc, abstime=0x7202f464) at pthread_cond_timedwait.c:198 #1 0x0021caf8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 12 (Thread 0x72130470 (LWP 1210)): #0 0x76e1494c in __pthread_cond_wait (cond=0xe70898, mutex=0xe7087c) at pthread_cond_wait.c:186 #1 0x0021cdfc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 11 (Thread 0x72230470 (LWP 1209)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x7222f6d4) at pthread_cond_timedwait.c:198 #1 0x002488f4 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 10 (Thread 0x72aff470 (LWP 1208)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72afed60) at pthread_cond_timedwait.c:198 #1 0x001918c0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 9 (Thread 0x72cff470 (LWP 1207)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72cfed60) at pthread_cond_timedwait.c:198 #1 0x001918c0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 8 (Thread 0x7335d470 (LWP 1206)): #0 0x76d90cb0 in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00193504 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 7 (Thread 0x72fff470 (LWP 1205)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x1472a28, mutex=0x1472a58, abstime=0x72ffed60) at pthread_cond_timedwait.c:198 #1 0x001918c0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 6 (Thread 0x733ff470 (LWP 1203)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x733fed54) at pthread_cond_timedwait.c:198 #1 0x002488f4 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 5 (Thread 0x734ff470 (LWP 1202)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0xe6fa40, mutex=0xe6fa24, abstime=0x734fe35c) at pthread_cond_timedwait.c:198 #1 0x0021caf8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 4 (Thread 0x7374b470 (LWP 1201)): #0 0x76e14ce8 in __pthread_cond_timedwait (cond=0x3260c0, mutex=0x3260a8, abstime=0x7374a704) at pthread_cond_timedwait.c:198 #1 0x002488f4 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (Thread 0x76a53470 (LWP 1198)): #0 0x76e17014 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=1, futex_word=0x31d8c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 #1 do_futex_wait (sem=sem@entry=0x31d8c0, abstime=0x0) at sem_waitcommon.c:115 #2 0x76e17158 in __new_sem_wait_slow (sem=0x31d8c0, abstime=0x0) at sem_waitcommon.c:282 #3 0x001ac174 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x763ff470 (LWP 1197)): #0 0x76e1494c in __pthread_cond_wait (cond=0x3258f0, mutex=0x3258bc) at pthread_cond_wait.c:186 #1 0x002158e8 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x76f30570 (LWP 1196)): #0 0x76e194cc in __waitpid (pid=1227, stat_loc=0x7e8bfa00, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #1 0x000bbb44 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= ./go: linje 2: 1192 Avbrutt (SIGABRT) sudo mono HSConsole.exe --log pi@raspberrypi:~/HomeSeer $

Her er oppsettet til bryteren. Edit: Off virker ikke via grensesnittet!

hehe..Ja jeg så etterpå at jeg hadde forklart meg rimelig dårlig Jeg må bruke "Dim 1%" som "Av" ellers vil ikke Eventen virke. Men det resulterer jo i at det er en liten glo igjen i pæra, noe som er veeldig irriterende Men setter jeg f.eks. Then On Then 98% Then 1% (med 3 min. delay) Then Off Ja så virker Eventen, men det gir meg en blaff i lysene hver gang dørbryteren eller PIR blir trigget mens lysene er på. Men hvis jeg setter Eventen til å være slik så blir lyset værende på. Then 98% Then Off (med 3. min delay) Bilde i første post er slik jeg har satt den for at eventen skal kjøre som "normalt". I grensesnittet mener jeg dimmeren virker upåklagelig. (er på jobb nå).

Hei. Jeg har en Nexa dimmer (Nexa EYCR-201) hvor jeg sliter med å kunne benytte On/Off i en Event. Det vil si at hvis jeg setter Off til å være Dim1% og On til å være Dim 98% så virker alt som det skal. Det jeg ønsker er at når den er av så skal den være Off og på eks. 20%. Eventen i seg selv virker greit slik jeg har den satt opp. Frank

Nei, da ble det mørkt. Men så fant jeg ett innlegg hvor du @ZoRaC hadde svart ang. invalid value knyttet til Fibaro Dimmer 2 Oppdaterte til siste betaversjon z-wave og det kan se ut til at gjorde underverk. Samme event og tid ? Tusen takk !

Mar-17 17:57:01 Z-Wave Device: Hovedetasje Kjøkken Sensor Binary Set to Off/Closed/No Motion Mar-17 17:57:00 weatherXML Check for timer items to run Mar-17 17:57:00 Z-Wave Device: Hovedetasje Kjøkken Home Security Set to NOTIFICATION for type Home Security, Event: No Event Mar-17 17:56:18 Z-Wave Device: Node 7 Z-Wave Power Set to 0.8 (W) Mar-17 17:56:18 Z-Wave Device: Node 7 Z-Wave Power Set to 207.1 (W) Mar-17 17:56:13 Z-Wave Device: Node 7 Z-Wave Switch Multilevel 1 Set to INVALID VALUE Mar-17 17:56:12 Z-Wave Device: Node 7 Z-Wave Switch Multilevel 1 Set to INVALID VALUE Mar-17 17:56:12 Device Control Device: Node 7 Z-Wave Switch Multilevel 1 to 98% (98) Threadpool worker Mar-17 17:56:12 Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 (Delayed Action) Threadpool worker Mar-17 17:56:12 Event Event Trigger "TEST Kjøkken Lys på kjøkkenet - After sunrise before sunset" Threadpool worker Mar-17 17:56:11 Device Control Device: Node 7 Z-Wave Switch Multilevel 1 to 98% (98) Threadpool worker Mar-17 17:56:11 Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 (Delayed Action) Threadpool worker Mar-17 17:56:11 Event Event Trigger "TEST Kjøkken Lys på kjøkkenet - After sunrise before sunset" Threadpool worker Mar-17 17:56:11 Z-Wave Device: Hovedetasje Kjøkken Sensor Binary Set to On/Open/Motion Mar-17 17:56:11 Z-Wave Device: Hovedetasje Kjøkken Home Security Set to NOTIFICATION for type Home Security, Event: Motion Detected Mar-17 17:56:02 Z-Wave Device: Ute Volvo Amper Set to 9.43 (9.43 Amperes) Mar-17 17:56:01 Z-Wave Device: Ute Volvo Volts Set to 214.11 (214.11 Volts) Mar-17 17:56:00 weatherXML Triggers to check: 0 Mar-17 17:56:00 weatherXML Check for timer items to run Mar-17 17:56:00 Z-Wave Device: Ute Volvo Watt Set to 2014.6 (2014.6 Watts) Mar-17 17:56:00 Z-Wave Device: Hovedetasje Kjøkken Sensor Binary Set to Off/Closed/No Motion Mar-17 17:56:00 Z-Wave Device: Hovedetasje Kjøkken Home Security Set to NOTIFICATION for type Home Security, Event: No Event Mar-17 17:55:59 Z-Wave Device: Ute Volvo Forbruk i kW Set to 36.79 (36.79 kW Hours) Mar-17 17:55:37 Z-Wave Device: Node 7 Z-Wave Power Set to 0.8 (W) Mar-17 17:55:37 Z-Wave Device: Node 7 Z-Wave Power Set to 209 (W) Mar-17 17:55:32 Z-Wave Device: Node 7 Z-Wave Switch Multilevel 1 Set to INVALID VALUE Mar-17 17:55:31 Z-Wave Device: Node 7 Z-Wave Switch Multilevel 1 Set to INVALID VALUE Mar-17 17:55:31 Z-Wave Device: Node 7 Z-Wave Power Set to 0.1 (W) Mar-17 17:55:31 Z-Wave Device: Node 7 Z-Wave Power Set to 44.7 (W) Mar-17 17:55:30 Device Control Device: Node 7 Z-Wave Switch Multilevel 1 to 98% (98) Threadpool worker Mar-17 17:55:30 Event Remove Delayed Device Action Removed event: Delayed Actions Switch Multilevel 1 (Delayed Action) Threadpool worker Mar-17 17:55:30 Event Event Trigger "TEST Kjøkken Lys på kjøkkenet - After sunrise before sunset" Threadpool worker Mar-17 17:55:30 Device Control Device: Node 7 Z-Wave Switch Multilevel 1 to 98% (98) Threadpool worker Mar-17 17:55:30 Event Event Trigger "TEST Kjøkken Lys på kjøkkenet - After sunrise before sunset" Threadpool worker Mar-17 17:55:29 Z-Wave Device: Hovedetasje Kjøkken Sensor Binary Set to On/Open/Motion Mar-17 17:55:29 Z-Wave Device: Hovedetasje Kjøkken Home Security Set to NOTIFICATION for type Home Security, Event: Motion Detected Mar-17 17:55:20 Z-Wave Device: Node 7 Z-Wave Power Set to 0 (W)