Just released firmware v3.20 has broken inputs/outputs connected to the NXT Master module :
inputs 0.1 - 0.3 don’t always update their status : e.g. my garagedoor (0.2) was open ; the Dobiss touch interface shows this correctly, but the HA entity stays at closed. Solution : selecting “0-10V” and then again “Contact” in the Dobiss config page brings the entity back to life, but only for a short while. Problem returns
when an extension module is connected to the NXT Relay outputs (0.15 to 0.32), their behaviour has changed compared to v3.10 :
Light switches connected to a 220V extension module don’t work anymore in HA (they do in Dobiss of course). They behave like a pulse, not a switch. This was perfectly fine in v3.10
Covers connected to a NO/NC extension module do work well now (where they didn’t before in v3.10)
The change in the API is also confirmed by the Dobiss product manager, Stijn Van Hoecke : Ondertussen hebben we dit eens verder bekeken en er ontbrak nog iets in de combinatie NXT-uitbreidingen met screens/rolluiken om de koppeling met Google Assistant mogelijk te maken. Zal opgelost zijn in de volgende productieversie die er binnen dit en enkele weken zal aankomen.
Everything works fine in the Dobiss interface, so I presume they added something to the API which we will have to take into account now.
I found a workaround though. That is defining a flag which is put on/off together with the input.
HA reads the flag status consistently, so problem solved.
But still, it’s intriguing to know what exactly they changed in the API for NXT Master extension modules.
I’ve asked feedback on what exactly changed in the API. I only have light sensors connected to the NXT module, so not sure I’ll be able to easily test this. But I’ll look into this if I get feedback, and maybe you can help me test something, or capture some debug logs to help find the root cause.
Something else which might be nice to implement is support for pincode locking on some inputs.
I currently have in Dobiss a pincode on “Open Garage” (obviously) and “Close Swimming Pool Cover” (to avoid someone closing the pool cover by mistake when people are still swimming)
But as we now use the HA interface, we are lacking this feature and anyone who would get access to our phone could open the garage.
I could implement this again on HA side (haven’t figured out how yet, still ramping up my YAML skills), but would be nice if the Dobiss Integration could just bring this into HA
I don’t think it’s possible - the dobiss API doesn’t expose this pincode limitation, so there is no way for the HA integration to pick it up. So that would be a feature request for dobiss, and when they implement this, I could look into adding this to the integration
In the meantime, does anybody know of any good custom HA integration to put on a pincode on just the open or close button of a cover ?
There is a custom integration (Lovelace Lock Card), but it locks a whole card, so not very practical in my opinion. It would be nice if there is something around.
If not, it’s time to dust off my programming skills. Been long time…
long time ago hope you are doing well …
Did you have feedback from Dobiss or did you investigate ? Because i’m facing the same issue (I open an issue for you in github)
i’m ready to help you (by testing) to solve this issue
I’ve worked with dobiss, and so far haven’t been able to reproduce this issue. There are some updates in the dev branch on github for better compatibility with this updated NXT server version, so if you could go ahead and try this, and see if that still shows the same behaviour, we can debug some more. Hopefully it works though
Hi @kester , sorry about the slow response, I was a bit occupied.
Yes!, I tried it, this evening.
When trying to add the integration, it stayed stuck for a while at the loading popup (as per screenshot in de reply above), but after a long wait, it finally arrived at the login popup state.
After that I refreshed and tried to add it again, and the login popup was showing instantly.
So that is great news!
no worries, just wanted to make sure you weren’t stuck
But it looks good now! There is as far as I know no publicly available sandbox or demo environment available from dobiss no. Once you have a dobiss NXT server installed, you can go ahead and enable the API and this should be up and running in no time!
@kester
Sound like it would work pretty straight forward, yes!
Are there any specifics of the modules/components I should buy to make it connectable (NXT) in HA? Just triple checking.
hope you are doing well …
