I successfully worked around the issue by updating the /Library/Application Support/Perceptive Automation/Indigo 2022.1/Plugins/MySensors.indigoPlugin/Contents/Server Plugin
/plugin.py script to recognize the internal 21 code.
Here's the diff:
34c134,135
< "GATEWAY_READY" : [14, "Gateway ready", ""]
"GATEWAY_READY" : [14, "Gateway ready", ""],
"DISCOVER_RESPONSE" : [21, "Discover response", ""]
715a717,719
elif itemType == self.getInternalNumber("DISCOVER_RESPONSE"):
# 21 Ignore
pass
P.S. Indigo 2022.1 is complaining about this plugin that it won't be supported in future releases. Is there anyone out there planning to update this plugin?
@NeverDie Thx for appreciating the work done. There will also be an open source part in the future. When and how extensive the open source part will be, remains to be seen. The release of certain information (block diagram, ..., in this post) is related to those open source parts.
There are some OBD solutions, however most of them (in my experience) give back low frequency data put by the car manufacturer on the OBD-bus (CAN, ...). Therefore transients evolving directly from the battery could only be recorded if the manufacturer sends those data accordingly on the bus. Due to the small bandwidth(also because of other car data that have to be sent, ...), such battery data are sent more often once per second or less. Fast battery events (i.e. cranking events, ...) are therefore imperceptible. Unless the manufacturer processes the fast events and then sends them (once per second or less), which is very unlikely if the manufacturer does not market this feature itself. Third parties devices for high frequency sensing costs several hundreds dollars.
In my experience, important battery states (especially the fast ones) are recorded by measuring and processing corresponding data directly on the battery.
I agree with you about the limits related to the communication over Bluetooth. But i think Bluetooth 5.0 will improve a lot. However, WiFi will always remain an important option due to the high data throughput. The combination of both (BLE & WiFi), especially with regard to energy consumption, will gain in importance.
@Tmaster What I meant by my previous comment was to tap on the Node name to see what sensors were connected - Had you clicked on TANQUE you would have seen a box pop up below giving you all the children to that particular Node with what value was last updated and when, so you could easily have found out all about your mysterious 13 children.
At least you have it sorted now, but it pays to do a bit of housekeeping in the sketch setup and Domoticz - eg which of the 6 "Unknown" Nodes is the one you want to next have a look at ?
All my Node IDs are set at the Node, and the sketch name labels the Node ID also, the Nodes are named in Domoticz for easy identification.
In the sketch my sensors are numbered sequentially and commented on what they are, so naming them in Domoticz becomes very much easier.
