- 20190906, V0.9.13
- Fixture: Add lastValue parameter to MqttSensor constructor to be able to restore attributes from database on startup
- Added default initialization for MqttSensor attributes values in case the values cannot be restored from database
- Added experimental device discovery for Tasmota switch and dimmer devices, issue #42
- Added support for wildcards (#/+) on state topics, issue #11
- Added JSON payload filtering for MqttSwitch state values, issue #34
- Added JSON payload filtering for MqttPresenceSensor state values, issue #45
- Added JSON payload filtering for MqttDimmer, MqttButtons, MqttContactSensor, and MqttShutter state values
- Added recovery of last state from database for MqttButtons device on startup
- Added support for displaying the status (last button pressed) for MqttButtons device, issue #43
- Fixed setting of default brokerId in case no brokerId has been set in the plugin config
-
pimatic-mqtt@0.9.13
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Thank you for your update. My finding is solved with it.
-
Many thanks
-
Hi guys,
My mqtt is not working anymore. During startup i see:
13:51:06.556 [pimatic] Loading plugin: "pimatic-mqtt" (0.9.13) 13:51:07.065 [pimatic] Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
and a little later:
13:51:19.864 [pimatic] No plugin found for device "acs712" of class "MqttSensor"!
Any ideas?
-
@fregger how dit you fix it?
-
@schmucke I upgraded to NodeJs 8.16.2 and the problem went away.
-
I have the same problem with pimatic-mqtt and old version od NodeJs.
@fregger how did you upgrade NodeJs to 8.16.2? I managed to upgrade it as explained in the original pimatic installation guideline, but afterwards pimatic didn’t start anymore. After reverting to 4.9.1 it worked again. -
@fips21 i have the same error.
after update to 8.16.2 my Pimtaic didn’t start up only the day of the week is displayed -
@fips21 said in pimatic-mqtt@0.9.13:
I have the same problem with pimatic-mqtt and old version od NodeJs.
@fregger how did you upgrade NodeJs to 8.16.2? I managed to upgrade it as explained in the original pimatic installation guideline, but afterwards pimatic didn’t start anymore. After reverting to 4.9.1 it worked again.I‘ve got the same problem like you and wuschel.
Did you tried it like it is recommended on the pimatic wiki installation guideline?
That’s what I will try to do next.
But I will do it with fresh installation of pimatic. -
A general hint:
The installation takes a while. I´m using Node 10.16.3 and it seems that the installation takes even longer then with older versions.
During installation starthtop
and watch your CPU. Don´t restart your pi till the CPU-Usage calms down.
If you restart pimatic or the pi during installation, pimatic will break and doesn´t start.
I think this happend to @wuschel , only showing the weekday.Merry christmas everyone
-
Merry Christmas everyone.
I have been trying to setup GBridge, which is a Google assistant mqtt bridge. My wish is to be able to control all my pimatic devices using my Google home in my native language. The ifttt solution is not available in my language.
I have setup GBridge and made the first mqtt device. When I ask Google to dim my lamp to 100 percent, the reported command is 100 in the mqtt topic, when I’m listening to all messages on my mqtt server.
But pimatic receives the command 102, which is out of range.
It only happens with 100% command for some reason?When I ask for 80 % on Google assistant, then pimatic receives 80%.
It is somewhere in pimatic or mqtt add on the error happens, which changes the 100 to 102.
Anyone know where I can start to solve this problem?
Thank you and a merry Christmas to all.
-
Just to understand your problem:
Whats happens if you ask to dim to 99%, 98%, etc. When is the value ok?
Did you check the mqtt messages you receive from gBridge?
Are you using your own mqtt server to connect to gBridge and not the hosted one from gBridge? -
Hi.
Thanks for the quick reply.When I ask for 99 or 98 % I get what I ask for.
My local mqtt server is set to bridge mode with the gBridge mqtt server.
The messages are received correct on the local mqtt server. The 100% command is also received correctly as 100 on the local mqtt server. It is only when pimatic is reading it, that it changes to 102 % and pimatic says out of range.
I know it is strange, but that is what is happening for some reason?
-
I assume that the bridge is transparant and not changing the value
What resolution are you using?
When a dimmer is set to 100% it is like an alternative for switching it on.
So the payload of a mqtt message could change when you go to 100%. i’m not sure weather thats the problem.
If it’s a problem just before Christmas and you are not afraid to change a bit of code, you could change 1 line of code in the file mqtt-dimmer.coffee in the mqtt directory. Let me know if you want that solution. -
I’m looking at the messages being passed through the mqtt broker.
It is plain figures being passed from the gBridge to the local mqtt broker. It is in pimatic the change is happening, but I can’t figure out why, as it is only the 100% command being changed.
When I ask for turn off, then it will send 0, which works as intended😊I’m open to try and change som code, but I’m not a programmer, so bear with me 🐻😂
-
But I’m not in a hurry. I have the next couple of weeks to setup my Google assistant with all my devices. If I can’t get the dimmer to work, I will end up with an on and off switch instead, but it would be nice to be able to ask to dim the lights when they are capable of it 😊
-
I tried 100 as resolution, but then it would not accept the command received, so I tried 102, 103 and 256 as resolution. All giving the resolution error, but the problem with 102 figures keeps being the same. Although being accepted by the dimmer device in pimatic.
16:47:40error [pimatic-mqtt]: value: 102 is out of range