@NeverDie Actually no. Because this is an EPA list denoting the effectiveness of listed products, it's much too complicated to find out concentrations of the active ingredient, and I would guess that the kill times have a Factor of Safety built in.
Saw nothing on what surfaces are referred as the Virus is known to survive on different surfaces for different durations, again I suspect a high FoS.
Sorted on "Follow the directions..." and looked for Human Coronavirus, ethanol and isopropol both pop up at 30 seconds contact (normal terminology for disinfection) time.
Hypochlorite is a few minutes but varies according to brand name, so not really helpful if you don't know concentrations.
My point remains that alcohol is readily available, and as an additional precaution post washing surfaces probably more than sufficient in a domestic environment.
If 70% is adequate for handwash on skin where it evaporates in a few seconds, no reason why on a cold non-porous surface it would be no less effective
technically yes this is possible by using:
custom BLE msg, depends on payload length, and longer payload can be enabled
BLE Serial service
but afaik there is no plan for adding and maintaining this for the moment
@GLAB No worries, was in a similar situation.. My perspective was on what the Node could be made to provide, not what could be done within Domoticz to address the requirement - eg Had heard of Dummy counters but had no experience nor understood their purpose, nor had ever used scripts.
I had been sending a logical ON/OFF as well as a cumulative total from the Node and hit the same hair-pulling scenario as yourself.
Now only the ON/OFF is sent and the short script makes the transposition within Domoticz to a dummy meter (I think kWhr) using the internal clock in Domoticz.
Thanks for taking a look Mikeal,.
Here's my update:
I added a 47uF cap to the 3.3V input to the RA-01 Lora radios on both Node and Gateway, now the SF 12 long payload messages pass!
I tested various SF and BW and coding rates, I decided on the following for the "long-range mode". Typical use will be point-point mode, or gateway to 2 or 3 nodes max, no repeaters. Horizontal polarised yagi antennas.
MY_RFM95_FREQUENCY 433237500ul (its 1MHz away from my co-located standard mode gateway frequency and other local ISM users).
RFM95_MODEM_CONFIGRUATION RFM95_BW62_5CR45SF4096 (Typical time-on-air is around 4000ms.
MY_RFM95_ATC_MODE_DISABLED (to reduce traffic).
Passive mode = off.
MY_REPEATER_FEATURE = off.
CAD = Default settings.
Encrypton = Off
Signing = Off
Sleep = Off.
Further test planned:
866 MHz setup.
TXCO setup narrow band modes to 7.6KHz
Chain network topology with repeaters.
Higher RF power (Ham radio license).
@NeverDie I can give my thoughts here, and we can move it later to another thread if necessary.
The bigger selling points, at least for me:
Every project is a self contained directory, even the boards configuration, bootloaders, libraries, code and build procedure
I have a project template for mysensors (mainly a platform.ini) that I copy for each node that I create.
I can manage everything with my known tools (vim, make, git, etc)
I like to play with arduino and electronics, but have other interests (Family, friends and 3 small kids...) so I usually have little time to spent in my hobbies. Platformio allows me to just have all the configuration in code and know 6 months ahead that I can do a "make clean && make upload" for a particular node without issues, even if I lost my PC, as everything is in my gitlab account.
Also the FW of my 3dprinter must be complied and uploaded with platformio (marlin 2.0) so I can have only one tool for both hobbies.