I thought about doing that - but the point is it is coded specifically to behave in the "no update" way - my change isn't a fix but a reversal of some deliberate logic - so if I change it - "someone" might just change it back - the best way would be to implement it as a configuration option - but that is a lot more work that my "dirty hack" of chopping out the checking code.
I will take another look when the 1.6 code is released and see when the options are then.
Have added my request to yours - however, I am not sure who "owns" the code for the mysensors "hardware" for domoticz - in my thread I detail the hack I did to the mysensorsbase.cpp file to make it always update a switch when requested - even if the value has not changed - in my case - this gives me the ability to add a "heartbeat" sensor to any node and update it from the sketch - not as neat as having sendheartbeat supported - but it works for me - but having to make that change every time i update domoticz is a pain. (https://www.domoticz.com/forum/viewtopic.php?f=42&t=9272)
Although nobody has said "its not up to me" - nobody has said - "it works like that for a reason" - I think the change for this would need to come in the mysensorsbase code set - and whilst that is shipped with domoticz - I don't know who actually wrote it - Gimzocus kind of suggested that "it had probably been coded a certain way" - that sounded like he wasn't looking after the code - but I might be wrong on that.
Hi - have discussed this over on Domoticz forum, but I guess it's best placed here.
I would like to use a "fake" sensor from a mysensors node to domoticz to indicate that a particular sensor that has "real" sensors is still alive - the sensors won't change often but I want to know that everything is well - the plan is have three "switches" presented - two linked to rea external sensors - the other, no physical device attached - I wait in the loop for interrupt on either switch and also for a timeout - when I wake - I check switch state - if changed - send update - and also send "on" to the dummy sensor .
this i hoped would make domoticz update its last seen time - but it doesn't - if the switch state does not chnage then the update is ignored - i have confirmed this by modyfying mysensorsbase.cpp to take out the "don't update if nothing changed code".
my question/suggestion is perhaps we should update last seen time - even if we don't actually update the status of the switch (although I have a use case for updating even if value the same)
would like to hear what others think.
I can confirm that the mysensors "adapter" for domoticz does not update anything for a sensor if the value has not changed - including last seen time. There has been a bit of a discussion about it and I have a bug and feature request in for it to be a configurable choice for the user - but as it stands - if no change in value then update is ignored.
I modified the mysensors adapter code to always update - even if values haven't changed - but that isn't really a long term solution since it gets overwritten on every update.
How about iButton?
Basically the system that we (at least in the UK) see a lot in point of sale devices where different users identify themselves to the the system - I have not seen any iButton implementations for MySensors - but we do have the 1wire library.
There are a lot of cheap key fobs and readers available - I am going to use one to allow me to override the house/garage alarm when I get home 1st and want to put the car away before entering the house and disarming the alarm.
I have a coupe of 1wire/DS18B20 working under 1.5.1 - can you post your sketch and confirm which pins things are connected to (and if you have the appropriate resistor in place for the DS18B20 ?
My sketch was pretty much a cut and past from the sample code - so I think that works fine.
@malarcy LIkely bad form replying to my own message - but I found I can work around it by removing the "offending" couple of lines - the temp sensor works - but I suspect that if I chain more together then I might get timing errors and problems.
I removed these lines
// query conversion time and sleep until conversion completed
int16_t conversionTime = sensors.millisToWaitForConversion(sensors.getResolution());
// sleep() call can be replaced by wait() call if node need to process incoming messages (or if node is repeater)
gw.sleep(conversionTime);```
This got me working for testing and playing - but would like some help on the proper solution.
not sure what the forum etiquette is but +1 or "me too" - same error on 1.6.6 ide - I have moved all the libraries etc from the latest mysensors download to the libraries area - other samples build ok - like binaryswitch.
@Cliff-Karlsson - I may be way off base here and I am new to this myself - but, does that sketch you quoted actually compile? - I ask because it looks like you have used the relay sample on the mysensors site - but cut out some of the loop.
The bit that sets the output pin that the relay is connected to pinMode (pin, OUTPUT) .....
From what you have posted, you haven't got pin defined anywhere - in the original example it gets declared in the line
for (int sensor=1, pin=RELAY_1; sensor<=NUMBER_OF_RELAYS;sensor++, pin++)
In your sketch i can't see pin or sensor defined - so I can't see how it's compiling....... but I may have missed something
If I have general advice would be check what pin the relay is connected to, and make sure thats that one you set as output and the one that you do the digitalWrite to.
Hope this helps - but if not - sorry if I am way off base.