jgyates
commented
11 months ago Hi @msteil4vse
I don't use the mopeka sensor regulariy as my generator does not use propane, but based on the data you provide here are my thoughts:
One thing that is odd is that you get a name resolution error when running mopeka_utility.py.
sudo python3 mopeka_utility.py
sudo: unable to resolve host [HeadendGenMon.vsenterprisesltd.com](http://headendgenmon.vsenterprisesltd.com/): Name or service not knownI am not sure where this error is coming from or why it is there. It looks like it is coming from the sudo command.
Also, the genmon add on uses this python library, which has been abandoned by the developer. The mopeka_pro_check library only supports specific sensors. Looking at the code in the project here:
the project is looking for one of three specific IDs in the returned data and based off the data packet you posted it does not look like the sensor you are using is supported. Specifically, which mopeka sensor are you using?
msteil4vse
Raptor607
Hello,
Seeking, input from someone out there that is successfully using the Mopeka Pro+ sensors with Genmon, to compare notes with.
This issue is most likely outside the general scope of Genmon, I am intentionally keeping this short, so ask questions as needed.
General info is I have 2 independent systems so far on and attempting to get them to display data from Mopeka Sensors, without much success. Each Pi/Genmon patform has been upgraded to the most recent code available, and the documentation has been followed to the letter. The Genmon/Pi Platforms seem to be having trouble "Syncing" with the sensors or at least that is where things go off the rails with the documentation. Ultimately the genmopeka.log log reports as follows:
2023-10-18 09:14:15,454 : starting scan 2023-10-18 09:14:30,456 : stopped scan 2023-10-18 09:14:30,459 : No sensor comms detected for BDAddress('F2:34:95:E4:B7:95') 2023-10-18 09:14:30,460 : Tank Data = {"Percentage": 0, "Tank Name": "Mopeka Sensor Tank"} 2023-10-18 09:14:30,463 : OK
Controller B8:27:EB:EE:51:B6 (public) Name: HeadendGenMon.vsenterprisesltd.com Alias: HeadendGenMon.vsenterprisesltd.com Class: 0x002c0000 Powered: yes Discoverable: yes DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0537 Discovering: yes Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name [bluetooth]#
sudo python3 mopeka_utility.py sudo: unable to resolve host HeadendGenMon.vsenterprisesltd.com: Name or service not known
NOTE: This program will look for Mopeka Pro Sensors. The SYNC button must be pressed and held for the discovery process to work.
Starting Discovery.... Discovery Stats ReadStats ( Ignored Ad Count: 1, Processed Ad Count: 0, Error Ad Count: 0), Zero Data Ad Count: 0)
Finished Discovery. Found 0 new sensor(s):
Now, I have a BLE scanner, and it sees the broadcast from the sensor, (see below) and the proximity of the devices is such there should be no RF issues.
1 address-type=random address=F2:34:95:E4:B7:95 name="F2:34:95:E4:B7:95" persist=no mtik-key="" rssi=-41 last-data="0DFF5900086F420040E4B795F8DD0302E5FE" last-seen=2023-10-18 09:19:17 beacon-types=""
Lastly, the sensors are reporting that are using the 0.0.98 code.
Thanks to those who read this, hopefully someone has had this difficulty before and has the piece of the puzzle I seem to be missing.
contact me directly if you wish msteil@trvnet.net