Hello,
I just updated my plugin from 30013 to 30014. I have my PI set up with a relay board and was working well but wanted to test the latest feature in 14, monitoring the output if changed by another program. I have the plugin set to load at boot time. I noticed that now when the Pi boots and initializes the plugin, all of the 8 outputs I am using turn on. I can turn them back off in HS3. This was not the case with 13. What logs should I provide for this beta test?
Thanks
-
Disable plugin before update
Probably need to add to installation instructions that the plugin should be disabled before updating (at least on Windows), otherwise get the error:
"Install/Update of package Raspberry IO failed"Leave a comment:
-
Well, that did it. Thank you very much. feel a little sheepish about
missing that.
Look forward to now reading the inputs from my pi
BruceLeave a comment:
-
I need some help. Trying to get the plugin working on a remote pi.
I keep getting this error. I have tried updating mono as shown below.
I have installed the remote and the plugin on the HS system as per the first post in this thread and the user guide
What am I missing? Thanks
Bruce
Raspberry PI terminal
pi@raspberrypi:/usr/local/RaspberryIO $ ./run.sh
Plugin: RaspberryIO Instance: alarmpanel starting...
Connecting to server at 10.0.0.215...
Connection attempt #1
Connected (HomeSeer API 3). Waiting to be initialized...
Sep-18 19:57:41 INFO RaspberryIO version 3.0.0.11
Sep-18 19:57:47 INFO Raspberry Pi running on Bcm2709 processor
Sep-18 19:57:47 INFO Firmware rev10625154, board model B3 (Raspberry Pi 3 Model B)
Sep-18 19:57:47 INFO Serial number: 00000000b52d1f72
Sep-18 19:57:47 ERROR Raspberry.IO.Interop.MemoryMapFailedException: Exception of type 'Raspberry.IO.Interop.MemoryMapFailedException' was thrown.
at Raspberry.IO.Interop.MemoryMap.ThrowOnError[TException] (System.IntPtr result) [0x00012] in <8241fed7a24249b3b5139c88cb92ad83>:0
at Raspberry.IO.Interop.MemoryMap.Create (System.IntPtr address, System.UInt32 size, Raspberry.IO.Interop.MemoryProtection protection, Raspberry.IO.Interop.MemoryFlags memoryflags, System.Int32 fileDescriptor, System.UInt32 offset) [0x00017] in <8241fed7a24249b3b5139c88cb92ad83>:0
at Raspberry.IO.GeneralPurpose.GpioConnectionDriver..ctor () [0x0004e] in <de882e835bca431da477d9e83099fb88>:0
at Raspberry.IO.GeneralPurpose.GpioConnectionSettings.GetBestDr iver (Raspberry.IO.GeneralPurpose.GpioConnectionDriverCapabilitie s capabilities) [0x0000a] in <de882e835bca431da477d9e83099fb88>:0
at Raspberry.IO.GeneralPurpose.GpioConnectionSettings.get_Defau ltDriver () [0x0002f] in <de882e835bca431da477d9e83099fb88>:0
at Raspberry.IO.GeneralPurpose.GpioConnectionSettings..ctor () [0x00006] in <de882e835bca431da477d9e83099fb88>:0
at Raspberry.IO.GeneralPurpose.GpioConnection..ctor (Raspberry.IO.GeneralPurpose.GpioConnectionSettings settings, System.Collections.Generic.IEnumerable`1[T] pins) [0x0001c] in <de882e835bca431da477d9e83099fb88>:0
at Raspberry.IO.GeneralPurpose.GpioConnection..ctor (System.Collections.Generic.IEnumerable`1[T] pins) [0x00000] in <de882e835bca431da477d9e83099fb88>:0
at HSPI_RaspberryIO.RaspberryPiApp.<Init>b__49_0 () [0x000ca] in <545c2516a5504395aa71caa7c9deb039>:0
HS Log
Sep-18 7:57:47 PM RaspberryIO
ERROR Raspberry.IO.Interop.MemoryMapFailedException: Exception of type 'Raspberry.IO.Interop.MemoryMapFailedException' was thrown. at Raspberry.IO.Interop.MemoryMap.ThrowOnError[TException] (System.IntPtr result) [0x00012] in <8241fed7a24249b3b5139c88cb92ad83>:0 at Raspberry.IO.Interop.MemoryMap.Create (System.IntPtr address, System.UInt32 size, Raspberry.IO.Interop.MemoryProtection protection, Raspberry.IO.Interop.MemoryFlags memoryflags, System.Int32 fileDescriptor, System.UInt32 offset) [0x00017] in <8241fed7a24249b3b5139c88cb92ad83>:0 at Raspberry.IO.GeneralPurpose.GpioConnectionDriver..ctor () [0x0004e] in :0 at Raspberry.IO.GeneralPurpose.GpioConnectionSettings.GetBestDr iver (Raspberry.IO.GeneralPurpose.GpioConnectionDriverCapabilitie s capabilities) [0x0000a] in :0 at Raspberry.IO.GeneralPurpose.GpioConnectionSettings.get_Defau ltDriver () [0x0002f] in :0 at Raspberry.IO.GeneralPurpose.GpioConnectionSettings..ctor () [0x00006] in :0 at Raspberry.IO.GeneralPurpose.GpioConnection..ctor (Raspberry.IO.GeneralPurpose.GpioConnectionSettings settings, System.Collections.Generic.IEnumerable`1[T] pins) [0x0001c] in :0 at Raspberry.IO.GeneralPurpose.GpioConnection..ctor (System.Collections.Generic.IEnumerable`1[T] pins) [0x00000] in :0 at HSPI_RaspberryIO.RaspberryPiApp.b__49_0 () [0x000ca] in <545c2516a5504395aa71caa7c9deb039>:0
HS Help
Current Date/Time: 9/18/2017 7:59:08 PM
HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.318
Linux version: Linux HomeTrollerZeeS2V2 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux System Uptime: 0 Days 22 Hours 41 Minutes 53 Seconds
IP Address: 10.0.0.215
Number of Devices: 220
Number of Events: 74
Available Threads: 391
Enabled Plug-Ins
3.0.0.68: HSTouch Server
3.0.4.3: SDJ-Health
3.0.0.73: weatherXML
3.0.1.130: Z-Wave
pi@raspberrypi:/usr/local/RaspberryIO $ mono --version
Mono JIT compiler version 5.2.0.215 (tarball Mon Aug 14 16:25:12 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen (concurrent by default)
homeseer@HomeTrollerZeeS2V2:~ $ mono --version
Mono JIT compiler version 4.5.1 (master/9db20c4 Fri May 13 15:41:42 EDT 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgenLeave a comment:
-
Is it possible in a future revision to get the root device to show connectivity status so I can alarm on lost connectivity?Leave a comment:
-
Hey Pete,Originally posted by Pete View Post
sorry for the delay.
If the RaspberryIO plug-in is running remotely on a RPi with mono 3.x, then you need it to talk to a HS3 running on Linux with mono 3.x
If it is running on a RPi with mono 4.x or later, it can talk to a windows HS3
or a Linux HS3 running mono 4.x or later.Leave a comment:
-
@Spud,
Looking to do pulse counting using a little lightning sensor board with your application. Connection is simple with three wires (3.3VCC, Ground and GPIO2)
It is more just to sense a local pulse. I am currently doing this with a little python script.
Just remotely connecting your plugin to one of two HS3 boxes (using Zee lite HS3 for testing). Zee Lite today is running on Ubuntu 16.04 64 bit.
I am testing on an old RPi (original Zee) with Wheezy installed on a 2G SD card. Yesterday ran out of space on SD card installing Mono so moving it to a 4Gb SD card today. 4Gb sd cards did no work for me here.
Base RPi wheezy without mono is around 3 Gb. Mono-Complete pushes it to over 4Gb so ended up ordered a few 16Gb SD cards as all I had here for testing were 32Gb SD cards.
Still wanting to test your plugin on the original RPi Zee so switched over to installing Mono 3.12. Size of mono-complete installation download is only around 280 Mb compared to over 900Mb with Mono 5.X.Last edited by Pete; June 28, 2017, 02:40 PM.Leave a comment:
-
Question to SPUD
I have been running Jessie lite on the RPi2 and it runs fine for about a month or two then crashes.
The RPi2 is just a Z-Wave slave and now maybe a 1-wire hub. When it ran Wheezy / Z-Wave I have had a problem with it.
Today looking to install original Wheezy on the RPi2 and wondering if you have tested your plugin on Wheezy?
I have installed the original Wheezy on the RPi version 1 and it is doing fine.
Tried this morning to install Wheezy on the RPi2 and having issues. IE: I am just writing the image to an SD card using Linux and it will not boot for whatever reason.
OK so switched to W7, formatted the SD card and used w32 disk imager and it worked the first time. Odd that Ubuntu 16.04 would not write the image correctly to the SD card. Even did the DD thing and it didn't boot.Last edited by Pete; June 26, 2017, 12:31 PM.Leave a comment:
-
in version 3.0.0.6 I have added a button to "pulse" an output pin. The pulse duration is configurable for each pin from the config page, default duration is 1000ms.Leave a comment:
-
I too am interested in sending a 1 second pulse as I want to interface a key-fob like RF transmitter that has lock and unlock buttons on it. This FOB works best with a 1 second key press.Originally posted by MFULLER View Post...A small feature request
If possible can the "toggle" button be configurable as a pulse? e.g you press toggle and it pulses the output once (e.g open/closed) in like half a second. Maybe have a configuration option that when enabled "Enable Pulse" the toggle option actually becomes "Pulse".
It would save people having to press on/off or toggle twice to pulse an output to a different system
...Leave a comment:
Leave a comment: