P
Its been a while since i've used this now, I've moved to Z-WaveJS..
Socat - so you have a remote connection to your z-stick? Should work fine with this contatiner, just set it up in the docker-compose file.
That said, I would ask on the z-way forum, you may find a more current z-way version in a newer container..
All settings should be persistent if volumes are set up correctly.
I havent needed Socat, just using Z2MQTT in a docker, and it connects to the vera just fine over network.. I ended up retiring the vera in the end in favour of UZB and Z-Stick, as some functions and security didn't work, but basic z-wave works well.
I know nothing about synology, but I do have a setup (at the cabin) that uses an old "nuked" VeraPlus for z-wave and zigbee, and it works flawlessly. I suppose this would be just as easy to do with a synology, bypassing the whole USB interface?
I appreciate both the strictness regarding code and the lesson in javascript. Thanks!
I've found out why my "MaxInInterval" didn't work in the original post, and what that "Force re-evaluation..." tickbox on the reactions does!
(to type it out, I changed the variable in reaction, and naturally, the only variable being updated was the one called out..)
I'd be happy to!
in the original post you see my expression: if NotificationSent != "true" then, which is supposed to reset the maximum reading when notification is sent, and prepare for a new increase when more wood is applied.
This never fired when the condition was met, but when I changed it to if NotificationSent != "1" then, (with the same change in the reactions) it worked as intended. The variable was still interpreted as a string.
My theory was that this was caused by the special considerations for the word "true" in the interpreter somehow, and that the ${{ true }} in the reaction would solve the problem.
That may offcourse be wrong? I admit that the imperical basis is rather thin. 
I should be able to reproduce this if needed.
Considering this solved, but would like to add that its a bit important to mark "true" and "false" as depicted above here, and not using them in string form.
Using "true" in string form in the condition like in "MaxInInterval" in the initial post didn't work, the condition didn't flip when the state changed.
I guess this is because of how these reserved words are interpreted, so tagging them as boolean is important.
The rule is corrected and works well:
It notifies once for each time the temperature has increased, only with temperatures above 100°C, and when i'm home..
The NotificationSent value wasn't nessecary here, But i'm still wondering if one can define a variable type and set the start value, and later manupulate that value by a reaction?
BTW, in the screenshots we see that the NotificationSent has fired, and is now interpreted as a string..
I have a use case where I need to have a boolean variable that will be set to true/false by reactions.
I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.
Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?
Am i going about this the wrong way?
-- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..
Edit: better screenhots. Reactor version 23010-7dd2c9e9
Hello amnd,
It seems to me that the appropriate "assistant" for you is "Home Assistant".
HA is an automation system that has integrations for a lot of IoT devices, and the latest versions is getting much easier to set up as well.
It is however an open source project, which means that it may be a challenge to get going if you have no experience with things like raspberry Pi's or Linux.
HA is also working on their own controller, but as of now people mostly run it on mini-PC's or similar.
if you're completely green on electronics and coding, perhaps Homey is a better bet.
when you have a system like this, you can connect to appliances and IoT in different ways, it all depends on how smart the devices are, and how the company that makes them integrates to other systems.
Regarding speakers, you get all kinds of wifi speaker systems, depending on where an how you want it.
Most automation controllers can be reached from outside the home through an app. This system can in practice be your alarm system if you connect motion and door/window sensors. 
How is the setup today? If you have a wired switch today, I would recommend to have a "pill" type switch/dimmer behind that switch, and a Pi(or some mini-computer) with a USB-Zigbee controller.
In other words, you stopped and deleted the Ezlo SW? In that case, installing ser2net should be a breeze? It would be cool to try running JS UI on it, I'd give it a go if you show me the door in.
I still have the "prototype" Ezlo plus in a box somewhere, any chance of "nuking" it like the Vera Plus? Zigbee and Z-wave 700 chip could be useful..
@toggledbits, the only reason I use Z-wave JS UI into HASS is that i use the HASS visualization on phones and UI panels, that would have to be replaced by helpers/virtuals if I were to take it into MSR instead?
I could offcourse feed both MSR and HASS from JS UI, but that seems like a bit of a waste of bandwidth? dunno..
@gwp1 : Yes, I've seen (100s!) of those, no problem there!
I just had this notion that there was some other function in place, where if a device was gone, it would prompt you "This entity is gone, select replacement here", and that this would do replacement of all uses of that entity/device.
To the other discussion:
My problems started when I moved ALL devices to a new system, as in all entity addresses changed.
I have previously been on the same MSR version for long periods of time without any issues, so I very much doubt any "planned obsolesence".
Ok, so what firmware do you have? You've used this stick before?
The firmware stuff is a bit of a mess, look at this thread..
As I discovered; There is a Bridge firmware for using the stick without z-way, and a regular one for Z-Way. Mabye you have the bridge one?
Don't think you have area troubles, EU is part of the most common firmware..
One workaround would perhaps be to have a helper in HASS that MSR can trigger, which in HASS initiates a notification? Haven't gone in to this myself yet, still using telegram..
@Matohl - If you're thinking about when the only way to make actions happen is the "play" button next to each individual action, I really doubt that its by design, nor being an automated way to say that an update is available. My system had a cascade of dead entities, and I suspect that had something to do with it.
The proper thing to do in that case is to save logs/setup files and open a mantis ticket, just like I didn't here. That how bugs disappear.
After about 7 years in the Vera/openLuup world i've now moved on to a home assistant installation. This was rather reluctantly, as openLuup has served me well with very few issues (other than ones I created myself off course!). A big thanks to @akbooer and all contributors for all the good work with this software!
The main reason for jumping the fence to HASS was in short all the integrations and UI possibilities. The device handling for Zigbee and RFXtrx is also developing to be really good, and is still maintained.
There is still plenty of annoying bugs/imperfections with HASS, but the maturity is at a level where most of what I need works well enough.
My system is now:
So far so good!
Sorry about that, I just had a slight hope for a "you just forgot to push that button" kind of answer..
In any case, I cleaned out my rules over the board and updated the MSR image, and now it's running like a charm..
For future reference, is there in fact a "this entity is now gone from the system, choose a replacement" function, or did i just dream that one? If not, it would be a great addition!
Again, a big thankyou to @toggledbits for sharing this great machine!
That one is OK, it's related to the UI in some way, and not the stick..
Very strange that you have contact to the stick, but can't include? that part usually works flawlessly, I don't use the expert panel for that though, as the other UI has a naming wizard for the units..
